Qt could be compiled native or cross for a system
different to the system on which Qt is build.
But this is not how mkspecs/ is organized:
linux-*native
win32-*native
wince* cross
unsupported/* cross and native
device/* cross
also configure supports different opti
On domingo, 19 de agosto de 2012 11.51.05, Peter Kümmel wrote:
> Therefore I propose to cleanup this before the 5.0 release.
Sorry, I oppose this.
You can clean it up, but not before the 5.0 release.
I'd actually prefer that you clean this up *after* we switch buildsystems,
whenever that happens
On Sun, 19 Aug 2012 12:00:25 +0200
Thiago Macieira wrote:
>
> I'd actually prefer that you clean this up *after* we switch buildsystems,
Ahhh! :)
> whenever that happens. Cleaning up configure is an unnecessary task if we're
> going to throw it away soon after.
>
> Please keep changes to the
We still need to figure out how to handle the changes file(s). I think we do
need one for each module, and then we simply aggregate that into the top-level
Qt directory on release generation. Also, since we want to also be able to
release modules independently, this would be required.
Question
I prefer use qbs instead of qmake.
qbs is a great build suite.
2012/8/19 Peter Kümmel
> Qt could be compiled native or cross for a system
> different to the system on which Qt is build.
>
> But this is not how mkspecs/ is organized:
>
> linux-*native
> win32-*native
> wince*
