[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Force a file to be compiled always
From: |
Benjamin Bihler |
Subject: |
Re: Force a file to be compiled always |
Date: |
08-Nov-2010 08:57:34 CET |
Hi Ralf,
excuse me, I have sent this mail twice but in the mailing list the body
seems to be empty. I will try it a last time with another method...
>> your first suggestion (with the phony target) works great. The second
one
>> does not force compilation here (but that doesn't matter anymore since I
>> use the phony target now).
> Hmm, do you have a file named FORCE in source or build tree?
No.
>> As to the third suggestion: I use the __DATE__ and __TIME__ macros in my
>> code as a kind of version information. Therefore the compilation result
>> differs with every compilation, although my source file does not change.
Is
>> there yet a better method to store the compilation time stamp in a
library
>> without fiddling with make targets?
> People do this, but I don't think storing the date and the time is the
> most useful thing to do. How about a different suggestion: store
> information generated from your version control repository?
This would probably be the nicest thing to do. We will have to think about
it...
> Hope that, and the other comments posted, help.
Yes, very much!
Bye,
Benjamin
- Force a file to be compiled always, Benjamin Bihler, 2010/11/03
- Re: Force a file to be compiled always, Ralf Wildenhues, 2010/11/03
- Re: Force a file to be compiled always, Benjamin Bihler, 2010/11/04
- Re: Force a file to be compiled always, Valentin David, 2010/11/04
- Re: Force a file to be compiled always, Ralf Wildenhues, 2010/11/04
- Re: Force a file to be compiled always, Benjamin Bihler, 2010/11/05
- Re: Force a file to be compiled always, Benjamin Bihler, 2010/11/05
- Re: Force a file to be compiled always,
Benjamin Bihler <=
- Re: Force a file to be compiled always, Steffen Dettmer, 2010/11/10