Commit Graph

96 Commits

Author SHA1 Message Date
Tobias Hunger
2bba8353ca Do not warn on ':' in symbian project names
... if it is part of the drive letter only.
2010-04-19 11:54:46 +02:00
dt
a1f7e462cd Remove debug output 2010-04-12 17:27:03 +02:00
Tobias Hunger
8cf30e86df Allow overriding the return value of abstractprocessstep::run
This is needed to enable additional checks on the result.

Reviewed-by: dt
2010-04-09 18:04:22 +02:00
Alessandro Portale
be0abf3cff Case insensitive drive comparision: Symbian SDK vs. project sources.
If SDK and Project were on te same drive but for some reason the drive
in the pathes had different cases, we had false alarms.

Made the comparision case insensitive as agreed with Tobias.

Reviewed-by: Tobias Hunger
2010-04-08 21:36:22 +02:00
Alessandro Portale
50b70d769b Fixed detection of /epoc32/include/stdapis/string.h
It was searched in /include/stdapis/string.h

Added the /epoc32/ as agreed with Tobias.

Reviewed-by: Tobias Hunger
2010-04-08 21:36:22 +02:00
kh1
1c31ff98a0 Fix "broken" qmake call on OSX for maemo.
Tested on OSX, otherwise qmake will automatically append -macx which
results in Makefiles containing references to the host Qt libraries,
e.g. -lQtCore_debug etc...

Reviewed-by: dt
2010-04-07 17:34:34 +02:00
Tobias Hunger
b47d279bc3 Do sanity checks when running qmake
* Check for symbian SDK and soureces being on the same drive on windows
 * Check for a Open C/C++ header in Symbian SDK and warn if that is not found
 * Check for chars in project name that might confuse symbian SDKs

Task-number: QTCREATORBUG-1045
Task-number: QTCREATORBUG-1043
Reviewed-by: dt
2010-04-07 16:06:48 +02:00
dt
0d4fdd291a Use a type enum instead of duplicating functions between build and clean
That is e.g. buildSteps() and cleanSteps() --> steps(type)
2010-03-16 17:45:08 +01:00
hjk
9595504bda Long live the king! 2010-03-05 11:28:13 +01:00
Friedemann Kleint
f87f421011 tr()-Fixes 2010-02-25 17:15:30 +01:00
dt
3c99f02bcb Rename QMake to qmake since that's the official spelling. 2010-02-17 16:54:50 +01:00
Tobias Hunger
261966dbb7 Have qmakestep trigger the import label
* Do not use the BuildManager but have the qmakestep trigger
   the update via the target and project.

Reviewed-by: dt
2010-02-16 13:18:25 +01:00
Tobias Hunger
d1bdfcc363 Integrate target support
* Ease cross device development by introducing 'targets' which
   group build- and runsettings that are valid for this one target

 Most of the kudos for the code review go to dt. Con, thorbjorn,
 ckandler and others did also review parts of this patch.

Reviewed-by: dt
2010-02-09 16:57:37 +01:00
Tobias Hunger
1726688434 Make use of ProjectConfiguration class in BuildSteps
* Use new BuildSteps interface (as seen in ProjectConfiguration).
 * Use new factory to construct/clone/restore them.

Reviewed-by: dt
2010-02-01 12:23:12 +01:00
dt
fb3ae97df3 Add Build to the right click menu of sub projects for Qt4 Projects
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
2010-01-13 18:02:22 +01:00
dt
b560e24034 Fix that changing qmake arguments did not update the import label
Task-Nr: QTCREATOR-269
2010-01-12 17:21:20 +01:00
dt
e3188417c3 Don't silently reset the qt version if it has become invalid
Instead note that it is invalid if trying to build and on the projects
mode pane.

Task-Nr: QTCREATORBUG-459
2010-01-12 15:51:11 +01:00
Tobias Hunger
a6ad773722 Make method naming more consistent.
* 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
2010-01-07 18:17:24 +01:00
Tobias Hunger
ec025c6dbf Rework Build Parser handling
* 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
2009-12-09 18:39:03 +01:00
dt
1e46cb424e Rework connections on the project pane for Qt4Projects.
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.
2009-12-07 15:00:17 +01:00
con
f3bdeb8c9a Share the code for determining used qmake arguments.
Move the code that compares the Qt version's debug|release property
with the build configuration's debug|release property
to the new build configuration class.

