Re: Source Tree Preference
Re: Source Tree Preference
- Subject: Re: Source Tree Preference
- From: Marshall Clow <email@hidden>
- Date: Sun, 9 Nov 2003 13:01:18 -0800
Am 09.11.2003 um 19:03 schrieb Marshall Clow:
Scott Tooker <email@hidden> wrote:
Just to clarify some things:
1. Xcode doesn't support recursive search paths.
A major failing, IMNSHO.
What's the rationale here?
Such things work on simplistic systems, only. Take the file
"limits.h", for example:
Nobile:~$ find /usr/include -name limits.h -print
/usr/include/gcc/darwin/2.95.2/machine/limits.h
/usr/include/gcc/darwin/3.1/machine/limits.h
/usr/include/gcc/darwin/3.3/machine/limits.h
/usr/include/i386/limits.h
/usr/include/limits.h
/usr/include/machine/limits.h
/usr/include/ppc/limits.h
Which one should the compiler use by default? There are already some
rules and more rules whould make things more complicated (and break
compatibility to most other UNIces in the world).
And how does the compiler know which one to use now?
if I say "#include <limits.h>, which one gets included?
FWIW, If I tell CW to look in "/usr/include/" (recursively), it will
read "/usr/include/limits.h".
It assumes that all the code that I share between projects lives in
a single directory. PowerPlant, boost, Whisper, crypto++, etc, none
of these follow that model.
Usually, you add a -I flag for every library you use.
Right.
I say -I $(PowerPlant).
But that doesn't work.
Or, you use something like
#include <crypto/whatever.h>
Both are common pratices in the UNIX world.
Ok - I have a lot of code that looks like:
#include <LAttachable.h>
which is located in:
$(PowerPlant)/Extra Classes/LAttachable.h
Are you suggesting that I should write:
#include <PowerPlant/LAttachable.h>
and why would I expect that would work?
Markus
P.S.: If you want recursive behaviour, add the output of
find /usr/include -type dir | while read D; do echo -n "-I $D "; done
to your CFLAGS ... ahem, but don't expect things work like before, then ...
I absolutely expect things to work like before.
If Apple is pushing XCode as something that CW users should switch
to, then it is in
their interest to not require them to make massive changes to their
source files.
P.S. Saying that such things "are common pratices (sic) in the
UNIX world" will not
convince me. I write software for the Macintosh (and secondarily
Windows). The fact that the Mac OS
is based on Unix is of very little interest to me - except that it
usually means 'cryptic, hard to use tools'.
--
-- Marshall
Marshall Clow Idio Software <mailto:email@hidden>
Hey! Who messed with my anti-paranoia shot?
_______________________________________________
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.