Re: Recompiling?

[Simon Wright <simon@pushface.org>]

Martin Krischik <krischik@users.sourceforge.net> writes:

> Harald Korneliussen wrote:
>
>> There's another pretty basic question I want to ask, about the
>> correct and portable way to install something like the Booch
>> components as a shared library. The package is just a bunch of
>> source files. I suppose I could copy them to every project that I
>> use booch on, but that seems so unclean and wasteful.

I can see your point, though (here) the BC's Ada library directory
seems to be about a megabyte; most of the cost comes in the
instantiations. That would be different for a non-generic library, of
course.

> AdaCL (adacl.sf.net) has an appropriate .gpr for the booch
> components. Just look into the Script directory for bc.gpr.

It's appropriate if you buy in to the AdaCL view of directory
structures, options etc. Not that that's a bad thing, Martin has done
a great job here!

I had real trouble understanding how to deal with library projects in
GPRs, and (as far as I can remember) there was a problem with VxWorks
anyway last time I looked (or was it Linux?). That would have been at
3.16a1, and we do not have support for Linux. So I've always been
content with a plain subproject; this is what I use for ColdFrame
(coldframe.sf.net):

   with "Options";

   project BC is

     --  You must define the top node under which software is installed:
     --  for example, "/usr/local/lib"
     Top := external ("TOP");

     --  You must define where under TOP the BCs are installed; for
     --  example, "bc-20030111"
     BC := external ("BC");

     for Source_Dirs use (Top & "/" & BC);

     for Object_Dir use Options'Object_Dir & "/bc";

     package Ide renames Options.Ide;

     package Builder renames Options.Builder;

     package Compiler renames Options.Compiler;

     package Binder renames Options.Binder;

     package Linker renames Options.Linker;

   end BC;

but you can see that it's only intended for source inclusion --
amongst other things it assumes that each user project will have its
own view of the standard Options.