Re: Don't want to use target as source...

Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
Newsgroups gmane.comp.programming.tools.scons.devel
Message-ID <CAEyG4CGRLLK3v_2k-vOUxKme72hXPBABd=tOm0tL3vQSQ5wuaA__23695.0611383238$1474218586$gmane$org@mail.gmail.com>
This message should go on the users mailing list.
The dev mailing list is for development of scons itself.



On Sun, Sep 18, 2016 at 8:45 AM, Left Right <[email protected]> wrote:

> Hello,
>
> I'm trying to write a builder which doesn't take a file as a source.
> The whole area of source_factory and target_factory in Builders is a
> huge mess, and it's impossible to understand why things produce the
> results they do.  For instance, one extremely undesirable behavior, of
> which I cannot find the source is that if the source isn't given, then
> the target assumed to be the source.
>
> Basically, I need something that works like Library() builder.  I
> tried to read the code, but after ten delegations of delegations to
> delegations to other delegations I've lost track.  Even simpler.  I
> want the source to be a directory.  Not a file.  I can write a scanner
> that generates all file names given the directory name, but I keep
> running into unrelated errors in Scons code which assume too much
> about what things can be built and the way to do that, and they are
> never right.
>
> Bottom line: isn't there any way to circumvent all the layers of
> needless abstraction on top of Node and Builder classes and just have
> access to the database and tasks / jobs?  Example would help hundred
> times more than an explanation.
>
> Thanks.
> _______________________________________________
> Scons-dev mailing list
> [email protected]
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>

_______________________________________________
Scons-dev mailing list
[email protected]
https://pairlist2.pair.net/mailman/listinfo/scons-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.