| "Build (if required) before launching" changes active build configuration [message #214615] |
Mon, 21 April 2008 08:22 |
Eclipse User |
|
|
|
Originally posted by: lukester_null.yahoo.co.uk
Hi
With a standard makefile project, I find that having the "Build (if
required) before launching" setting enabled changes the active build
configuration when running or debugging.
My project has two configurations - mdid (old style boost naming,
essentially debug with dynamic libraries) and mdi (release).
The makefile generates two different binaries for each config, but also
a soft link with a common name (the project's name) pointing to the last
built binary. (It seems like variables from the build config can't be
used in the run config so that's why I do this to create a "common" name
that can be used across run configurations).
So, starting with no run configurations defined:
1. Select mdid as active build configuration
2. Build
3. Run - select the soft link. All is well.
4. Now select mdi as the build configuration
5. Run - builds mdid build again and runs that. Active build
configuration is now mdid.
I think someone else may have tripped over this:
http://dev.eclipse.org/newslists/news.eclipse.tools.cdt/msg1 5072.html or
are we going crazy?!
My work around for now is to disable "Build (if required) before
launching" and do a two stage build then debug/run, rather than just
debug/run but it would be nice if it's possible to stop it from changing
the build configuration...
Is this intentional behavior or is there some other way to "tie
together" a build and run configuration? Or in fact, decouple them as it
seems the run configuration created in step 3 is somehow tied to the
build configuration active at the time!
Tried both Fedora 8's CDT (4.0.1) and latest from eclipse.org.
Thanks in advance for any help.
Luke Elliott.
|
|
|
Powered by
FUDForum. Page generated in 0.02905 seconds
Home