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

From: sheila miguez (shekay_at_[hidden])
Date: 2004-12-30 10:30:00

On Wed, 29 Dec 2004 15:22:19 -0600, Rene Rivera
<grafik.list_at_[hidden]> wrote:

> >>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.
> >
> > What is "it?" A process isn't normally spoken of as being rooted in a
> > directory.

Right. The stuff in the directory isn't the process, it's just a bunch
of scripts used to make builds. There isn't much of a process where I
am right now, just the concept of making builds and vaguely keeping
copies of them somewhere. My former job had a really tight and nice
build process, but then, they'd had time to work out most of the kinks
and had a lot more resources available to them. The place I recently
joined has a lot more constraints, &c. I probably won't be able to
work out the ideal process since I'll invariably end up working on
development. typical trade offs.

> I believe that Sheila meant "it" to be the BBv2 project that references
> the various /repos/projN, and hence the Jamfile/Jamroot. The project/ID
> location independence you describe makes the answer: There's no
> restriction. One could place the Jamfile/Jamroot anyplace and refer to
> other projects (Jamfiles) without regard to actual directory location.

Thanks. This clarifies things.

-- 
sheila