On quinta-feira, 23 de agosto de 2012 01.40.00, Holger Hans Peter Freyther >
In fact in Yocto/Poky we are using a custom mkspec that allows us to target
> 7 different CPU architectures. I would be very happy if Qt would use
> autoconf (and pkg-config) for the configuration step on Unix/Posix (it
>
On Mon, Aug 20, 2012 at 11:22:29AM -0700, Romain Pokrzywka wrote:
> On Sunday, August 19, 2012 11:51:05 AM Peter =?ISO-8859-1?Q?K=FCmmel?= wrote:
Hi,
adding my two cents here as well. There is and should be nothing special
about cross-compiling. With sane systems the only difference between nativ
On Sunday, August 19, 2012 11:51:05 AM Peter =?ISO-8859-1?Q?K=FCmmel?= wrote:
> Here a proposal:
> 1. -target-mkspec : specify mkspec name
> 2. -target : specify toolchain prefix
-toolchain-prefix sounds much more appropriate than -target (which to me means
the target hardware platfo
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*
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
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
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
