Re: [Boost-bugs] [Boost C++ Libraries] #552: Building universal binary on MacOSX

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #552: Building universal binary on MacOSX
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2007-05-29 15:00:44

#552: Building universal binary on MacOSX
-------------------------------+--------------------------------------------
  Reporter:  shaishasag        |       Owner:  grafik     
      Type:  Support Requests  |      Status:  assigned   
 Milestone:                    |   Component:  build      
   Version:  None              |    Severity:  Showstopper
Resolution:  None              |    Keywords:             
-------------------------------+--------------------------------------------
Changes (by grafik):

  * component:  Building Boost => build
  * severity:  => Showstopper

Old description:

> {{{
> I'm using boost libraries on Windows (VC++) And MacOSX
> (gcc).
>
> Currently on MacOSX boost compiles for PPC processor.
> As Apple is moving to Intel processors, I would like to
> be able to compile boost, on the Mac for both PPC and
> Intel.
>
> Apple created the universal binary format, where you
> compile and link the code twice, the only difference in
> the compilation is a single option: -arch ppc or -arch
> i386.
>
> Later a tool called CreateUniversalBinary is called
> upon the linked codes. CreateUniversalBinary merges the
> two binaries into one. During runtime, the operating
> system loads the code and chooses which part to run,
> according to the local processor.
>
> I tried looking into the jamfiles but was overwhelmed
> by the complexity.
>
> What would be the best method to achieve universal
> binary on MacOSX?
> }}}

New description:

 {{{
 I'm using boost libraries on Windows (VC++) And MacOSX
 (gcc).

 Currently on MacOSX boost compiles for PPC processor.
 As Apple is moving to Intel processors, I would like to
 be able to compile boost, on the Mac for both PPC and
 Intel.

 Apple created the universal binary format, where you
 compile and link the code twice, the only difference in
 the compilation is a single option: -arch ppc or -arch
 i386.

 Later a tool called CreateUniversalBinary is called
 upon the linked codes. CreateUniversalBinary merges the
 two binaries into one. During runtime, the operating
 system loads the code and chooses which part to run,
 according to the local processor.

 I tried looking into the jamfiles but was overwhelmed
 by the complexity.

 What would be the best method to achieve universal
 binary on MacOSX?
 }}}

-- 
Ticket URL: <http://svn.boost.org/trac/boost/ticket/552#comment:2>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.