[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 140594] kdevelop fails to evaluate local variables
From: Andreas Pakulat <apaku () gmx ! de>
Date: 2007-01-25 22:53:56
Message-ID: 20070125225356.15581.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=140594
------- Additional Comments From apaku gmx de 2007-01-25 23:53 -------
Ok, I just downloaded the gimp code and imported it into 3.4.0. No problems, after \
installing a few requirements the automake&friends run works perfectly. Afterwards it \
runs configure --enable-maintainer-mode which is perfectly fine as it also states \
that this can only be changed by changing autogen.sh or setting an environment \
variable. This indicates that autogen.sh contains a call to configure. And this is \
what is causing problems for you.
Try a fresh import and before running automake&friends change the build configuration \
to default in Project Options->Configure options.
The reason for this is that because the autogen.sh script calls configure directly, \
configure is called in the top-level dir of the gimp sources, which means the \
Makefiles are not created where KDevelop expects them (inside a copy of the source \
tree in the debug subdir) but directly in the source tree. And no this is not a \
kdevelop bug, its more a bug in gimp's usage of autogen.sh as it runs configure even \
though it should only run the autotools in the right order.
So this should fix your problem of opening the project and building it and we can get \
back to the original problem and wether its solved in 3.4.0.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic