On Mon, 22 Jun 2009, James E Keenan wrote:
Since jhorwitz asked me about this just now at YAPC|10 Parrot BOF, a data
point:
./parrot_config --dump | grep '$('
cat => '$(PERL) -MExtUtils::Command -e cat'
chmod => '$(PERL) -MExtUtils::Command -e ExtUtils::Command::chmod'
cp => '$(PERL) -MExtUtils::Command -e cp'
libparrot => '$(LIBPARROT_SHARED)'
libparrot_shared => 'libparrot$(SHARE_EXT).$(SOVERSION)'
libparrot_shared_alias => 'libparrot$(SHARE_EXT)'
libparrot_soname => '-Wl,-soname=libparrot$(SHARE_EXT).$(SOVERSION)'
mkpath => '$(PERL) -MExtUtils::Command -e mkpath'
mv => '$(PERL) -MExtUtils::Command -e mv'
rm_f => '$(PERL) -MExtUtils::Command -e rm_f'
rm_rf => '$(PERL) -MExtUtils::Command -e rm_rf'
touch => '$(PERL) -MExtUtils::Command -e touch'
i ended up working around this problem, so it's not as critical for me
anymore. that said, i decided to dig a little deeper for the greater
good. i found that the Makefile-style variables are hidden in the OS
hints files. it doesn't make much sense to expand them there, but we
might want to consider doing it while generating parrot_config. i
already wrote the expansion code for mod_parrot -- i'll see if i can
shoehorn it in.
-jeff
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
