I'm running Ubuntu 9.10 with geany 0.18 from the devel PPA. To give the new 0.19 a try, I've compiled and installed a local copy with
./configure --prefix=/home/jd/local/geany-test
Now I want to compile the latest 0.19 plugins, but it doesn't work. configure doesn't use the the prefix and so always find the "officially" installed 0.18.
./configure --prefix=/home/jd/local/geany-test --with-geany-libdir=/home/jd/local/geany-test
What's the correct way to make configure use the geany test installation?
On Mon, 21 Jun 2010 10:47:19 +0200, Joerg Desch jd.vvd@web.de wrote:
I'm running Ubuntu 9.10 with geany 0.18 from the devel PPA. To give the new 0.19 a try, I've compiled and installed a local copy with
./configure --prefix=/home/jd/local/geany-test
Now I want to compile the latest 0.19 plugins, but it doesn't work. configure doesn't use the the prefix and so always find the "officially" installed 0.18.
./configure --prefix=/home/jd/local/geany-test --with-geany-libdir=/home/jd/local/geany-test
What's the correct way to make configure use the geany test installation?
I did set up my PKG-config dir to include also local installation, so the configure script will catch up the 0.19 as first installation.
Cheers, Frank
On Mon, 21 Jun 2010 09:35:14 +0000 Frank Lanitz frank@frank.uvena.de wrote:
I did set up my PKG-config dir to include also local installation, so the configure script will catch up the 0.19 as first installation.
Super fast answer. Thanks.
Do you modify the environment variable or is there a option for configure (which I currently miss)?
On Mon, 21 Jun 2010 11:45:53 +0200, Joerg Desch jd.vvd@web.de wrote:
On Mon, 21 Jun 2010 09:35:14 +0000 Frank Lanitz frank@frank.uvena.de wrote:
I did set up my PKG-config dir to include also local installation, so the configure script will catch up the 0.19 as first installation.
Super fast answer. Thanks.
Do you modify the environment variable or is there a option for configure (which I currently miss)?
I'm not sure how to best modify only temporally, as I did set it inside my .zshrc and never ever cared about :)
Cheers, Frank
On Mon, 21 Jun 2010 09:51:53 +0000 Frank Lanitz frank@frank.uvena.de wrote:
I'm not sure how to best modify only temporally, as I did set it inside my .zshrc and never ever cared about :)
I now simply export the environment variable (manually) and build the plugins. (Nearly) all works fine. Thanks again.
The problem with the templates replacing the filename still not works. ;-) Nick Treleaven is aware of this problem (Thread: BUG: storing a custom template clutters buffer.)
On Mon, 21 Jun 2010 11:45:53 +0200 Joerg Desch jd.vvd@web.de wrote:
On Mon, 21 Jun 2010 09:35:14 +0000 Frank Lanitz frank@frank.uvena.de wrote:
I did set up my PKG-config dir to include also local installation, so the configure script will catch up the 0.19 as first installation.
Super fast answer. Thanks.
Do you modify the environment variable or is there a option for configure (which I currently miss)?
The configure script internally modifies PKG_CONFIG_PATH=${geany_libdir} temporarily for locating geany's include files for a non-standard path. ${geany_libdir} is what's passed to --with-geany-libdir, and is the directory where geany.pc is found.
On Mon, 21 Jun 2010 18:33:53 +0800 Chow Loong Jin hyperair@ubuntu.com wrote:
The configure script internally modifies PKG_CONFIG_PATH=${geany_libdir} temporarily for locating geany's include files for a non-standard path. ${geany_libdir} is what's passed to --with-geany-libdir, and is the directory where geany.pc is found.
OK. Thanks for the info. I've never tried to "understand" the autotools "in the depth".
On Mon, 21 Jun 2010 14:08:46 +0200, Joerg Desch jd.vvd@web.de wrote:
On Mon, 21 Jun 2010 18:33:53 +0800 Chow Loong Jin hyperair@ubuntu.com wrote:
The configure script internally modifies PKG_CONFIG_PATH=${geany_libdir} temporarily for locating geany's include files for a non-standard path. ${geany_libdir} is what's passed to --with-geany-libdir, and is the directory where geany.pc is found.
OK. Thanks for the info. I've never tried to "understand" the autotools "in the depth".
Me neither. I prefer the waf approach even there I don't have a clue about everything is working :)
Cheers, Frank
On Mon, 21 Jun 2010 12:17:42 +0000 Frank Lanitz frank@frank.uvena.de wrote:
Me neither. I prefer the waf approach even there I don't have a clue about everything is working :)
WAF is on my "ways too long" TODO list. My wife, my kids, the house and the dog. All are "eating" my spare time. So all the interesting stuff moves into the TODO list and wait for me. ;-)
On Mon, 21 Jun 2010 10:47:19 +0200 Joerg Desch jd.vvd@web.de wrote:
I'm running Ubuntu 9.10 with geany 0.18 from the devel PPA. To give the new 0.19 a try, I've compiled and installed a local copy with
./configure --prefix=/home/jd/local/geany-test
Now I want to compile the latest 0.19 plugins, but it doesn't work. configure doesn't use the the prefix and so always find the "officially" installed 0.18.
./configure --prefix=/home/jd/local/geany-test --with-geany-libdir=/home/jd/local/geany-test
What's the correct way to make configure use the geany test installation?
./configure --with-geany-libdir=/home/jd/local/geany-test/lib would be the right way to go. --with-geany-libdir wants the ${libdir}, not the ${prefix} of Geany.
Depending on the distro, this can be ${geany_prefix}/lib or ${geany_prefix}/lib64 or even ${geany_prefix}/lib32. I didn't want to autodetect that, so I left it to the user to specify. I thought it was pretty obvious, considering it was worded "geany-libdir" rather than "geany-prefix". I guess it wasn't obvious enough.
Anyway, I haven't gotten round to this, but I plan to scrap all this --with-geany-* crap and just let you specify the --prefix/libdir and let everything be resolved automatically.
On Mon, 21 Jun 2010 18:30:38 +0800 Chow Loong Jin hyperair@ubuntu.com wrote:
./configure --with-geany-libdir=/home/jd/local/geany-test/lib would be the right way to go. --with-geany-libdir wants the ${libdir}, not the ${prefix} of Geany.
Ahh. OK, thanks.
I thought it was pretty obvious, considering it was worded "geany-libdir" rather than "geany-prefix". I guess it wasn't obvious enough.
I thought it is the the "base directory" where the lib directory is located. After your hint, this sound a little big strange. ;-)