• 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: Relative paths for headers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Relative paths for headers


  • Subject: Re: Relative paths for headers
  • From: Markus Hitter <email@hidden>
  • Date: Wed, 4 Jan 2006 21:33:30 +0100


Am 04.01.2006 um 18:23 schrieb Greg Norz:

...
#include "boost/shared_ptr.hpp"
...
If relative paths don't work in Xcode, what are some other developers
using when they share projects across multiple machines that might house
code in different locations on disk?

You should be able to create a fake framework by setting up a framework hierarchy, filling it with a symlink to the header directory and one to the actual library. Location of this framework matters, as libraries have their installation path compiled in.



Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/




_______________________________________________ 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
References: 
 >Relative paths for headers (From: "Greg Norz" <email@hidden>)

  • Prev by Date: Xcode dependencies
  • Next by Date: Xcode & Visual C++
  • Previous by thread: Re: Relative paths for headers
  • Next by thread: RE: Relative paths for headers
  • Index(es):
    • Date
    • Thread