Re: [ccmtools-devel] more environment stuff

[Leif J. <le...@am...>]

Hi again -

On Sat, 2004-01-03 at 10:17, Teiniker Egon wrote:
> I used the Christmas days to set up my own home network (xDSL, WLan and
> Ethernet). Hey, it's fun to use high speed internet access ;-)

Nice ! Welcome back from the stone age. :)

> > Over vacation I was thinking more about the CCM Tools environment files.
> > I came up with an idea(tm) : From a Unix perspective (small tools that
> > perform one task), the CCM Tools shouldn't even include environment
> > files. We ought to move all these environment files out of the ccmtools
> > source tree entirely. I started to move them into a different directory,
> > which I thought we could distribute separately, and include as a
> > separate CVS module ("cvs checkout environment", perhaps ?).
>
> I agree with you that separating environment libs from the ccmtools is the
> better approach (yes to both advantage 1 and 2).
> 
> About the disadvantages, I think that first installing the environment libs and
> then building the CCM-Tools is no problem. Until now, we have to call the
> install-environment scripts too.

Yes, excellent. I'm working on updating this as I write this email.
Unfortunately it's quite cold here, and my hard drive is being a bit
sluggish. :-/

> For testing, why do we need to install the environment libs again (and not using
> the existing installation)?
> Especially the remote environment (that contains the ORB) is not that flexible.

Yes, I meant that to run the _check_* tests, Confix will have to link
those tests with not only the site-installed environment libraries
(which might be installed under something like /usr or /usr/local), but
also the component libraries that are created in the
test/CppGenerator/sandbox/install/ directory.

Still, I think this problem is manageable. Having external environment
libraries might free us from a lot of painful checking for ORBs and
Python development files.

> > Another question about the environment files : Do we really need to have
> > all those separate directories for holding the source files ? Why not
> > put all the files in one directory, since they'll be compiled and
> > installed together ?
> 
> I think it is more clear to separate the source files in directories which
> reflect the source code's namespace structure and there is just one Confix call
> needed to build and install this stuff.
> But, if you really want to change this - why not ;-)

No, especially now since we'll be providing these files in a separate
CVS module, it would be a bit cleaner to have the directories. I also
agree with you that it's more helpful to have the namespaces as
directories.

So I'll get these environment files into a CVS module called
`environment'. It shouldn't be a problem at all.

leif