Re: building Boost using Jam

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-05-10 08:02:14

"dmarsh26us" <david.marsh10_at_[hidden]> wrote in message
news:abg53b+d43p_at_eGroups.com...
> Can't really help but heres my two pennies worth anyway.
>
> You need to make sure certain symbols/environment variables exisit
> within you environment or edit the JAM file directly.

Do only the former, not the latter. These will all be documented for the
upcoming Boost release.

> These env vars tell jam where your compiler, headers, libs
> directories are.
> Don't know which version of boost jam you are using, the version I'm
> using does not support windows long file names with spaces

It does; you just have to quote them properly. The need for quoting will be
fixed in the upcoming boost release.

> so
> virtually all targets fail due to bad include paths, and I decided
> not to hack my VC installation just to let JAM build.

You can also use the "SUBST hack" to work around it: just map your vc
install directory to a top-level drive letter:

C:\boost\libs\python\test>SUBST /?
Associates a path with a drive letter.

SUBST [drive1: [drive2:]path]
SUBST drive1: /D

  drive1:        Specifies a virtual drive to which you want to assign a
path.
  [drive2:]path  Specifies a physical drive and path you want to assign to
                 a virtual drive.
  /D             Deletes a substituted (virtual) drive.

Type SUBST with no parameters to display a list of current virtual drives.

> You may have the same thing, I gave up and just used the parts of the
> library that only require headers. I still have stuff which won't
> build though, and don't even consider VC7!

I am building and testing successfully with VC6 and VC7.

-Dave