Reviewed-by: dt
2009-12-02 18:16:34 +01:00
dt
3565fe4e82 Fix always to end of line jumping cursor in MakeStepConfigWidget
Also rename some methods/signal to make clearer that those only are
relevevant for user changes not for all arguments.
2009-11-30 19:33:14 +01:00
dt
2de390cfdb Move QMakeParser to Qt4ProjectManager 2009-11-30 19:33:14 +01:00
dt
994f8d5fbf Don't allow adding a second qmakestep 2009-11-30 19:02:16 +01:00
dt
16fcb82d08 Fix signal names and also ensure that we don't reset the cursor position 2009-11-30 17:21:59 +01:00
dt
5fc8324b8b compile on windows 2009-11-30 15:59:27 +01:00
dt
01ce6f0e2e Rebase is bad 2009-11-30 15:43:17 +01:00
dt
9984944171 Fix compile 2009-11-30 15:24:32 +01:00
dt
d6d48fa23c Some cleanup after BuildConfiguration refactoring 2009-11-30 15:24:32 +01:00
dt
cff2c1df6d QMakeStep some API cleanup
Rename arguments to allArguments(), qmakeArguments() to userArguments()
2009-11-30 15:24:32 +01:00
dt
fb1ef427a0 Remove setValue/value from Project 2009-11-30 15:24:32 +01:00
dt
592c1fba65 Fix signal broken in the porting to new buildconfiguration 2009-11-30 15:24:32 +01:00
dt
801e9948f5 Hide static cast in accessor methods 2009-11-30 15:24:32 +01:00
dt
d9a1769542 Remove unneeded code 2009-11-30 15:24:32 +01:00
dt
4c28a2ea0c Fix connects, the signal moved 2009-11-30 15:24:32 +01:00
dt
0e4e35f876 Rename method to the more correct canCreateForBuildConfiguration 2009-11-30 15:24:31 +01:00
dt
a7a7e4d002 Change IBuildStepFactory::canCreate to take a BuildConfiguration
instead of a Project. Since BuildSteps "should" only care about the
BuildConfiguration not the Project. (Not 100% doable, but still.)
2009-11-30 15:24:31 +01:00
dt
a312206306 Move most of the BuildConfiguration specific functions
Note: I didn't fix all the connects and there are a few missing things.
This compiles, more work is coming.
2009-11-30 15:24:31 +01:00
dt
60a1ee12ba Remove project() from BuildStep
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.
2009-11-30 15:24:31 +01:00
dt
0d162be22f Make BuildSteps one instance per BuildConfiguration
Enables users to change which buildsteps get run per buildconfiguration.
Some further tweaks are probably necessary. This is a rather big
change, though it should work. :)
2009-11-19 16:36:48 +01:00
dt
72fe54db77 Remove value(name) and setValue(name, value) from BuildStep 2009-11-19 16:35:19 +01:00
dt
0fa60aa3d8 Use QFlags<> for QmakeBuildConfig that removes a few casts. 2009-11-19 16:35:19 +01:00
dt
6ff99e056d Fix calling the wrong base class 2009-11-16 13:01:48 +01:00
Tobias Hunger
d151493acc Add buildparser for the QMake step
Add an option to have a buildparser for the qmake step and implement
a pretty simple parser.

Reviewed-By: dt
2009-11-12 09:04:18 +01:00
dt
75e23cc58f Fix -spec handling 2009-11-10 13:29:13 +01:00
dt
7dc399d678 Fixed the check for whether there already is a -spec parameter 2009-10-30 18:41:55 +01:00
con
3e81572b8a Merge commit 'origin/1.3' 2009-10-30 17:22:01 +01:00
dt
4798ec5529 On qt version change updat qmakestep config widget
That is the effective qmake command and summary label.
2009-10-29 19:42:56 +01:00
kh1
efa44fa5c1 Return <default> if we can't find out the mkspec name. Overwrite mkspec
in case one has set MAKESPEC but does not actually pass it as argument.

Reviewed-by: dt
2009-10-26 15:57:30 +01:00
dt
cfc7040ede The qtversions's toolchain now depends on the actual compiler not mkspec
That is we actually parse the mkspec and evaluate QMAKE_CXX (and a few
other variables) to figure out the correct mkspec. This makes using
custom mkspecs easier and is also cleaner. I also changed mkspec() and
mkspecPath() to behave a little diffrent, essentialy mkspec() will
return only the name (the actual dir name) of the mkspec. That is in
general not sufficient for passing on to qmake. mkspecPath() only
returns the correct path to mkspecs/default.
Hopefully I haven't broken WinCE/Maemo/MinGW.
2009-10-22 14:39:00 +02:00