Re: [Boost-build] generator problems

Subject: Re: [Boost-build] generator problems
From: Nogradi, Chris (Chris.Nogradi_at_[hidden])
Date: 2012-03-23 08:17:13

Steven,

I am using SVN 75749 on Windows and I have been needing to add explicit dependencies to auto generated targets since they did not appear to get rescanned after generation.  Are there some fixes that went in after?  I'll try to get the latest TRUNK soon and see if it is resolved.

Chris

-----Original Message-----
From: boost-build-bounces_at_[hidden] [mailto:boost-build-bounces_at_[hidden]] On Behalf Of Steven Watanabe
Sent: Thursday, March 22, 2012 11:02 PM
To: Boost.Build developer's and user's list
Subject: Re: [Boost-build] generator problems

AMDG

On 03/22/2012 08:31 PM, George Georgiev wrote:
> Hi,
>
> Something that I can not understand is how the scanner will be able to
> detect the dependencies if the files are still not generated.

Generated targets are rescanned for dependencies.
i.e. the include scanner should run /after/
lib1-1.cpp is created.

> I feel
> like the right solutions is in scanner.process to be added fake
> propagation explaining the expected dependencies. In pseudo code:
>
>
>     rule process ( target : matches * : binding )
>     {
>         ...
>
>         local cpp = get cpp target from $(target);
>         headers = get h targets from $(matches);
>         INCLUDES $(cpp) : $(headers) ;
>     }
>
> Unfortunately I am laking a basic knowledge of jam language and every
> experiment takes me forever to implement.
>

In Christ,
Steven Watanabe
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please contact the sender and delete all copies.

Thank you for your cooperation.