Boost logo

Boost Users :

From: Sliwa, Przemyslaw (London) (Przemyslaw_Sliwa_at_[hidden])
Date: 2006-01-20 10:32:24

Thanks a lot for this.
I have a quick question - I would like to build the static library and
not the DLL.
Could you tell me what should be changed in the project apart form the
"General->static lib"?

Do you know how to disable the auto-link of boost?

Many thanks for help,


Kind regards



Przemyslaw Sliwa
Global Foreign Exchange

FX Risk Engine Development
Merrill Lynch
( +44 (0)20 7995 4182
) +44 (0)79 6325 2319
* Email: przemyslaw_sliwa_at_[hidden]

-----Original Message-----
From: boost-users-bounces_at_[hidden]
[mailto:boost-users-bounces_at_[hidden]] On Behalf Of Nat Goodspeed
Sent: 20 January 2006 14:35
To: boost-users_at_[hidden]
Subject: Re: [Boost-users] STL-PORT and VC 7.1

> -----Original Message-----
> From: boost-users-bounces_at_[hidden] [mailto:boost-users-
> bounces_at_[hidden]] On Behalf Of Sliwa, Przemyslaw (London)
> Sent: Friday, January 20, 2006 8:18 AM
> To: boost-users_at_[hidden]
> Subject: Re: [Boost-users] STL-PORT and VC 7.1
> I did not understand your statement properly -> did you create your
> VC 7.1 projects for the three libraries?

[Nat] Yes, using the IDE, we made new VC 7.1 projects, which I've
attached for you to review & modify to suit your own needs. (There's
already a libs/python/build/VisualStudio/boost_python.dsp file, which we
loaded into VC 7.1, implicitly converting it to .vcproj.) We created
them in


under the Boost main directory. (It's important to know where we put the
.vcproj files because we use .. in the projects' include paths. We do
that because the project file is checked into our version control
system, and we want people to be able to check out multiple copies in
different locations on their own machine and build each of them

The include paths reference $(STLPORTDIR), which you must set in the
environment. boost_python.vcproj additionally references $(PYTHONDIR),
which you must likewise set.

> Is this a standard procedure what people do when something is not
> working in boost?

[Nat] It's a standard procedure for when bjam produces build errors and
you don't even WANT to learn enough about its idiosyncrasies to try to
coax it. :-)

If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail.

Boost-users list run by williamkempf at, kalb at, bjorn.karlsson at, gregod at, wekempf at