and ApplicationRunConfiguration to LocalApplicationRunConfiguration,
preparing remote debugging. Change the interface canRun() to be const,
run() to create() (since it does not run anything), use references
to the QSharedPointer<Foo>. Introduce d-Pointer and remove
unneeded headers from ProjectExplorerPlugin and add missing includes
everywhere.
Closer again to qmake, ossi won't like it, but this is exactly what
qmake does, even it it looks a little bit strange. He can come up with
a better fix after he is back from vacation.
It works, except that the code model doesn't get the rvct include
directories and defines yet. And you need to have everything for
rvct set up in your environment.
This is a fix for a446491ae8.
The option debug_and_release determines whether the debug/ and release/
subdirectories are used to put *object* files there. The option
debug_and_release_target is used to put the final taget into debug/
and release/ directories.
Merge-request: 745
Reviewed-by: dt <qtc-committer@nokia.com>
CONFIG+=debug_and_release not working on linux and
CONFIG-=debug_and_release not working on windows.
The logic should be now correct. That is the profile reader reads the
values that are set for the qt build, gets qmake arguments which we
might pass on the command line and reads the .pro files, and in the end
we are interested what CONFIG contains. Patch from Michael Karcher
Task-number: 254925
Note: This code should be shared between Qt4RunConfiguration,
CMakeRunConfiguration and CustomRunExecutable. Also we are approaching
other IDEs like configuraion options for setting the environment.
Without having a good GUI for that. I'll probably be redesigning this
for 1.3 or 1.4.
Missing is options to base the environment on either:
- the last build buildconfiguration (current implementation)
- the project environment
- a clean environment
signals which indicate that the baseEnvironment changed
some layout stuff is wrong
Qt Creator wouldn't find the correct target if shadow building a project
that uses $$OUT_PWD, like for example itemviews-ng.
We didn't set the necessary variable on the ProFileReader *, simplified
the code to always use a ProFileReader created for the exact
profilenode.
Save a relative path to the .pro file. This means RunConfigurations can
now be shared between platforms.
Note: BuildConfigurations have two problems: The qt version id and the
shadow build option. If the user doesn't use those two, then he is fine.
