RE: [jamboost] Some fundamental misunderstandings (v2)

From: Mark Elston (m.elston_at_[hidden])
Date: 2004-06-15 14:18:41

Thanks for the info.

Responses inline.

Mark

> -----Original Message-----
> From: Vladimir Prus [mailto:ghost_at_[hidden]]On Behalf Of Vladimir
> Prus
> Sent: Tuesday, June 15, 2004 12:21 AM
> To: jamboost_at_[hidden]
> Subject: Re: [jamboost] Some fundamental misunderstandings (v2)
>
>
> Mark Elston wrote:
>
> > I then cd'd into the example/libraries directory and ran bjam
> > without any parameters. Everything seemed to build just fine
> > except I got the following three lines in the build output:
> >
> > warning: using independent target <lib1/msvc/debug>lib1.dll
> > warning: using independent target <lib1/msvc/debug>lib1.rsp
> > warning: using independent target <app/msvc/debug>app.rsp
>
> In the current version I see only one of those warnings. Anyway,
> gotta remove the last one too.

I have been having trouble getting the CVS stuff. I get timeout
errors trying to connect. I will keep trying.

How have you fixed this? Have you been modifying the tools/msvc.jam
file? Or is it someplace else? I am curious about this because I would
like to see how these kinds of changes are made. It would help me
understand how this product is put together.

>
> > Another issue is that we would like to provide a "common" build
> > environment for all the developers on a project to use. Rather than
> > tell them "get the boost-build package and build it, ..." we would
> > like to put together a pre-built binary with bjam and all its supporting
> > files. What would that list of files include. I assume there is some
> > set of the directories under the boost-build directory that must be
> > available when using bjam. However, I cannot find any documentation
> > that says "here is what you need in your environment". I assume you
> > don't need the jam-src, example, or doc sub-directories. Which, if any,
> > of the other directories do you need?
>
> You don't need: "debian", "doc", "example" and "test" and you
> need everything else.

Thanks.

>
> BTW, the boost-build.jam file mentioned in the "Installation" section of
>
> http://boost.org/boost-build2/boost_build_v2.html
>
> can be quite handy for a project. It can give the path to a "official" V2
> installation location, so that developers don't have to set
BOOST_BUILD_PATH
> in environment.
>

I expect we will put all the required stuff in a subdirectory in Perforce
and, at the top of our project, we will put a custom boost-build.jam file
with
the relative path to the 'actual' location. That should make things pretty
easy for our developers.

> - Volodya
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>