XCode 1.5: EXECUTABLE_SUFFIX broken?
XCode 1.5: EXECUTABLE_SUFFIX broken?
- Subject: XCode 1.5: EXECUTABLE_SUFFIX broken?
- From: George van den Driessche <email@hidden>
- Date: Mon, 31 Jan 2005 01:17:04 +0000
Hi,
According to the release notes, a target's output is a file at
EXECUTABLE_PATH, where EXECUTABLE_PATH is made up of
EXECUTABLE_FOLDER_PATH, EXECUTABLE_PREFIX, EXECUTABLE_NAME and
EXECUTABLE_SUFFIX. However, it's slightly unclear about the
relationship between EXECUTABLE_EXTENSION and EXECUTABLE_SUFFIX. And to
make matters worse, the setting in the Target Settings pane is titled
"Executable suffix" but the documentation in the same pane lists its
variable name as EXECUTABLE_EXTENSION.
Anyway, none of this would have bothered me much except for this
problem: setting the "Executable suffix" field in the target settings
(or in the project settings, for that matter) seems to have no effect
at all on the output filename for the target.
Adding an empty Shell Script build stage to my target allows me to see
all the environment variables that are set before the script is
invoked. I can check that indeed, EXECUTABLE_SUFFIX is empty and the
"Executable suffix" setting is being assigned to the
EXECUTABLE_EXTENSION variable.
Is this a known bug, or am I doing something wrong? Ultimately all I
need is to build a target whose filename ends in .so, for Python to be
able to load it as an extension. But I can't for the life of me figure
out how.
Many thanks,
George
_______________________________________________
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