How to specify dependencies that aren't included in the target

[Paul Fox-7]

I am using a linking script to link the project I am working on, and therefore need the script to be a dependency of the target (in order to generate it via some custom scripts at each build). However, it will not be included in the target, and boost-build does not, to my knowledge, know what to do with it. How to I make it a dependency of the final target without boost-build trying to include it in the target.

Thank you in advance for your help,

Paul


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Anatoly Shirokov]

Hi Paul!

In such cases I use <dependency>:

exe target : ... : <dependency>some_script.sh ;

Paul Fox:

> I am using a linking script to link the project I am working on, and
> therefore need the script to be a dependency of the target (in order
> to generate it via some custom scripts at each build). However, it
> will not be included in the target, and boost-build does not, to my
> knowledge, know what to do with it. How to I make it a dependency of
> the final target without boost-build trying to include it in the target.
>
> Thank you in advance for your help,
>
> Paul
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
>  

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Paul Fox-7]

Wow, that was simple. Thank you! I just wish I could find stuff like this in the online documentation more easily.

On Wed, Jun 17, 2009 at 12:19 PM, Anatoly Shirokov <shirokov_a@...> wrote:

Hi Paul!

In such cases I use <dependency>:

exe target : ... : <dependency>some_script.sh ;

Paul Fox:

I am using a linking script to link the project I am working on, and therefore need the script to be a dependency of the target (in order to generate it via some custom scripts at each build). However, it will not be included in the target, and boost-build does not, to my knowledge, know what to do with it. How to I make it a dependency of the final target without boost-build trying to include it in the target.

Thank you in advance for your help,

Paul

------------------------------------------------------------------------

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
 

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Paul Fox-7]

Another question: I have to pass the linker script as a parameter to ld, and I'm currently using <linkflags> to do so. However, the script will be generated on a target-specific basis, so I need to be able to place the linker script in the correct bin subdirectory for the current target under the project root. I know I can do the script generation using a generate rule to do this. However, I can't figure out how to retrieve that information to pass the location of the script to the linker. How would I do that?

Thanks,
Paul

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build