[Qt-interest] Just QMake
Girish Ramakrishnan
girish at forwardbias.in
Thu Jun 18 05:12:30 CEST 2009
I think he did mean to ask how to compile qmake easily :-)
The simplest way is to run configure, as Nathan suggested. If you want
to do it the harder way.
- cd into qmake and compile it with the Makefile.* present in the
directory. Before you start using the Makefile, you have to set the
variable in the makefile (listed in the top). And then, mingw32-make -f
Makefile.win32-g++ (subsitute Makefile.* appropriate for your compiler).
This is exactly what configure does, it is probably simpler to ^C after
it builds qmake :-)
Girish
Nathan Carter wrote:
>
> Or did you mean what's the fastest way to do it without building lots of
> other stuff?
>
> I know that ./configure builds qmake and nothing else, but it does also
> run qmake on a ton of .pro files, which takes a long time. You can pass
> --fast to ./configure to speed this process up significantly by just
> doing a superficial qmake pass on each .pro file, postponing most of the
> processing for later (in a step you'll never do if you just want qmake).
>
> Is that what you were looking for?
>
> Nathan
>
>
> On Jun 17, 2009, at 5:55 AM, Girish Ramakrishnan wrote:
>
>> Jason Todd Slack-Moehrle wrote:
>>> Hi All,
>>>
>>> QT 4.5.1 LGPL and OS X 10.5.7
>>>
>>> Can I take a fresh download of QT 4.5.1 LGPL and just build the QMake
>>> binary without having all the ./configure bloat, etc, etc. I just want
>>> the end result of the QMake binary and nothing else.
>>>
>>> Does anyone have thoughts?
>>>
>>
>> So you want to just use qmake for some non-Qt project and are worried
>> about the license? Looks OK to me. As I understand, commercial programs
>> can use the output of GPL/LGPL programs.
>>
>> Girish
>> _______________________________________________
>> Qt-interest mailing list
>> Qt-interest at trolltech.com
>> http://lists.trolltech.com/mailman/listinfo/qt-interest
More information about the Qt-interest-old
mailing list