Re: [boost] Boost.Python win32 build/link problem (boost_1_27_0)

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-04-16 10:00:37

----- Original Message -----
From: "Pål Frogner Hansen" <pal_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Tuesday, April 16, 2002 9:20 AM
Subject: [boost] Boost.Python win32 build/link problem (boost_1_27_0)

> Question: To use boost.python, do I have to use the Jam thing? As
there were dsw-workspaces included I hoped I could just use these.
> Seemed to work, but I get linker errors.

Yes, those are outdated and will be removed in the next release.

> I have tried with python 2.0.1, 2.2.0 and 2.2.1 installed. Also tried
with vc6.0 and vc7.0. Building the example-project; both gives
> me the error-message below.
>
> What is wrong? Do I _need to_ use jam to build?

Yes, sorry, you do! We are trying to make this easier, and plan to
update the documentation shortly. In the meantime, I'll be happy to help
in any way I can.

Hints:

1. Get the version of jam that lives here:
http://groups.yahoo.com/group/jamboost/files/jam.exe
2. Boost.Build is designed to work three ways:

    a. You can call your vcvars32.bat to set up the compiler before
invoking jam; the build system will use the value of your MSVCDir
environment variable to figure things out

    b. You can explicitly prepare variables to indicate your
installation. This works better, for example, if you want to build with
both vc6 and vc7, since either one will set MSVCDir and the build system
wouldn't be able to distinguish.

    c. I think you can avoid setting up any variables if you have
allowed the installer to put everything in its default location.

I use method "b". I set up the relevant variables in a small .bat
script:

    rem myjam.bat excerpt
    set VISUALC=c:\tools\msvc6\vc98
    set VC7_ROOT=c:\tools\vc7
    jam %*

3. Be sure to use the latest CVS state of Boost; the build system and
Boost.Python have both improved reliability since the last release.

Good luck,
Dave