• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Env differences between debug and non-debug
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Env differences between debug and non-debug


  • Subject: Re: Env differences between debug and non-debug
  • From: Jim Ingham <email@hidden>
  • Date: Mon, 15 Dec 2003 17:23:15 -0800

Note, however, that the Environment variables are stored on a per user basis, so your friend won't be able to share them with his colleagues through CVS. If you make a user file called "default.pbxuser" in the project folder, then new users will pick this up. So you can use this as a vehicle to share this setting. But note that if the user already has a .pbxuser file extant, then the default.pbxuser will be ignored.

Jim

On Dec 15, 2003, at 1:30 PM, Chris Espinosa wrote:

On Dec 15, 2003, at 12:46 PM, Michael Cashwell wrote:

He's working on an X11 app built in XCode using a native target. His problem is that the app expects a display environment variable to provide the xserver host name. When running the app via a shell he can put this variable in his .profile and all's well. But as the target process is owned directly by XCode and there's no intervening shell this doesn't work when debugging.

What's the best approach to capture environment variables for use when running under XCode within the project? (He would like that since it then is under version control and other developers will get the setting as part of getting the project and not need non-version-controlled magic data in order to build and debug.) I would have thought that just adding them to the target or build style would export them out but it doesn't seem to.

As in Project Builder, the Executables configuration lets you set env variables on launch or debug of the target application. In the Groups and Files list under Executables, select the executable you want and double-click it. There's an Environment Variables area where you can press the (+) button to add env variables that are set at launch and debug time.


Chris Espinosa
Apple
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.


--
Jim Ingham                                   email@hidden
Developer Tools
Apple Computer
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

References: 
 >Env differences between debug and non-debug (From: Michael Cashwell <email@hidden>)
 >Re: Env differences between debug and non-debug (From: Chris Espinosa <email@hidden>)

  • Prev by Date: Can I ignore syntax error in jam file?
  • Next by Date: Re: next version of xcode
  • Previous by thread: Re: Env differences between debug and non-debug
  • Next by thread: Re: XCode 'can't find' sources
  • Index(es):
    • Date
    • Thread