Am Dienstag, 5. September 2006 00:54 schrieb Leopold Toetsch: > most[1] of ... > > > build/tools/dynpmc.pl > > ... should go away in favor of standard Makefile rules
That answer was probably a bit too terse. Here are my thoughts: 1) perl Configure.pl creates all the settings to properly compile and link (shared or dynamic) parrot or libs. 2) Makefiles can use makefile variables or substitutions provided by config/gen/makefiles.pm or even posix substitutions. 3) Perl programs have all the config variables available with: use qw(lib); # or similar paths use Parrot::Config qw/%PConfig/; 4) Parrot's providing access to all these config vars too: see e.g. t/pmc/config.t or tools/dev/src-t.sh 5) lib/Parrot/Test.pm needs this info too, to run t/src tests 6) and dynpmcs, dynops, ... other stuff not even in the tree ... 7) if something is missing or wrong with 1) it should be adjusted/fixed there and not ever and ever again in 2) - 6). leo
