Peter Prymmer <[EMAIL PROTECTED]> writes:
> The time has apparently come to get rid of the attempt to pass
> a list of extensions to build to the make_ext.com script.
> The enclosed patch introduces a new extensions.lis file to the
> main build directory and re-writes make_ext.com to use it
> in place of p1. I've also included a VMS portability patch for
> ext/Cwd/Cwd/xs.
>
> Are there any questions or comments on this approach? I thought I'd
> let vmsperl mull it over before I send into p5p + pumpkings.
Peter,
it's good that you're looking at this stuff!
I presume that you don't want to have make_ext.com get the
list of extensions from config.sh because of DCL symbol length
limitations....otherwise it would be better to use config.sh
and not have config information duplicated in extensions.lis.
But the list of extensions has to fit in a single DCL symbol (length
<1024 IIRC) because that's what we use to store the list in
configure.com before writing it to config.sh, and the same symbol is
then used for writing to extensions.lis.
However, looking at [.vms]munchconfig.c and ConfigPM., it seems that we
can split long config.sh symbols:
blah="stuff stuff stuff stuff
morestuff morestuff morestuff"
Although I rather doubt that munchconfig's capabilities have been tested
WRT split config.sh lines (and it probably needs to use malloc'd strings
rather than fixed buffers to avoid length limits), this does seem to
provide a way to keep individual lines of config.sh within bounds, yet
store a long list of extensions.
My suggestion is to have the take the list of extensions (stored in
multiple DCL symbols) to generate multi-line config.sh entries. Then
have make_ext.com read config.sh for the list of extensions to build.
--
Drexel University \V --Chuck Lane
======]---------->--------*------------<-------[===========
(215) 895-1545 _/ \ Particle Physics
FAX: (215) 895-5934 /\ /~~~~~~~~~~~ [EMAIL PROTECTED]
