Re: Using agvtool's generated version info file?
Re: Using agvtool's generated version info file?
- Subject: Re: Using agvtool's generated version info file?
- From: Nicholas Helke <email@hidden>
- Date: Mon, 16 Aug 2010 14:52:16 +0200
Your right. A bug report should be submitted for insufficient documentation. And another bug report should be submitted suggesting that a header file be generated at the same time as $(PRODUCT_NAME)_vers.c.
Nicholas
On Mon, Aug 16, 2010 at 2:42 PM, Christiaan Hofman
<email@hidden> wrote:
On Aug 16, 2010, at 14:22, Rainer Brockerhoff wrote:
> At 13:52 +0200 16/08/10, Christiaan Hofman wrote:
>> On Aug 16, 2010, at 13:35, Rainer Brockerhoff wrote:
>>> So you can access those constants by including
>>> extern const unsigned char XYZVersionString[];
>>> extern const double XYZVersionNumber;
>>> in the file where you want to access them, and the linker will find them for you.
>>
>> The fact that they exist and you can do that does not mean that you SHOULD have a use for them (and that's what I said, I never said you can't). AFAIK they're there only to have these symbols in the binary, for debugging purposes. They're not meant for actual use. Otherwise there would be a header file to advertise them, or at least some documentation.
>
> There can't be a fixed header file as the names change (your project name is a prefix).
But that's something you could look up (or set yourself!) in the build settings. And the header would be automatically found if it were there, as Xcode always adds the derived sources to the header search path.
Christiaan
_______________________________________________
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