- Feb 01, 2010
-
-
Friedemann Kleint authored
QString: Use QChar where appropriate.
-
Tobias Hunger authored
* Use new BuildSteps interface (as seen in ProjectConfiguration). * Use new factory to construct/clone/restore them. Reviewed-by: dt
-
- Jan 13, 2010
-
-
dt authored
They do what you expect them to do, that is build only a subtree. The implementation is a little bit strange. We temporarly set the sub node to be built on the BuildConfiguration, enqueue that BuildConfiguration (which calls BuildStep::init()), and then reset that temporary value. A more general way would be to have the ability to extend BuildConfiguration::buildProject() in a way that additional data can be passed to the BuildSteps. Task-Nr: QTCREATOR-5 Task-Nr: QTCREATORBUG-44
-
- Jan 11, 2010
-
-
Tobias Hunger authored
Reviewed-by: thorbjorn
-
- Jan 07, 2010
-
-
Tobias Hunger authored
* Use id() for methods returning a string used to represent some type of object. * Use displayName() for strings that are meant to be user visible. * Quieten some warnings while touching the files anyway. * Move Factories to their products in the plugins where that was not done before. Reviewed-by: dt
-
- Dec 09, 2009
-
-
Tobias Hunger authored
* Rework IBuildParser: * Remove name() method. * Remove enterDirectory and leaveDirectory signals. * Allow chaining of parsers. * Rename IBuildParser to IOutputParser. * Implement GnuMakeParser. * Remove entering/leaving directory related code from all other parsers * Move filename fixup heuristic based on entering/leaving directory massages from gnumake here from AbstractMakeStep. * Add outputParser method to ToolChain: This removes the need to map toolchains to BuildParser names in the BuildSteps. * Enhance AbstractProcessStep to accept a IOutputParser to parse its output. * Remove AbstractMakeStep. * Set the appropriate Parsers in all classes deriving from AbstractProcessStep and append the ToolChain's parser to the parser chain. * Remove BuildParserFactories: There is no more need for them. * Remove constants used to identify the BuildParsers. * Clean up some names: * Replace stdOut with stdOutput. * Replace addToTaskWindow with addTask and addToOutputWindow with addOutput. Do this wherever it is not yet clear that this will end up in the Task/Output window. Reviewed-by: dt
-
- Dec 07, 2009
-
-
dt authored
Should fix a lot of corner cases, might introduce a few bugs. Also rename functions/slots to be better named. Generic Project Manager and CMake Project Manager are missing from this patch.
-
- Nov 30, 2009
-
-
dt authored
Also rename some methods/signal to make clearer that those only are relevevant for user changes not for all arguments.
-
dt authored
-
dt authored
-
dt authored
-
dt authored
-
dt authored
instead of a Project. Since BuildSteps "should" only care about the BuildConfiguration not the Project. (Not 100% doable, but still.)
-
dt authored
Note: I didn't fix all the connects and there are a few missing things. This compiles, more work is coming.
-
dt authored
The project() should in most cases not matter, instead the BuildConfiguration should. This shows all the information that needs to move into the BuildConfiguration classes.
-
- Nov 19, 2009
- Nov 12, 2009
-
-
Tobias Hunger authored
Rename BuildParserInterface to IBuildParser to comply with latest naming conventions. Reviewed-By: con
-
- Nov 09, 2009
-
-
Tobias Hunger authored
This is a initial version including * ABLD error parsing * RVCT compiler output parsing. Reviewed-By: con
-
- Oct 29, 2009
-
-
dt authored
Also ensure that Qt4ProjectConfigWidget does not emit any signals from it's init method.
-
- Oct 28, 2009
- Oct 21, 2009
-
-
dt authored
-
- Oct 01, 2009
-
-
con authored
Builds, but I'm pretty sure it doesn't *work* :)
-
- Sep 03, 2009
- Aug 14, 2009
-
-
hjk authored
-
- Aug 13, 2009
-
-
dt authored
-
Daniel Molkentin authored
-
Daniel Molkentin authored
-
dt authored
-
- Aug 12, 2009
-
-
dt authored
-
- Aug 06, 2009
-
-
dt authored
This has still a few missing things, but this enough to start getting some feedback. Missing are non qt projects, a solution for the runconfiguration, a missing black line between the treeview on top and the project settings at the bottom. Some flickering with removing/adding widgets to the QScrollArea and not showing the expanded widget if the Details button is right at the bottom.
-
- Jul 28, 2009
-
-
dt authored
Just one qmakestep is allowed though. But I you can add as many makesteps as you want.
-
- Jul 27, 2009
-
-
dt authored
-
- Jul 24, 2009
-
-
dt authored
-
- Jul 17, 2009
-
-
dt authored
Not finished 100%
-
- Jul 13, 2009
-
-
Alessandro Portale authored
There were both variants, with and without extra semicolon.
-
- Jun 24, 2009