> Were you able to incorporate any of the work that Dave Marker did on this?
> As I recall, he had libraries building with a non-recursive make system,
> and did so quite fast.
I haven't seen Dave Marker's work on this -- nor am I sure this is
related -- but I mentioned to Sasha (Alexender Kolbasov) another
idea that Jonathan, Rod Evans and I were kicking around, as covered
in Jonathan's Evaluation for:
4631488 lib/Makefile is too patient: .WAITs should be reduced
Make the library build two-phase. During the first phase, "dummy"
libraries would be created from the information in the spec files, and
installed in some central location. In the second phase, everything
would be built in parallel, but would link against the "dummy"
libraries.
It looks like we've got almost everything we need already, except for
exported data. We would have to add a 'definition' line for each such
element. Then:
1. use spec2map -F to generate the "filter" version of the mapfile,
mapfile.dummy
2. process all of the 'data' entries in the spec file, and generate
a .c file containing all of the data definitions.
3. Compile the .c file, then link it with -M mapfile.dummy, to generate
libfoo.so.1.dummy
4. install libfoo.so.1.dummy as '$(DUMMYDIR)/libfoo.so.1', and add the
'libfoo.so' symlink.
(The reason you need the data definitions and the .c lines is to get
the data sizes correct)
Note that this Evaluation was written back when we had specfiles, but I'm
sure we could do something similar (and perhaps simpler) with mapfiles.
Again, I inherited 4631488 from Jonathan but haven't had time to work on
it. If others are ready and able, I'm happy to hand it off.
--
meem
_______________________________________________
tools-discuss mailing list
[email protected]