How to sensibly use project relative paths?
How to sensibly use project relative paths?
- Subject: How to sensibly use project relative paths?
- From: Andy Wiese <email@hidden>
- Date: Wed, 17 Nov 2004 22:59:49 -0600
I'm considering reconstructing my project to get away from the
relative-source-outside-of-project-dir problem. But I am having
difficulty deciding on the most graceful way to do it. Any feedback
would be appreciated.
I have a project that ideally...hopefully, builds several different
modules, for multiple platforms and IDEs. I am currently working with a
file tree like this (pretend p_ is the overall project name):
p_
p_/source/...
p_/source/core/... // core x-platform tools
p_/source/interface/...
p_/source/interface/carbon/... // carbon UI tools
p_/source/interface/cocoa/... // cocoa UI tools
p_/build/...
p_/build/codwarrior/...
p_/build/xcode/...
p_/build/xcode/p_core/ (p_core.xcode)
p_/build/xcode/p_carbon/...
Ignore linux for now.
I'm currently trying to get a p_core project working with Xcode.
p_core.xcode should be able to reference source files in
p_/source/core. But this requires project relative paths eg
../../source/core which seems to be a real problem for Xcode.
I considered whether source trees would solve my problem, but this
seems to require an absolute path wired into the project (or is it all
xcode projects, even worse). Which, IIUC, would make working with CVS
branches a mess--I may have several different sandboxes, each with
their own xcode project. Wouldn't I have to redefine the source tree
every time I switched to working in a different branch?
If I stick to project relative paths, do I have to put all of the
source for core with the xcode project?
p_/m_core/m_core.xcode
p_/m_core/source
I like having the source for different modules unified under one source
directory. Hate to lose that.
But if I do that, where do I gracefully put the build tools for other
environments?
I know its hard to generalize, but I am wondering, what do typical
Xcode developers do?
I don't like to take needless potshots at a new environment just
because I'm not used to it yet. I'm not too picky about Find utilities
or text editing or whether a few break points slip. But this seems just
wrong. I don't think I should have to clutter up my source tree with a
bunch of tool specific files at such a high level.
Am I missing something?
_______________________________________________
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