Re: [jamboost] Re: Simplify target path generation?

From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-10-22 10:42:30

Hugo Duncan wrote:
> --- In jamboost_at_[hidden], Vladimir Prus <ghost_at_c...> wrote:
> > David Abrahams wrote:
> > > > Or hash the directory name and only have something like:
> > > >
> > > > gcc/1234567/...
> >
> > The only problem with this is that target path stops being
>
> extremely long and
>
> > starts being expremely cryptic. I sometimes go to bin dir to look
>
> at
>
> > generated files, for example, and it would be nice to know which
>
> dir to look
>
> > at.
>
> Could you generate a hashed path by default, but allow the user
> to overide the generated name for a specific build?

That's a possible idea. I'm not sure that hashes paths are enough needed to 
implement them right now, though.

> Also, at least for me, the default usage is just to build a debug,
> release or profile version - so what are the issues with names like
>
> gcc/release
> gcc/debug

I.e. without "bin" and main target name. Well, "bin" is just a way to store 
all built products under one directory.

> I can see that might cause problems if you change the definition
> of the options used in a specific build.

Hmm... interesting question. The main target name is used to handle the 
situation when a target has some property which can't be represented
in path, e.g. free property. But this is only a problem is target can be built 
twice with different values of that free property. And if a target is used 
only by one main target, it's always built with the same properties.

Maybe, the main target name can be just removed from target path?

- Volodya