Every time I build Csound with scons it insists on building every
library each time, even when no changes have been made to the source.
How can I tell it to stop? I'm using scons 1.2 and python 2.6, just
updated last night. This never happened with the previous version I
was running.

Rory.


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Does it build _everything_? You can pass --debug=explain to scons to try
to figure out why does it think it needs to rebuild stuff. Note that the
swig stuff is (at least on linux) manually built, so anything depending
on that will get rebuilt.

On Tue, 2009-11-03 at 19:02 +0000, Rory Walsh wrote:
> Every time I build Csound with scons it insists on building every
> library each time, even when no changes have been made to the source.
> How can I tell it to stop? I'm using scons 1.2 and python 2.6, just
> updated last night. This never happened with the previous version I
> was running.
> 
> Rory.
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"


-- 
Saludos,
Felipe Sateler

Hi Felipe, thanks for the help. It states that it's building all the
libraries and .def files because they either don't exist or they have
changed. This is odd. If I build straight after building it goes and
rebuilds all the libraries again? Why does scons things they've
changed? Scons doesn't clean up automatically after building does it?
If it does, it doesn't say anything about that after teh build has
finished.

Rory.


2009/11/3 Felipe Sateler :
> Does it build _everything_? You can pass --debug=explain to scons to try
> to figure out why does it think it needs to rebuild stuff. Note that the
> swig stuff is (at least on linux) manually built, so anything depending
> on that will get rebuilt.
>
> On Tue, 2009-11-03 at 19:02 +0000, Rory Walsh wrote:
>> Every time I build Csound with scons it insists on building every
>> library each time, even when no changes have been made to the source.
>> How can I tell it to stop? I'm using scons 1.2 and python 2.6, just
>> updated last night. This never happened with the previous version I
>> was running.
>>
>> Rory.
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
> --
> Saludos,
> Felipe Sateler
>


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Well, scons is somewhat hard to debug on this... Are the files scons
says doesn't exist actually exist (exact same filename)? You can use the
-n option to not actually build anything, but just print what would be
done. Also, has the last run from scons been successful?

On Tue, 2009-11-03 at 20:48 +0000, Rory Walsh wrote:
> Hi Felipe, thanks for the help. It states that it's building all the
> libraries and .def files because they either don't exist or they have
> changed. This is odd. If I build straight after building it goes and
> rebuilds all the libraries again? Why does scons things they've
> changed? Scons doesn't clean up automatically after building does it?
> If it does, it doesn't say anything about that after teh build has
> finished.
> 
> Rory.
> 
> 
> 2009/11/3 Felipe Sateler :
> > Does it build _everything_? You can pass --debug=explain to scons to try
> > to figure out why does it think it needs to rebuild stuff. Note that the
> > swig stuff is (at least on linux) manually built, so anything depending
> > on that will get rebuilt.
> >
> > On Tue, 2009-11-03 at 19:02 +0000, Rory Walsh wrote:
> >> Every time I build Csound with scons it insists on building every
> >> library each time, even when no changes have been made to the source.
> >> How can I tell it to stop? I'm using scons 1.2 and python 2.6, just
> >> updated last night. This never happened with the previous version I
> >> was running.
> >>
> >> Rory.
> >>
> >>
> >> Send bugs reports to this list.
> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> >
> >
> > --
> > Saludos,
> > Felipe Sateler
> >
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"


-- 
Saludos,
Felipe Sateler

Csound builds successfully. When I try the -n option it shows a load
of linker commands that it runs each time I build.I just checked my
csound dir and all the .a files are there and the .dlls too! Any other
ideas on how to proceed?

2009/11/3 Felipe Sateler :
> Well, scons is somewhat hard to debug on this... Are the files scons
> says doesn't exist actually exist (exact same filename)? You can use the
> -n option to not actually build anything, but just print what would be
> done. Also, has the last run from scons been successful?
>
> On Tue, 2009-11-03 at 20:48 +0000, Rory Walsh wrote:
>> Hi Felipe, thanks for the help. It states that it's building all the
>> libraries and .def files because they either don't exist or they have
>> changed. This is odd. If I build straight after building it goes and
>> rebuilds all the libraries again? Why does scons things they've
>> changed? Scons doesn't clean up automatically after building does it?
>> If it does, it doesn't say anything about that after teh build has
>> finished.
>>
>> Rory.
>>
>>
>> 2009/11/3 Felipe Sateler :
>> > Does it build _everything_? You can pass --debug=explain to scons to try
>> > to figure out why does it think it needs to rebuild stuff. Note that the
>> > swig stuff is (at least on linux) manually built, so anything depending
>> > on that will get rebuilt.
>> >
>> > On Tue, 2009-11-03 at 19:02 +0000, Rory Walsh wrote:
>> >> Every time I build Csound with scons it insists on building every
>> >> library each time, even when no changes have been made to the source.
>> >> How can I tell it to stop? I'm using scons 1.2 and python 2.6, just
>> >> updated last night. This never happened with the previous version I
>> >> was running.
>> >>
>> >> Rory.
>> >>
>> >>
>> >> Send bugs reports to this list.
>> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> >
>> >
>> > --
>> > Saludos,
>> > Felipe Sateler
>> >
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
> --
> Saludos,
> Felipe Sateler
>


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hmm, I'm kind of out of ideas. Maybe this is a bug on your version of
scons.

On Tue, 2009-11-03 at 21:14 +0000, Rory Walsh wrote:
> Csound builds successfully. When I try the -n option it shows a load
> of linker commands that it runs each time I build.I just checked my
> csound dir and all the .a files are there and the .dlls too! Any other
> ideas on how to proceed?
> 
> 2009/11/3 Felipe Sateler :
> > Well, scons is somewhat hard to debug on this... Are the files scons
> > says doesn't exist actually exist (exact same filename)? You can use the
> > -n option to not actually build anything, but just print what would be
> > done. Also, has the last run from scons been successful?
> >
> > On Tue, 2009-11-03 at 20:48 +0000, Rory Walsh wrote:
> >> Hi Felipe, thanks for the help. It states that it's building all the
> >> libraries and .def files because they either don't exist or they have
> >> changed. This is odd. If I build straight after building it goes and
> >> rebuilds all the libraries again? Why does scons things they've
> >> changed? Scons doesn't clean up automatically after building does it?
> >> If it does, it doesn't say anything about that after teh build has
> >> finished.
> >>
> >> Rory.
> >>
> >>
> >> 2009/11/3 Felipe Sateler :
> >> > Does it build _everything_? You can pass --debug=explain to scons to try
> >> > to figure out why does it think it needs to rebuild stuff. Note that the
> >> > swig stuff is (at least on linux) manually built, so anything depending
> >> > on that will get rebuilt.
> >> >
> >> > On Tue, 2009-11-03 at 19:02 +0000, Rory Walsh wrote:
> >> >> Every time I build Csound with scons it insists on building every
> >> >> library each time, even when no changes have been made to the source.
> >> >> How can I tell it to stop? I'm using scons 1.2 and python 2.6, just
> >> >> updated last night. This never happened with the previous version I
> >> >> was running.
> >> >>
> >> >> Rory.
> >> >>
> >> >>
> >> >> Send bugs reports to this list.
> >> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> >> >
> >> >
> >> > --
> >> > Saludos,
> >> > Felipe Sateler
> >> >
> >>
> >>
> >> Send bugs reports to this list.
> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> >
> >
> > --
> > Saludos,
> > Felipe Sateler
> >
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"


-- 
Saludos,
Felipe Sateler

I suppose I can try to role back to an earlier version. Thanks for your help.

Rory.


2009/11/3 Felipe Sateler :
> Hmm, I'm kind of out of ideas. Maybe this is a bug on your version of
> scons.
>
> On Tue, 2009-11-03 at 21:14 +0000, Rory Walsh wrote:
>> Csound builds successfully. When I try the -n option it shows a load
>> of linker commands that it runs each time I build.I just checked my
>> csound dir and all the .a files are there and the .dlls too! Any other
>> ideas on how to proceed?
>>
>> 2009/11/3 Felipe Sateler :
>> > Well, scons is somewhat hard to debug on this... Are the files scons
>> > says doesn't exist actually exist (exact same filename)? You can use the
>> > -n option to not actually build anything, but just print what would be
>> > done. Also, has the last run from scons been successful?
>> >
>> > On Tue, 2009-11-03 at 20:48 +0000, Rory Walsh wrote:
>> >> Hi Felipe, thanks for the help. It states that it's building all the
>> >> libraries and .def files because they either don't exist or they have
>> >> changed. This is odd. If I build straight after building it goes and
>> >> rebuilds all the libraries again? Why does scons things they've
>> >> changed? Scons doesn't clean up automatically after building does it?
>> >> If it does, it doesn't say anything about that after teh build has
>> >> finished.
>> >>
>> >> Rory.
>> >>
>> >>
>> >> 2009/11/3 Felipe Sateler :
>> >> > Does it build _everything_? You can pass --debug=explain to scons to try
>> >> > to figure out why does it think it needs to rebuild stuff. Note that the
>> >> > swig stuff is (at least on linux) manually built, so anything depending
>> >> > on that will get rebuilt.
>> >> >
>> >> > On Tue, 2009-11-03 at 19:02 +0000, Rory Walsh wrote:
>> >> >> Every time I build Csound with scons it insists on building every
>> >> >> library each time, even when no changes have been made to the source.
>> >> >> How can I tell it to stop? I'm using scons 1.2 and python 2.6, just
>> >> >> updated last night. This never happened with the previous version I
>> >> >> was running.
>> >> >>
>> >> >> Rory.
>> >> >>
>> >> >>
>> >> >> Send bugs reports to this list.
>> >> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> >> >
>> >> >
>> >> > --
>> >> > Saludos,
>> >> > Felipe Sateler
>> >> >
>> >>
>> >>
>> >> Send bugs reports to this list.
>> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> >
>> >
>> > --
>> > Saludos,
>> > Felipe Sateler
>> >
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
> --
> Saludos,
> Felipe Sateler
>


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Reverting to an older version of scons did it. Thanks for the suggestion.

Rory.


2009/11/3 Rory Walsh :
> I suppose I can try to role back to an earlier version. Thanks for your help.
>
> Rory.
>
>
> 2009/11/3 Felipe Sateler :
>> Hmm, I'm kind of out of ideas. Maybe this is a bug on your version of
>> scons.
>>
>> On Tue, 2009-11-03 at 21:14 +0000, Rory Walsh wrote:
>>> Csound builds successfully. When I try the -n option it shows a load
>>> of linker commands that it runs each time I build.I just checked my
>>> csound dir and all the .a files are there and the .dlls too! Any other
>>> ideas on how to proceed?
>>>
>>> 2009/11/3 Felipe Sateler :
>>> > Well, scons is somewhat hard to debug on this... Are the files scons
>>> > says doesn't exist actually exist (exact same filename)? You can use the
>>> > -n option to not actually build anything, but just print what would be
>>> > done. Also, has the last run from scons been successful?
>>> >
>>> > On Tue, 2009-11-03 at 20:48 +0000, Rory Walsh wrote:
>>> >> Hi Felipe, thanks for the help. It states that it's building all the
>>> >> libraries and .def files because they either don't exist or they have
>>> >> changed. This is odd. If I build straight after building it goes and
>>> >> rebuilds all the libraries again? Why does scons things they've
>>> >> changed? Scons doesn't clean up automatically after building does it?
>>> >> If it does, it doesn't say anything about that after teh build has
>>> >> finished.
>>> >>
>>> >> Rory.
>>> >>
>>> >>
>>> >> 2009/11/3 Felipe Sateler :
>>> >> > Does it build _everything_? You can pass --debug=explain to scons to try
>>> >> > to figure out why does it think it needs to rebuild stuff. Note that the
>>> >> > swig stuff is (at least on linux) manually built, so anything depending
>>> >> > on that will get rebuilt.
>>> >> >
>>> >> > On Tue, 2009-11-03 at 19:02 +0000, Rory Walsh wrote:
>>> >> >> Every time I build Csound with scons it insists on building every
>>> >> >> library each time, even when no changes have been made to the source.
>>> >> >> How can I tell it to stop? I'm using scons 1.2 and python 2.6, just
>>> >> >> updated last night. This never happened with the previous version I
>>> >> >> was running.
>>> >> >>
>>> >> >> Rory.
>>> >> >>
>>> >> >>
>>> >> >> Send bugs reports to this list.
>>> >> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Saludos,
>>> >> > Felipe Sateler
>>> >> >
>>> >>
>>> >>
>>> >> Send bugs reports to this list.
>>> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>> >
>>> >
>>> > --
>>> > Saludos,
>>> > Felipe Sateler
>>> >
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>> --
>> Saludos,
>> Felipe Sateler
>>
>


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"