Re: [Boost-build] forcing regeneration of intermediate files

Subject: Re: [Boost-build] forcing regeneration of intermediate files
From: renaud lepere (lepere.renaud_at_[hidden])
Date: 2016-03-09 04:09:53

Le 09/03/2016 08:15, Vladimir Prus a écrit :
> the best way we have now is documented at:
>
> http://boost.2283326.n4.nabble.com/Automatic-version-number-or-build-id-tp4680192p4680429.html
>
> See my last post at the bottom of the page - could you give that a try?
>
> Thanks,
>
Thanks a lot, it put me on a good direction (I hope so). I did something 
similar and simpler but it seems to work :

exe hello : hello.cpp hello2.cpp build-id.cpp ;
make build-id.cpp : : @generate-build-id ;

actions generate-build-id
{
      python version.py > $(<)
}

explicit build-id.cpp ;
always build-id.cpp ;

The version control and other stuff (__DATE__ macros) are all in 
version.py and build-id.cpp is always regenerated.

Thanks