[Scons-users] SCon example for common build scenario

[Dan Pidcock]

Hi Dirk,

Yes you're absolutely correct. Don't know how I got os.getcwd() into
CPPPATH, must be an old test project!
For LIBPATH, my thinking is that the output directory should generally not
be in the same dir as source code, but for portability of this sample
project I have left it as cwd. I think in a real world project you would
set it from an environment variable (with sensible O/S specific defaults)
or something like that. I did try just to set it to '.', but couldn't get
that working with SCons.

Thanks for the points, I've updated the project.

Dan


On 16 June 2014 16:56, Dirk Bächle <tshortik at gmx.de> wrote:

>  Hi Dan,
>


> thanks for the nice example. I had a short look at it, and I think that
> it's a good start. Allow me one small remark though: I'm not a big fan of
> using absolute paths for specifying LIBPATH and CPPPATH, in connection with
> VariantDirs. By using relative paths like "../module1" you don't have to
> pass the current "build" dir down to your modules, and are much more
> flexible and robust against changes in the directory structure of your
> "src" tree.
>
> Just my 2 cents.
>
> Best regards,
>
> Dirk
>
>
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> http://four.pairlist.net/mailman/listinfo/scons-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://four.pairlist.net/pipermail/scons-users/attachments/20140616/06430e20/attachment.html>