On 07/10/02 08:38 +1000, Sisyphus wrote:
> 
> ----- Original Message -----
> From: "Piers Harding" <[EMAIL PROTECTED]>
> 
> 
> 
> >
> > It might be worth thinking about giving varying degrees of the output
> > depending on command line options, or CONFIG directives.

Yes. I think some evironment variables might come to the rescue here. Which,
of course could also be config directives too.

> Actually - now that I take the time to think about it - I don't see any
> problem with altering "$make > out.make 2>&1" to "$make".

Not a bad idea. I'll have to play with it. It at least should be an option.

> Just tried it and it seems to suit me fine. The build directory is still
> specified and I can go straight to the xs file if I need to.

I think the most important things you want to see are error messages and then
the C code that caused them. Dumping the C to the screen is proabably not
what you want. But an option to copy the .c file into the current directory
might be ok.

> 
> I'll keep with that change so long as no problem surfaces. But perhaps it's
> not to *everyone's* liking.

Well, I think it's at least better than the current situation. Let's play
with this. I'll put some stuff in the next release. It might be a couple
days. I'm working on a secret side project. :)

Cheers, Brian


Reply via email to