The recent security update toasted my ability to use the
environment.plist to load dynamic library paths. Other variable seem
to make it through, but not DYLD_LIBRARY_PATH. Questions:
1) Was this an oversight? I know there were some security issues
surrounding this ...
2) I have never been able to get LSEnvironment to work properly as a
means for propagating this environment variable. Anyone have any
hints since it specifically mentions it in the environment variable
section of "Runtime Configuration Guidelines"?
3) Would it not be nice to have a way to propagate environment
settings through to the resulting distribution build in xcode? Maybe
it is in there somewhere, but all I am aware of is that environment
settings are only valid if run from within xcode.
Thanks to everyone advance,
Robert.
_______________________________________________
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
