GNOME Bugzilla – Bug 621194
cmake doesn't configure (reconfigure) when --autogen
Last modified: 2010-07-03 07:47:18 UTC
Attempting: $ jhbuild buildone --autogen libproxy Doesn't cause the libproxy module to be reconfigure. --------------- This command: $ jhbuild buildone --autogen libproxy causes the following to be run: cmake -DCMAKE_INSTALL_PREFIX=/opt/gnome2 -DLIB_INSTALL_DIR=/opt/gnome2/lib64/home/oxyde/gnome2/libproxy-0.4.0 This command: $ jhbuild buildone libproxy causes the following to be run: make Therefore it looks like JHBuild is sending the correct command, but CMake is caching the previous configure result. I guess a command needs to be run to clear the CMake cache.
I am not sure about what you are seeing; are you sure the commands you copy/pasted are the correct ones? ("jhbuild buildone --autogen libproxy" is given in both first and second examples, with different results.)
There isn't a mistake in my description, but I'll try to describe the problem better: jhbuild buildone --autogen libproxy doesn't re-check what libraries are available, instead cmake uses the last cached result.
Oh, I get it; I doesn't look lilke cmake has a flag to avoid loading the cache, probably removing CMakeCache.txt would work; I'll do that.
commit 95f78f3d1a3c8f59c3ae92e69fe40d115206115e Author: Frédéric Péters <fpeters@0d.be> Date: Sat Jul 3 09:46:03 2010 +0200 Remove CMakeCache.txt before triggering the cmake configure command (GNOME bug 621194)