[Scons-users] how to add a folder to be included in the build

[Gary Oberbrunner]

I think you're trying to build and modify some software that already uses
scons, right? To work with SCons, there has to be a file called SConstruct
at the top of the tree. Typically that file calls SConscript files in the
subdirs. You can read a the users guide to learn more, but probably you
should talk with the authors of the system you are trying to extend.
On Nov 6, 2012 7:36 AM, "Kumar, Ranjan" <ranjank at qti.qualcomm.com> wrote:


>  Hi Gary****

>

> ** **

>

> Thanks a lot for the response.****

>

> ** **

>

> Actually we have .scons file in the build directory for each module but I

> see that those files only specify which API(nodes) it wants to import or

> export and it is protected, restricted or public in scope.****

>

> ** **

>

> I could find lots of .py files (python script files) in which I can see

> actual sconscript commands. These are in tools folder and in other folders

> as well.****

>

> But I am not able to identify which is the top level script and the

> subsidiary scripts. I think I have to modify the .py files actually. Not

> sure.****

>

> ** **

>

> So I am not able to find out in which .py or .scon I should modify so that

> my folder which I have added gets included in the build.****

>

> ** **

>

> ** **

>

> Below is a kind of layout.****

>

> ** **

>

> Abc****

>

>     Abc1****

>

>            Build****

>

>                   T1.scons****

>

>            src****

>

>    Abc2****

>

>            Build****

>

>                     T2.scons****

>

>           src****

>

> Xyz****

>

>    Xyz1****

>

>           ….****

>

>    Xyz2****

>

>               …..****

>

> Tools****

>

>        Khkh****

>

>                a.py****

>

>                b.py****

>

> ** **

>

> ** **

>

> As I said in the .scons file , it specifies only what nodes it exports or

> imports.****

>

> There are a lot of .py files where I think the change is required to build

> my folder.****

>

> ** **

>

> I think I have made it too complicated J****

>

> ** **

>

> Thanks & Regards****

>

> Ranjan****

>

> ** **

>

> ** **

>

> ** **

>

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

> scons-users-bounces at scons.org] *On Behalf Of *Gary Oberbrunner

> *Sent:* Tuesday, November 06, 2012 5:49 PM

> *To:* SCons users mailing list

> *Subject:* Re: [Scons-users] how to add a folder to be included in the

> build****

>

> ** **

>

> Hi Ranjan, SCons builds "targets" (files or dirs), and each target has to

> have two things: a build command (or set of commands) to build it, and a

> set of source files (or dirs).  If you can lay out how that maps to your

> case, perhaps we can help.****

>

> ** **

>

> On Tue, Nov 6, 2012 at 3:56 AM, Kumar, Ranjan <ranjank at qti.qualcomm.com>

> wrote:****

>

> Hi ****

>

>  ****

>

> I have added a folder. I want it to be included in the build.****

>

> Can anybody let me know where to modify in the .scons file so that this

> folder gets built?****

>

>  ****

>

> Thanks****

>

> Ranjan****

>

>  ****

>

>

> _______________________________________________

> Scons-users mailing list

> Scons-users at scons.org

> http://four.pairlist.net/mailman/listinfo/scons-users****

>

>

>

> ****

>

> ** **

>

> --

> Gary****

>

> _______________________________________________

> 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/20121106/7deb3a9d/attachment-0001.html>