Re: [jamboost] Re: file vs. project hierarchy

From: sheila miguez (shekay_at_[hidden])
Date: 2004-12-29 15:59:36

On Wed, 29 Dec 2004 10:27:37 -0900, David Abrahams
<dave_at_[hidden]> wrote:
> 
> sheila miguez wrote:

> > Am I
> > constrained in how I organize my directory structure?
> 
> I don't think so.
> 
> > Is the toplevel
> > jam file the only one that depends upon file structure?
> 
> I don't think it depends upon file structure either, but maybe you have
> something specific in mind that I missed?

At this stage I am still ignorant enough that I probably didn't state
my question clearly, and I'm the one who missed something instead of
you.

I'm mixed up thinking about how bjam creates a map of the dependency
space (or the project space?), and of how it transform an element in
conceptual space onto the location in the physical space.

I'm trying to convert a big project over from our current primitive
build process to a bjam process. Our file structure is as follows:

/repos
/repos/proj1
/repos/proj2
/repos/proj3
...

projN will have sub projects, etc.

The build process I have to work with for now is rooted in

/repos/proj1/install/

which operates on everything. I don't like that, and want to relocate
it. I'm not sure if I am constrained by bjam conventions in where I
may locate it. Does it have to be at toplevel? and so on.

> > Here are the docs I'm studying.
> >
> > http://www.boost.org/doc/html/bbv2/tutorial/hierarchy.html
> > http://www.boost.org/doc/html/bbv2/advanced/jamfiles.html#bbv2.advanced.projects
> 
> FWIW, I have been cleaning up these documents. You might want to study
> the CVS sources for the latest state:
> 
> http://cvs.sourceforge.net/viewcvs.py/boost/boost/tools/build/v2/doc/src/
> 
> I can generate updated HTML from this, but significant explanatory
> content may be contained in XML comments that Volodya has yet to resolve
> into the main part of the document, so that won't show up.

I checked out the repos and will look at the changes.

I was reading through the online appendix and in
<http://www.boost.org/doc/html/bbv2/arch/targets.html#bbv2.arch.depends>
it reads,
"NOTE: THIS SECTION IS NOT EXPECTED TO BE READ! " and later, " The
remainder of this document is not indended to be read at all. This
will be rearranged in future."

er... Does this mean the section is inaccurate, organized poorly,
and/or merely not a compulsary read?

btw, is it better for me to work from a build made with CVS source instead?

-- 
sheila