Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

XCode 1.5: EXECUTABLE_SUFFIX broken?

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:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.