Re: date-time info at compile time
Re: date-time info at compile time
- Subject: Re: date-time info at compile time
- From: Paul M <email@hidden>
- Date: Tue, 19 May 2009 17:32:36 +1200
Thanks Jeff, you're is right, this is exactly the problem I'm solving,
so it's the build date I need, not the compile time of one of the
sources.
It seems the 2 step proceedure outlined earlier could be
simplified/streamlined for my needs - the key is probably the 'run
script phase'. I dont know xcode very well either, but this gives me
something I can look up in the docs.
I'd want it to be a fully automated one step process to avoid potential
errors (if there is potential for error, you can never rely on the
result after the fact). Once I've figured out the way to run an
arbtrary command as part of the build, the rest should be easy enough.
thanks for the clues
paulm
On 19/05/2009, at 5:04 AM, Ray, Jeffrey R. {Jeff}(DFRC-ME) wrote:
Probably stupid question:
Why not just use the __DATE__ and __TIME__ macros?
These macros tell you the time a particular source file was compiled.
This
is useful if you want your application(s) to print a list of when each
of
the component object files was compiled.
It's not so helpful with the problem of knowing when the final
executable
was compiled, nor does it allow you to have a single string that every
executable in a toolset uses, such as you might want for release
documentation or a version command.
Since the original poster was using a makefile define (the old way of
getting around this problem), I assumed he was solving that kind of
problem.
-jrr
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden