vincent wrote: >Hi there, > >in the course of preparing a suitable Portfile to integrate Qt 4.5.0 >bt1 into Macports, I ran into a build error. The cause is simple: some >objc primitives used by Cocoa are not allowed in MacOS X 10.4 and the >compiler produces an error if the flag -mmacosx-version-min is not set >to 10.5, which happens to be the case if I compile for both x86_64 and >i386 at the same time (the latter sets the option to 10.4)
That's correct. The Cocoa port of Qt requires MacOS X 10.5.
That does not affect the Carbon port. It can still build with a target of
10.3 (even though it has to be compiled on a Tiger or a Leopard).
>If the corresponding template in mkspecs/common/mac-g++.conf is
>updated, the build runs fine.
>
>The solution seems to be the use of a single -mmacos-version-min set
>to the max of all values (10.3 for ppc, 10.4 for i386 and 10.5 for 64
>bit builds).
Hmm... so you're saying we should have -mmacosx-version-min set to 10.5 by
default, so that a full universal build will work out of the box?
>Something else: when lauching (for testing purposes) Designer, I
>briefly enter X11 before Designer UI sets up. It is thereafter safe to
>quit X11, even while running Designer, which proves that the
>application does not rely on X11, but I wonder why this glitch.
Qt on Mac should not link to the X11 libraries. So this is really weird.
Any chance you can investigate further? It is probably some third-party
library that got loaded by mistake (or built by mistake in X11 mode).
--
Thiago Macieira - thiago.macieira (AT) nokia.com
Senior Software Engineer - Nokia, Qt Software
Qt Software is hiring - ask me
Sandakerveien 116, NO-0402 Oslo, Norway
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Qt4-preview-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback
