[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: [ANN] lgi 0.2 - Lua to GObject (GNOME) libraries binding
- From: Javier Guerra Giraldez <javier@...>
- Date: Thu, 24 Nov 2011 09:42:36 -0500
On Thu, Nov 24, 2011 at 9:29 AM, Hisham <email@example.com> wrote:
> On Unix systems (the target platform of lgi), the simple case of
> installing LuaRocks under /usr/local is a matter of "./configure &&
> make && sudo make install", and "sudo luarocks install lgi" would then
> install the module building a standard Lua tree under /usr/local
> (using /usr/local/lib/lua/5.1 and so on), provided you have the
> necessary external dependencies. (The lgi builder checks external
> dependencies by itself, so in that aspect it wouldn't be any different
> from building "by hand"). Is there anything in your setup which makes
> these procedures inadequate?
i've tried that a few times, but what i get is a non-standard tree and
a preloader. it was a few months ago, so i don't remember the
details; but could that be because
- how luarocks itself was installed / configured?
- how it was invoked?
- something about the specific packages i was installing?
also, how can i tell luarocks that i already have something installed,
not from a rock but as a standard module?
maybe just a rockspec->english (or bash, or whatever) translator would
be better for old stubborn guys like me....