- Jul 10, 2009
-
-
Daniel Molkentin authored
This reverts commit 33dd9dea.
-
Daniel Molkentin authored
-
- May 27, 2009
-
-
dt authored
Note: as for qt projects, this is also used for running. And we don't use it for running cmake yet.
-
- May 08, 2009
-
-
Alessandro Portale authored
-
- Apr 22, 2009
-
-
dt authored
Hopefully i didn't miss a plugin.
-
- Mar 09, 2009
-
-
dt authored
Details: That fixes a few bugs, while still having a few missing things. Don't allow the user to set a shadow build directory, if there is already a in source build. Detect if a cbp file is already existing and recent enough, don't rerun cmake then. Ensure that the user runs cmake with the cbp generator on opening the project. Show the output of the cmake generator while running. Remove the unecessary cmake step.
-
- Jan 23, 2009
-
-
dt authored
Details: Add a dialog asking for command line options and build directory. This dialog pops up if you don't have a .user file. Note, though that it also pops up if there is already a in source build. (The build directory lineedit should be read only then.) The cmake button in that dialog and the output pane need more polish to make them better. With those changes you can now build and run marble from Qt Creator. (For marble you need to pass a few options to cmake.) Also add a configuration page to the Tools/Options dialog, where you can specify the cmake executable path. And add a class which runs cmake in the background to find out which version and wheter that cmake version has Qt Creator generator. (Which I did begin to write.)
-
- Jan 22, 2009
-
-
dt authored
-
- Jan 21, 2009
-
-
dt authored
Details: There's a linedit on there, we restore and save the settings, only thing missing is actually using it.
-
- Dec 09, 2008
-
-
dt authored
Task: - RevBy: - AutoTest: - Details: Note: I need to refactor the code significantly, i'm more or less convinced that one build configuration per target is wrong. We probably want one build configuration per build directory and instead build all targets that we are interested then in the makestep. This means we won't have any cmake support for the beta.
-
- Dec 04, 2008
-
-
dt authored
Details: Also add copyright headers and some initial code for the CMakeStep and MakeStep. Soon it will actially build something.
-
- Dec 02, 2008