Peter Christopher <[EMAIL PROTECTED]> wrote:
> I'll check out the build scripts and see what flags will do to compile
> the t/src/*.c and put them in. Further, I'll try to determine good
> values for --cflags, --include, etc. from the Makefile.
Ok. Can you move the build script to F and provide a
Hi listers,
> > 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.
Ok two comments about the complexity of a build scri
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 di
Peter Christopher <[EMAIL PROTECTED]> wrote:
> Hi there,
> I have included a script that I think addresses TODO #32365 --
> which was, in short, allow easy shortcuts to build information. The
> script generates a file called parrot-config.pbc in the root directory
> that can search through
