Ludovic Brenta пишет:
>> BTW, is gprbuild publicly available?
>
> TTBOMK, not yet; it was announced in September and probably released
> only as part of wavefronts of GNAT Pro to customers. It should
> surface as part of GNAT GPL 2008 Edition and, maybe, GCC 4.4 or later.
>
> OTOH, I was not talking about gprbuild. I was talking about gprmake,
> which has been part of GCC since 4.0 and is publicly available.
> gprmake handles multi-language projects just fine, thank you very
> much.
OK, it seems to be available to the wide public in the future. I've just
remembered that I have downloaded a nightly build of GPS 4.3.0w in
December, 2007. gprbuild is present there! And its documentation is
present too.
I have published it on
http://octagram.gorodok.net/gprbuild/gprbuild_ug.html
FYI.
Google can't find gprbuild_ug.html on any other website.
No mysteries anymore. Now I can see what does gprbuild pretend to be.
> GPRbuild manages a three step build process
>
> * compilation phase
>
> * post-compilation phase (or binding)
>
> * linking phase
The whole idea looks good for me, but... what if I'll want once in a
blue moon to use, for instance, gnatelim? Or maybe I would like to use
"C++ headers => GCCXML => XSLT => thin Ada bindings" scheme? The problem
I see here is that gprbuild aids simple building processes, but when one
needs something beyond this scope one seems to have to deal with gpr
projects and their extensions on his own. Locate files, compute flags,
etc. Let's locate files at least. Can gprbuild's ability to locate files
be "exported"?
I'm not sure if it's worth jumping on gprbuild. I think other Makefile
replacements & additions are worth to be reviewed. Jamfile is one of the
most visible ones.
--
If you want to get to the top, you have to start at the bottom
|
