[Qt-creator] patch for improving cmake support with mingw

[Antoine Requet]

Hello,

I haven't used qtcreator very much now, but it looks like the cmake
support is already quite functional. Maybe I'll encounter more issues
when I'll use it more, but for now it seems that everything is working
well once the project is configured.

A feature that I think would be useful would be to provide a way of
adding the mingw and qt binary path to the environment before running
cmake, so that they can be detected by cmake. In my case, this would
be very useful, as I don't have a default qt or mingw accessible from
my PATH environment variable, since I use the PATH variable to choose
which qt version will be detected.
An ideal solution for this would be to use the existing Qt options or
to allow defining cmake profiles that could be chosen before running
cmake.

Antoine

2009/3/10 Daniel Teske <daniel.teske at nokia.com>:
>>
>> I have tried to use qtcreator's support for cmake under windows/mingw,
>> and I have encountered the following problems:
>>  - the generator uses the "CodeBlocks - Unix Makefiles" generator.
>> However, this generator does not works under windows, so an empty
>> project is opened in qt-creator
>>  - when starting a build, the plugin tries to launch "make". The
>> default make that is included in mingw is "mingw32-make"
>>
>> The attached diff uses #ifdef Q_OS_WIN to replace "CodeBlocks - Unix
>> Makefiles" and "make" by "CodeBlocks - MinGW Makefiles" and
>> "mingw32-make" under windows, which seems to fix the problem.
>> There is also a fix for an uninitialized member variable in makestep.cpp.
>
> Thanks, note though that I obviously don't test it on windows at the moment.
> And all of it is rather alpha quality at the moment.
> If you have any feedback what is most needed for you, I'd be interested in
> that.
>
> daniel
> _______________________________________________
> Qt-creator mailing list
> Qt-creator at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>