Re: custom install paths

2010-07-20 Thread Wesley Smith
> Maybe these can help (please read them in the order given here): >   >   >   >  

Re: custom install paths

2010-07-20 Thread Stefano Lattarini
At Tuesday 20 July 2010, Wesley Smith wrote: > > luadir = $(LUA_DIR) > > lua_LTLIBRARIES = cairo.la > > ok, one more thing. I understand what's going on with the above > code with *dir matching *_LTLIBRARIES, but before you posted that > code, I had not idea that such things were possible. In ot

Re: custom install paths

2010-07-20 Thread Wesley Smith
> luadir = $(LUA_DIR) > lua_LTLIBRARIES = cairo.la ok, one more thing. I understand what's going on with the above code with *dir matching *_LTLIBRARIES, but before you posted that code, I had not idea that such things were possible. In other words, I thought lib_LTLIBRARIES was a single variabl

Re: custom install paths

2010-07-20 Thread Wesley Smith
> Surely not given that you're generating the module by compiling code. > /usr/lib/lua/5.1, perhaps? Actually you're right. Egg on my face. I looked into how other packages like Lua Socket do it They put symlinks in /usr/lib/lua/5.1 to the actual compiled libs in /usr/lib. Here are the Lua Soc

Re: custom install paths

2010-07-19 Thread Russ Allbery
Wesley Smith writes: > I've been reading ch12 in the automake manual, trying to make heads or > tails of how to setup a custom install location as a default that can be > overridden by the user. > Here's an example Makefile.am > AM_CPPFLAGS = -I/usr/include/lua5.1 -I/usr/include/cairo > -I/usr/

custom install paths

2010-07-19 Thread Wesley Smith
I've been reading ch12 in the automake manual, trying to make heads or tails of how to setup a custom install location as a default that can be overridden by the user. Here's an example Makefile.am AM_CPPFLAGS = -I/usr/include/lua5.1 -I/usr/include/cairo -I/usr/include/directfb -I/usr/include/fre