| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
Configure has very basic parsing of mkspecs where it traverses
includes, but assumes that the last seen value is the right one.
Since this parsing does not take scopes into account we can't
use tricks like isEmpty().
Reviewed-by: ossi
|
| |
|
|
|
|
|
|
|
|
|
|
| |
86636e0c4ab91bfb6 refactored the mkspecs, but didn't account for people
with their own mkspec who would still include g++.conf directly. We now
print a warning if this situation is detected, and explain to the user
how they can fix their mkspec.
For convenience we redirect g++.conf to g++-unix.conf so that people's
mkspecs will still work.
Reviewed-by: Marius Storm-Olsen <marius.storm-olsen@nokia.com>
|
| |
|
|
|
|
| |
Preparation for introducing Clang-style precompiled-header support.
Reviewed-by: Marius Storm-Olsen <marius.storm-olsen@nokia.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The g++ and llvm mkspecs now share the common parts in common/gcc-base.conf
Each top level mkspec includes a platform-specific version of this base,
either common/gcc-base-unix.conf or common/gcc-base-mac.conf, and these
platform specific bases will include the cross-platform one.
The same pattern is then used for the g++ specific configurations, which
are split up into common/g++.conf, common/g++-unix.conf and common/g++-mac.conf
The qplatformdefs.h for mac was also shared where possible.
The test in tests/manual/mkspecs was used to ensure that the final output
of all the mkspecs was the same after the refactoring as before.
Reviewed-by: ossi
|
| |
|
|
|
|
|
|
|
|
| |
the unix makefile generator can make files for "regular" unixes and
macos (the difference being the framework handling). so far, the output
choice was hard-wired to the host platform. the previous commit made
that soft-configurable, and this one exploits this capability to enable
limited cross-building.
Reviewed-by: mariusSO
|
| |
|
|
|
|
|
|
|
|
|
| |
The GCC-LLVM compilers on Snow Leopard have advanced enough
to make them worth the effort to make sure they at least work again.
These are the minimum changes needed to make things work. The current
gcc-llvm compilers on Mac OS X support Objective-C++ so, no need to
special case them anymore either. You STILL need to make sure your path
is correct however.
Reviewed by: Morten Sørvig
|
| |
|
