Boost logo

Boost-Build :

Subject: Re: [Boost-build] setup the environment variable correctly on OS X 10.4
From: Michael Jackson (mike.jackson_at_[hidden])
Date: 2009-04-02 10:37:33


If you plan on distributing your application I would also recommend
that you build static libraries which will avoid the eventual use of
"install_name_tool" and all the "fun" that brings with it.

Here is the command that I use to build boost:

bjam toolset=darwin --with-test --with-filesystem --with-
program_options --with-iostreams --with-thread variant=release,debug
threading=multi link=static runtime-link=shared --prefix=/Users/Shared/
Toolkits/boost-1_36/ architecture=combined install

Note that I am only asking for certain libraries to be installed. If
you are using the latest boost and boost.build then you can also add
the --address-model=32_64 to create Quad binaries if you need/want
those.

In my bjam from above I would set BOOST_ROOT=/Users/Shared/Toolkits/
boost-1_36

_________________________________________________________
Mike Jackson mike.jackson_at_[hidden]
BlueQuartz Software www.bluequartz.net
Principal Software Engineer Dayton, Ohio

On Apr 2, 2009, at 10:28 AM, norman wrote:

>
> Thanks for the replies, I will enquiry on the cmake list.
>
> When running bjam from the root of the boost_1_38, like:
>
> $ bjam --toolset=darwin --with-python --prefix=/usr/local --
> undefined=-Wl,-flat_namespace,-undefined,dynamic_lookup --
> compatibility_version=1.38.0 --current_version=1.38.0 --build-
> type=complete
>
> Is this the correct way to install boost?
>
> --- On Thu, 2/4/09, Michael Jackson <mike.jackson_at_[hidden]>
> wrote:
>
>> From: Michael Jackson <mike.jackson_at_[hidden]>
>> Subject: Re: [Boost-build] setup the environment variable correctly
>> on OS X 10.4
>> To: "Boost.Build developer's and user's list" <boost-build_at_[hidden]
>> >
>> Date: Thursday, 2 April, 2009, 3:45 PM
>> You need to set BOOST_ROOT to the
>> directory where boost was installed. Looks like on your
>> system this might be /Users/khinester/Installed which
>> is kinda odd but worth a try.
>>
>> You may also want to inquire on the cmake mailing list
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.cmake.org/mailman/listinfo/cmake
>>
>> _________________________________________________________
>> Mike Jackson
>> mike.jackson_at_[hidden]
>> BlueQuartz Software
>> www.bluequartz.net
>> Principal Software Engineer
>> Dayton, Ohio
>>
>>
>>
>> On Apr 2, 2009, at 8:12 AM, Vladimir Prus wrote:
>>
>>> On Thursday 02 April 2009 13:25:23 norman_khine_at_[hidden]
>> wrote:
>>>
>>>> But when I try to setup Wt, using the http://www.webtoolkit.eu/wt/wiki/index.php/Installing_Wt_on_Mac_OS_X_Leopard
>>>>
>>>>
>>>> $ cd ~/sandboxes/wt/
>>>> $ rm -rf build
>>>> $ mkdir build
>>>> $ cd build
>>>> $ cmake
>> -DBOOST_DIR=/Users/khinester/Installed/include ../
>>>> ..
>>>> ** Error finding Wt required library:
>>>> ** Could not find a boost installation in
>> /Users/khinester/Installed/include.
>>>> ** It may be necessary to set appropriate values
>> for the
>>>> variables BOOST_DIR,
>> BOOST_COMPILER, and BOOST_VERSION
>>>
>>> Did you set BOOST_COMPILER and BOOST_VERSION per
>> whatever instructions that project
>>> provides? Are you sure BOOST_DIR should point at
>> include directory, and not one
>>> level up? Further, it appears they implemented their
>> own solution for finding
>>> boost libraries in CMake, rather than using standard
>> one.
>>>
>>> I am afraid you have to ask Wt folks what to do here.
>>>
>>> - Volodya
>>> _______________________________________________
>>> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
>>
>> _______________________________________________
>> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
>>
>
>
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build


Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk