This is a philosophical thing. My philosophy is: keep it simple, stupid (I
know very well that you are not stupid!). So if the build can rebuild a
target in a short time, I avoid putting in a condition to rebuild it only
if some dependency is out of date, as that makes the build file just a
little bit more more complex. But these things add up.

Original Message:
-----------------
From: steven yi stevenyi@csounds.com
Date: Thu, 07 Oct 2004 20:06:06 -0700
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:5387] generateXMG


Hi All,

I'm still chippin' away at the SConstruct file and was wondering about 
the generateXMG build option.  Is there a reason why this isn't done by 
default, or should I say, is this something optional for csound?  I was 
thinking of changing it to automatically "build the xmg files if the 
source file for it changes, and build makedb if it doesn't exist".  
Please let me know if this is a bad idea and I'm missing something 
regarding the xmg files.

Thanks,
steven


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

It seems more complex to me to have a user option to build the XMG 
rather than to have it auto-detect to build it or not.  If it requires 
building, it *should* get rebuilt.  To me, it's actually a 
simplification to remove any extraneous user options and have it done 
for them.  It's only a couple of conditions to add to the SConstruct 
file so I don't think it'd make it much more complex.  I'll try it out 
and see how it goes.

gogins@pipeline.com wrote:

>This is a philosophical thing. My philosophy is: keep it simple, stupid (I
>know very well that you are not stupid!). So if the build can rebuild a
>target in a short time, I avoid putting in a condition to rebuild it only
>if some dependency is out of date, as that makes the build file just a
>little bit more more complex. But these things add up.
>  
>