Re: [E-devel] Recent e_modules configure.in changes
On Wed, 14 Nov 2007, Christopher Michael wrote: Hey Seb, Just looking through configure.in I wondered why you didn't use: AC_PATH_PROG(EDJE_CC, edje_cc, , $PATH) instead of the: edje_cc=$(pkg-config --variable=prefix edje)/bin/edje_cc it is maybe possible that $(pkg-config --variable=prefix edje)/bin in not in the PATH. With AC_PATH_PROG, you are sure tht edje_cc can be called. Vincent - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Recent e_modules configure.in changes
On Thu, 15 Nov 2007, [EMAIL PROTECTED] wrote: With edje_cc=$(pkg-config --variable=prefix edje)/bin/edje_cc you get the full path, so it will be executable anyway. ha, indeed :) With AC_PATH_PROG(EDJE_CC, edje_cc, , $PATH) edje_cc must be in the path, which is possible that it isn't. Could be that people install library binaries in special folders? I usually install all the efl in $HOME/local/e17. I have to add $HOME/local/e17/bin to my path. So, imagine that a guy who installed edje in a specific folder (for any reason) and he didn't update his PATH, or if he miswrote the dir after --prefix when installing edje. Vincent - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Recent e_modules configure.in changes
On Wed, 14 Nov 2007, Christopher Michael wrote: Hey Seb, Just looking through configure.in I wondered why you didn't use: AC_PATH_PROG(EDJE_CC, edje_cc, , $PATH) instead of the: edje_cc=$(pkg-config --variable=prefix edje)/bin/edje_cc it is maybe possible that $(pkg-config --variable=prefix edje)/bin in not in the PATH. With AC_PATH_PROG, you are sure tht edje_cc can be called. With edje_cc=$(pkg-config --variable=prefix edje)/bin/edje_cc you get the full path, so it will be executable anyway. With AC_PATH_PROG(EDJE_CC, edje_cc, , $PATH) edje_cc must be in the path, which is possible that it isn't. Could be that people install library binaries in special folders? Sebastian - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Recent e_modules configure.in changes
Hey Seb, Just looking through configure.in I wondered why you didn't use: AC_PATH_PROG(EDJE_CC, edje_cc, , $PATH) instead of the: edje_cc=$(pkg-config --variable=prefix edje)/bin/edje_cc that is there currently. Because the latter was used in the first file I encountered, and I just did the same in all files. But I agree, the first is probably better, as it really isn't important where the edje_cc is as long as it works. Sebastian - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Recent e_modules configure.in changes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Carsten Haitzler (The Rasterman) schreef: On Thu, 15 Nov 2007 11:12:49 +0100 Dr. Michael 'Mickey' Lauer [EMAIL PROTECTED] babbled: If you want to be nice to cross-compilation environments, AC_PATH_PROG(EDJE_CC, edje_cc, , $PATH) edje_cc is more advisable than edje_cc=$(pkg-config --variable=prefix edje)/bin/edje_cc since in the latter case it would probably point to the cross-compiled edje_cc which we surely can't run during the build process. of course if you did the scratchbox trick of being able to run arm binaries even when cross compiling... problem solved :) Actually, no. Qemu still can't emulate armv6 and armv7 binaries, needs gruesome patches to support nptl (which is what openmoko needs), crashes when you run stuff compiled with llvm, and it doesn't support platforms I build for (e.g. blackfin and avr32). Depending on things like scratchbox is shortsighted and leads to bad infrastructure. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHPDhkMkyGM64RGpERAgBkAKCo81ntCBbdiBlawWztv2xAUcUx1gCgnOuu G4dP6cNQdAd35489EF4fDC8= =bki3 -END PGP SIGNATURE- - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Recent e_modules configure.in changes
If you want to be nice to cross-compilation environments, AC_PATH_PROG(EDJE_CC, edje_cc, , $PATH) edje_cc is more advisable than edje_cc=$(pkg-config --variable=prefix edje)/bin/edje_cc since in the latter case it would probably point to the cross-compiled edje_cc which we surely can't run during the build process. Regards, :M: -- Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Recent e_modules configure.in changes
On Thu, 15 Nov 2007 11:12:49 +0100 Dr. Michael 'Mickey' Lauer [EMAIL PROTECTED] babbled: If you want to be nice to cross-compilation environments, AC_PATH_PROG(EDJE_CC, edje_cc, , $PATH) edje_cc is more advisable than edje_cc=$(pkg-config --variable=prefix edje)/bin/edje_cc since in the latter case it would probably point to the cross-compiled edje_cc which we surely can't run during the build process. of course if you did the scratchbox trick of being able to run arm binaries even when cross compiling... problem solved :) -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Recent e_modules configure.in changes
On Thu, 15 Nov 2007 13:15:32 +0100 Koen Kooi [EMAIL PROTECTED] babbled: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Carsten Haitzler (The Rasterman) schreef: On Thu, 15 Nov 2007 11:12:49 +0100 Dr. Michael 'Mickey' Lauer [EMAIL PROTECTED] babbled: If you want to be nice to cross-compilation environments, AC_PATH_PROG(EDJE_CC, edje_cc, , $PATH) edje_cc is more advisable than edje_cc=$(pkg-config --variable=prefix edje)/bin/edje_cc since in the latter case it would probably point to the cross-compiled edje_cc which we surely can't run during the build process. of course if you did the scratchbox trick of being able to run arm binaries even when cross compiling... problem solved :) Actually, no. Qemu still can't emulate armv6 and armv7 binaries, needs gruesome patches to support nptl (which is what openmoko needs), crashes when you run stuff compiled with llvm, and it doesn't support platforms I build for (e.g. blackfin and avr32). Depending on things like scratchbox is shortsighted and leads to bad infrastructure. sure - but when it works (as maemo uses it), it works really nicely. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Recent e_modules configure.in changes
[EMAIL PROTECTED] wrote: Hey Seb, Just looking through configure.in I wondered why you didn't use: AC_PATH_PROG(EDJE_CC, edje_cc, , $PATH) instead of the: edje_cc=$(pkg-config --variable=prefix edje)/bin/edje_cc that is there currently. Because the latter was used in the first file I encountered, and I just did the same in all files. But I agree, the first is probably better, as it really isn't important where the edje_cc is as long as it works. Agreed :) dh Sebastian - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Recent e_modules configure.in changes
On Thursday 15 November 2007, Carsten Haitzler wrote: On Thu, 15 Nov 2007 11:12:49 +0100 Dr. Michael 'Mickey' Lauer If you want to be nice to cross-compilation environments, AC_PATH_PROG(EDJE_CC, edje_cc, , $PATH) edje_cc is more advisable than edje_cc=$(pkg-config --variable=prefix edje)/bin/edje_cc since in the latter case it would probably point to the cross-compiled edje_cc which we surely can't run during the build process. of course if you did the scratchbox trick of being able to run arm binaries even when cross compiling... problem solved :) while scratchbox with qemu provides a novel trick for executing binaries of other arches, it certainly isnt resilient nor feasible for all targets and requires a lot of extra work. AC_PATH_PROG() is the correct answer all the time. -mike signature.asc Description: This is a digitally signed message part. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] Recent e_modules configure.in changes
Hey Seb, Just looking through configure.in I wondered why you didn't use: AC_PATH_PROG(EDJE_CC, edje_cc, , $PATH) instead of the: edje_cc=$(pkg-config --variable=prefix edje)/bin/edje_cc that is there currently. dh - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
