On Mon, 10 Jan 2005, Leopold Toetsch wrote: [snip]
> I'm not quite sure, if we need the additional complexity of a > build-script that generates parrot-config. It's for sure more flexible > but OTOH we probably just need a few shortcuts, which could be handled > directly too. > > > One thing I didn't address is what kind of shortcuts folks want. I just > > have a couple of example shortcuts in the script. > > Yeah. I was thinking of just > > --compile > --link > > maybe with shared variants that emit everything needed to create e.g. a > t/src/*.c -ish binary. > > Let's see what other people would need. for me, this would greatly simplify the mod_parrot build process, though i'd like to see it broken down into at least --cflags, --include, --ldflags and --libs so we can use our own flags. these options are pretty standard for *-config programs (apr-config, gtk-config, etc.). -jeff
