Changes between Version 5 and Version 6 of UniversalDevelopment


Ignore:
Timestamp:
Apr 7, 2014, 2:33:17 PM (5 years ago)
Author:
cooljeanius (Eric Gallager)
Comment:

Give more examples and descriptions of how and when to use these different universal building methods

Legend:

Unmodified
Added
Removed
Modified
  • UniversalDevelopment

    v5 v6  
    22
    33=== Approaches ===
    4  * Adding the universal build flags (''-arch ppc -arch ppc64 ..'') to the compiler flags: Suited for straight compilation of executables
    5  * Adding universal build flags to the CFLAGS etc.: Suited for certain autotool driven builds
     4 * Adding the universal build flags ("-arch i386 -arch x86_64 ...") to the compiler flags (i.e. the "CC" environment variable itself): Suited for straight compilation of executables. This is usually done for hand-written Makefiles and often has to be done manually from the Portfile. For example, if the `build.cmd` is `make`, the code in the Portfile would look something like this:
     5{{{
     6build.args-append CC="${configure.cc} [get_canonical_archflags cc]"
     7}}}
     8 You could also try setting it in `build.env`, but sometimes `make` does not respect environment variables if that variable is not also used as a Makefile variable, so it is safer just to force it in `build.args`.
     9 * Adding universal build flags to the CFLAGS etc.: Suited for certain autotools-driven builds. This is done by default. The default values for these universal flags vary by platform. On Tiger on PowerPC, they are:
     10{{{
     11configure.universal_cflags -isysroot ${developer_dir}/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc
     12configure.universal_cppflags -isysroot ${developer_dir}/SDKs/MacOSX10.4u.sdk
     13configure.universal_cxxflags -isysroot ${developer_dir}/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc
     14configure.universal_ldflags -Wl,-syslibroot,${developer_dir}/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc
     15}}}
     16 On Tiger on Intel and on Leopard, they are:
     17{{{
     18configure.universal_cflags -arch i386 -arch ppc
     19configure.universal_cxxflags -arch i386 -arch ppc
     20configure.universal_ldflags -arch i386 -arch ppc
     21}}}
     22 On Snow Leopard and later, they are:
     23{{{
     24configure.universal_cflags -arch x86_64 -arch i386
     25configure.universal_cxxflags -arch x86_64 -arch i386
     26configure.universal_ldflags -arch x86_64 -arch i386
     27}}}
     28 The exception is `configure.universal_args`, which has the same default across platforms:
     29{{{
     30configure.universal_args --disable-dependency-tracking
     31}}}
    632 * Adding universal build flags to the libtool command e.g. `reinplace "s|CC -dynamiclib|CC -dynamiclib ${configure.universal_ldflags}|g" ${worksrcpath}/libtool`
    7  * Separating builds for different architectures, merging the different (single-arch) destroots: See the muniversal portgroup (emulation or multiple build machines differing in arch may be necessary for some ports)
    8 
     33 * Separating builds for different architectures, merging the different (single-arch) destroots: See the [browser:trunk/dports/_resources/port1.0/group/muniversal-1.0.tcl muniversal PortGroup] (emulation or multiple build machines differing in arch may be necessary for some ports). This is useful in various different situations:
     34  - When the port tries to use the `--enable-dependency-tracking` configure flag anyways, which makes building normally result in an error like this:
     35{{{
     36gcc-4.2: -E, -S, -save-temps and -M options are not allowed with multiple -arch flags
     37}}}
     38  - When the build system tries to put a fat archive inside another archive, resulting in an error like this:
     39{{{
     40/opt/local/bin/ranlib: archive member: libtcs.a(libtddl.a) fat file for cputype (16777223) cpusubtype (3) is not an object file (bad magic number)
     41}}}
     42  (this works when the archive is '''not''' fat)
     43  - When the build system has architecture-specific assembly, or otherwise builds files differently based on architecture.
    944
    1045=== Developers ===