Re: DOS path separators - more info
Re: DOS path separators - more info
- Subject: Re: DOS path separators - more info
- From: Jerry <email@hidden>
- Date: Tue, 9 Aug 2005 19:07:24 +0100
On 9 Aug 2005, at 18:06, Brad Oliver wrote: I should have mentioned this in my prior post, but a scripting solution is not too practical.
For each change we make to the PC code, we must bracket it with #if MAC_PORT / #endif along with our initials and date - that includes these header syntax changes. As such, I pair up each group of #includes requiring a change - some files have 1, others have 30 or 40 in chunks throughout. This is beyond my scripting ability - if someone else has a script that will accomplish this like described - please feel free to share. :-)
That aside, one of our mandates when working with ported code is to minimize the amount of changes we make to the PC source base where possible. With this in mind, an Xcode/gcc switch would be far preferable, since it would keep out "noisy" changes that clutter up our file merges when we get PC patch code - remember, our changes never get propagated back, so each update to the PC code requires manual checking of the Mac-specific changes we make.
Would it be possible to pre-process the source tree before building so you don't need to actually do the #ifdef stuff? Then you could use a scripting solution.
Jerry
|
_______________________________________________
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