#216 universal binary switch in fink.conf

open
nobody
None
5
2007-02-12
2007-02-12
No

It would be nice to have a switch available in fink.conf to build universal binaries. This would be helpful in cases when building an app outside of Fink that uses Fink derived libraries and one wishes to release it as a universal App.

In cases where the Arch: field includes only 1 architecture, then the universal switch would be ignored and only the specified architecture would be built.

Related

Feature Requests: #239

Discussion

  • Hanspeter Niederstrasser

    Logged In: YES
    user_id=927770
    Originator: YES

    This might actually work better as a flag used during 'fink build' to signal which architecture(s) to build. It would of course default to the architecture of the local system.

     
  • Hanspeter Niederstrasser

    Logged In: YES
    user_id=927770
    Originator: YES

    Another possibility, especially since many packages can't be built directly as universal and there's no universal :) way to build multi-arch binaries across different build tools would be to have 1) a flag in fink.conf that says whether to try to build universal and 2) a new field in the .info file that a package maintainer would use to describe how to make the build universal. Something like:

    BuildUniversal: <<
    CFLAGS="-isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc"
    LDFLAGS="-Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk -arch ..."
    ./configure %c
    etc etc
    <<

    This way everything wouldn't be trying to default to universal and would only do it iff the package maintainer had done the work to test it out. No "BuildUniversal" field (default) -> no universal builds. fink.conf setting on "off" (default) -> no universal builds.

    This could even be set up to have a few predefined versions, so that different packages that use e.g. autotools would all look the same if the package maintainer decides that it works and uses the predefined autotools standard values for BuildUniversal:.

    I don't know how to work around dpkg not knowing about multi-arch files, so that makes most of this moot, but figured I'd write it down anyway.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks