[Scons-users] Out of project tree builds

[Brian Raven]

> -----Original Message-----

> From: scons-users-bounces at scons.org [mailto:scons-users-

> bounces at scons.org] On Behalf Of William Deegan

> Sent: 29 October 2012 01:50

> To: SCons users mailing list

> Subject: Re: [Scons-users] Out of project tree builds

>

> Francis,

>

>

> On Oct 28, 2012, at 9:48 AM, Francis Bolduc <fbolduc at gmail.com> wrote:

>

> >> "scons" === "scons ."

> >

> > I never understood this design choice, and I've been struggling

> > because of it since I started using SCons.

> >

> > Why isn't it rather "scons" === "scons /", so that if you don't

> > specify what you want built, it builds everything everywhere.

> >

> > It seems to me like the idea was to make some kind of hierarchical

> > thing where there would be SConstruct files in sub-directories, just

> > like Make projects do.

> >

> > But this clashes with out-of-source builds, becauses it forces you to

> > put build products somewhere below SConstruct, that is, in the

> source.

>

>

> It may be historical from Cons (the perl predecessor to SCons).

>

> True make does just build everything by default (IIRC).

> (Unless you notate otherwise)


A small nit-pick, but the default behaviour of make, with no targets specified, is to bring the first target in the makefile up to date. Granted, the first target is commonly a phony one 'all: ...'.

Perhaps I am missing something, but I don't see the OPs problem in my builds, possibly because I supply the variant directory as a Dir object, rather than a string, which seems to convert the relative directory path into an absolute one.

HTH


--
Brian Raven




________________________________

Please consider the environment before printing this e-mail.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.