Lines Matching refs:package

6 [[luarocks-package-tutorial]]
8 ==== +luarocks-package+ tutorial
10 First, let's see how to write a +.mk+ file for a LuaRocks-based package,
29 16: $(eval $(luarocks-package))
32 On line 7, we declare the version of the package (the same as in the rockspec,
36 On line 8, we declare that the package is called "foo" on LuaRocks. In
42 are built before the build process of our package starts.
45 building the package.
47 On lines 13-14, we specify the licensing terms for the package.
49 Finally, on line 16, we invoke the +luarocks-package+
51 package to be built.
57 that will automatically generate a Buildroot package. The result must
60 * The +package/Config.in+ file has to be updated manually to include the
63 [[luarocks-package-reference]]
65 ==== +luarocks-package+ reference
69 Buildroot, the +luarocks-package+ infrastructure only supports the +builtin+
71 should instead be packaged using the +generic-package+ and +cmake-package+
74 The main macro of the LuaRocks package infrastructure is +luarocks-package+:
75 like +generic-package+ it works by defining a number of variables providing
76 metadata information about the package, and then calling +luarocks-package+.
79 by defining a number of variables before calling the +luarocks-package+
82 First, all the package metadata information variables that exist in
88 +download+ step). If your package is not hosted on the LuaRocks mirror
100   package name