Re: DYLD_LIBRARY_PATH no longer valid in environment.plist ?
Re: DYLD_LIBRARY_PATH no longer valid in environment.plist ?
- Subject: Re: DYLD_LIBRARY_PATH no longer valid in environment.plist ?
- From: Luis Gustavo Martins <email@hidden>
- Date: Thu, 11 Sep 2008 18:33:52 +0100
Hello Fritz,
Thank you very much for the tips! It definitely seems the correct way
to define those env vars in Xcode.
I just have now to discover how to make CMake (we are using CMake to
automatically create the XCode projects) to automatically fill those
env vars in XCode. But that is a question for the CMake mailing list.
Btw, I found this security update info from apple that confirms that
DYLD_LIBRARY_PATH loaded from environment list was in fact deprecated
due to security reasons:
$MATLAB/bin/maci:$MATLAB/sys/os/maci:/usr/lib:/usr/local/lib
Cheers,
Gustavo
----------------------------------------------------------------------------------------
Marsyas open source framework
Music Analysis, Retrieval and SYnthesis for Audio Signals
http://marsyas.sf.net
----------------------------------------------------------------------------------------
On 11 Sep, 2008, at 17:34 , Fritz Anderson wrote:
On 10 Sep 2008, at 11:58 AM, Luis Gustavo Martins wrote:
The problem is that Xcode (in fact GDB inside XCode) complains
about not finding some of those MATLAB dylibs and borks my debug
session, even if I set the DYLD_LIBRARY_PATH env var to the correct
directories in .bash_profile (in fact, if I run my command line
executable in the Terminal everything goes well... but I miss the
Xcode debugger...). I guess that this is because env vars defined
in .bash_profile do not get propagated to Xcode (or any other GUI
app in OSX).
So as far as could discover, the other option would be to set
DYLD_LIBRARY_PATH in ~/.MacOSX/environment.plist which (after
logout/login) would make it global for everything in OSX (XCode and
GDB included).
... and of course, you wouldn't want that development-only library
path to apply to everything you do, development-related or not.
The shell-login scripts are not the way to go, as they are executed
only when, well, you log in to a shell. They're terminal-only.
When you run or debug an application in Xcode, the application is
run through an "executable," which is an Xcode abstraction for an
application package (or other binary), its arguments, and its
environment variables (etc.). Find your application in the
Executables group in the Groups & Files list (_not_ in the Products
group), and double-click it. (Or Project > Edit Active Executable.)
You'll get an inspector that lets you set environment variables for
just that application, for just when it is run from Xcode. (See the
Arguments tab.)
There are even checkboxes for you turn vars or arguments on and off.
— F
--
Fritz Anderson -- Xcode 3 Unleashed: Now Available -- http://x3u.manoverboard.org/
Luis Gustavo Martins
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