On Fri, 2 Apr 2010 08:56:26 +0800 Tom Haste <tomha...@gmail.com> said:
> So... > > We're adding a patch that packagers use to make LUA install correctly, > so wouldnt that make E more difficult to package? Since its effecting > the install of LUA? Its early in the morning here so it may just be my > squishy morning brain not understanding the idea. no no no.. WE are not adding the patch. WE are just assuming the lua install is "sane" (ie provides a .pc file etc.) and expect the installed lua to be patched and set up properly. :) > On 2 April 2010 08:22, Carsten Haitzler <ras...@rasterman.com> wrote: > > On Thu, 1 Apr 2010 16:21:51 -0700 Dave Ray <cl...@jonive.com> said: > > > >> Thanks, I am not aware of any patch for MacOS-X but I would be happy > >> to create one , although I might need some help. > > > > use the same ones linux distros use - look at the debian ones for example. > > > > http://packages.debian.org/lenny/lua5.1 > > > > and specifically: > > > > http://ftp.de.debian.org/debian/pool/main/l/lua5.1/lua5.1_5.1.3-1.diff.gz > > > > sure. the patch also contains things to add debian packaging info into the > > tree > > - but within that patch is what you need to 1. build shared libs, 2. > > provide .pc files that are correct and usable. > > > >> In the mean time, I have used other work-arounds that have allowed me > >> to compile and install the packages. > >> > >> FYI "Fink" (as described on the E MacOSX page) is an older X11 > >> implementation on MacOS that has been out of date and unsupported for > >> at least 2 years (actually Fink has many problems and was abandoned). > >> Apple's latest X11 implementation is excellent, much more compatible > >> than before, and does not require Fink. E16 compiles and runs great > >> just using the default Darwin environment, and I am very close to > >> getting E17 to work. I plan to make a binary install package for MacOS > >> and to help update the Enlightenment MacOS-X page as soon as I have a > >> working wm. That page is very out of date. > >> > >> -Dave > >> > >> > >> > >> > >> On Apr 1, 2010, at 3:33 PM, Carsten Haitzler (The Rasterman) wrote: > >> > >> > On Thu, 1 Apr 2010 15:11:55 -0700 Dave Ray <cl...@jonive.com> said: > >> > > >> > see my previous mail. lua as-is from upstream is insufficient. you > >> > need to > >> > patch it like linux distributions do to make it sane. > >> > > >> >> Thans for taking the time to make this diff. Sadly it does not seem > >> >> to > >> >> fix the problem. I tried compiling EDJE with and without the patch > >> >> and > >> >> with a number of different ENV options with the following results: > >> >> > >> >> my normal environment: > >> >> LDFLAGS=-L/usr/lib -L/usr/X11/lib -L/usr/local/lib > >> >> [ lua located at /usr/local/lib/liblua.a ] > >> >> > >> >> 1) without patchfile: > >> >> > >> >> ./autogen.sh produces: > >> >> ... > >> >> checking for LUA... no > >> >> checking for LUA... no > >> >> checking for LUA... no > >> >> checking for LUA... no > >> >> configure: error: unable to find Lua > >> >> > >> >> 2) with patchfile: > >> >> > >> >> ./autogen.sh produces: > >> >> ... > >> >> checking for LUA... no > >> >> checking for LUA... no > >> >> checking for LUA... no > >> >> checking for LUA... no > >> >> ... > >> >> [autogen.sh finishes without error] > >> >> [make fails with "ld: symbols not found"] > >> >> > >> >> 3) with patchfile: > >> >> LDFLAGS=-L/usr/lib -L/usr/X11/lib -L/usr/local/lib -llua (<- > >> >> added - > >> >> llua) > >> >> ./autogen.sh produces: > >> >> ... > >> >> checking for LUA... no > >> >> checking for LUA... no > >> >> checking for LUA... no > >> >> checking for LUA... no > >> >> ... > >> >> [autogen.sh finishes without error] > >> >> [make finishes without error, but might not have LUA linked] > >> >> > >> >> 4) with patchfile: > >> >> LDFLAGS=-L/usr/lib -L/usr/X11/lib -L/usr/local/lib (<- without - > >> >> llua) > >> >> LUA_CFLAGS=-I/usr/local/include > >> >> LUA_LIBS=-L/usr/local/lib > >> >> > >> >> ./autogen.sh produces: > >> >> ... > >> >> checking for LUA... yes > >> >> ... > >> >> [autogen.sh finishes without error] > >> >> [make fails with "ld: symbols not found"] > >> >> > >> >> 5) with patchfile: > >> >> LDFLAGS=-L/usr/lib -L/usr/X11/lib -L/usr/local/lib -llua (<- > >> >> added - > >> >> llua) > >> >> LUA_CFLAGS=-I/usr/local/include > >> >> LUA_LIBS=-L/usr/local/lib > >> >> > >> >> ./autogen.sh produces: > >> >> ... > >> >> checking for LUA... yes > >> >> ... > >> >> [autogen.sh finishes without error] > >> >> [make finishes without error] > >> >> > >> >> From there on, I have to set new environment variables for every > >> >> package I need to compile that uses LUA or EDJE. > >> >> [package-name]_CFLAGS=-I/usr/local/include > >> >> [package-name]_LIBS=-L/usr/local/lib -llua > >> >> > >> >> This is what I was reporting yesterday. > >> >> > >> >> By the way this is using the latest source in svn. > >> >> > >> >> Dave > >> >> > >> >> > >> >> On Mar 31, 2010, at 9:20 PM, Vincent Torri wrote: > >> >> > >> >>> > >> >>> 1) patch edje with the attached file : > >> >>> > >> >>> put that file in edje/, then: > >> >>> > >> >>> patch -p0 < edje_lua.diff > >> >>> > >> >>> 2) set CFLAGS accordingly: > >> >>> > >> >>> export CFLAGS="$CFLAGS -I/my/lua/prefix/include" > >> >>> > >> >>> 3) set LDFLAGS accordingly: > >> >>> > >> >>> export LDFLAGS="$LDFLAGS -L/my/lua/prefix/lib" > >> >>> > >> >>> note that there is no -llua anymore > >> >>> > >> >>> 4) run 'make', it should launch autoconf and other autotools > >> >>> automatically > >> >>> > >> >>> 5) if edje compiles: > >> >>> > >> >>> go to elementary directory > >> >>> run 'make maintainer-clean' > >> >>> run './autogen.sh' > >> >>> run 'make' > >> >>> > >> >>> tell me if there are errors > >> >>> > >> >>> Vincent<edje_lua.diff> > >> >> > >> >> > >> >> ------------------------------------------------------------------------------ > >> >> Download Intel® Parallel Studio Eval > >> >> Try the new software tools for yourself. Speed compiling, find bugs > >> >> proactively, and fine-tune applications for parallel performance. > >> >> See why Intel Parallel Studio got high marks during beta. > >> >> http://p.sf.net/sfu/intel-sw-dev > >> >> _______________________________________________ > >> >> enlightenment-devel mailing list > >> >> enlightenment-devel@lists.sourceforge.net > >> >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > >> >> > >> > > >> > > >> > -- > >> > ------------- Codito, ergo sum - "I code, therefore I am" > >> > -------------- > >> > The Rasterman (Carsten Haitzler) ras...@rasterman.com > >> > > >> > >> > >> ------------------------------------------------------------------------------ > >> Download Intel® Parallel Studio Eval > >> Try the new software tools for yourself. Speed compiling, find bugs > >> proactively, and fine-tune applications for parallel performance. > >> See why Intel Parallel Studio got high marks during beta. > >> http://p.sf.net/sfu/intel-sw-dev > >> _______________________________________________ > >> enlightenment-devel mailing list > >> enlightenment-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > >> > > > > > > -- > > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > > The Rasterman (Carsten Haitzler) ras...@rasterman.com > > > > > > ------------------------------------------------------------------------------ > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
