[Alephmodular-devel] XCode notes so far

[Br'fin <br...@ma...>]

Ok, I've finally upgraded to OSX 10.3. This means that I also am 
working with XCode now. For AlephModular, I'm clearly the one in charge 
of updating the project file in CVS. I'm not sure who's grabbing the 
responsibility for AlephOne.

XCode opens and updates existing ProjectBuilder project files. And 
apparently requires some major changes in the outlook of some things if 
you want to get the full benefits XCode offers.

Target notes:

XCode imports PB projects and puts existing targets into a Classic 
Target node. This continues to build programs the way PB does.

* Both AM and A1 compiled with negligible problems using the Classic 
Target

XCode also has a Native Target mode. This is what XCode requires in 
order to use its own vastly different build system. Maintaining extra 
information about built files. However, Native Targets are definitely 
outside the range of information that PB can handle.

* Recommendation: Try to setup and maintain both Classic and Native 
build Targets for now, possibly as separate checkins. (Do one checkin 
with code in the Classic target, then follow up with an update to the 
Native Target to ease joining added files to the PB-2_0 branch)

* I couldn't get either AM or A1 to work in Native Target with ZeroLink 
on. Separate problems though. AM ends up with a missing symbol relating 
to the virtual destructor of ostream or ofstream. But it's 
straightforward to turn ZeroLink off. A1 gave me a missing symbol with 
respect to _luaopen. Either case, more investigation needs to be done 
and this is low priority to me.

* AM Compiles fine. With A1 I ended up having an issue where the 
resource file generation misses marathon2.resource and just skips it. 
Renaming/Copying marathon2.resource to marathon2.rsrc was horky, but 
fixed the problem. This could be done as an additional step in 
fix_cvs_resources.sh

Build Styles

XCode seems to lack the same semantics for Build Styles, as in PB could 
do PROP += <more values> and PROP = <override value>, but it seems as 
if XCode only does the latter. However, I've only just begun to grasp 
how XCode handles these issues and need to look into it more.


With respect to AM, I believe I'm going to create a CVS branch for 
dealing with XCode issues and sort them out on the branch before I land 
these changes on AM's main branch. Hence limiting the initial main 
trunk checkins until I've smoothed it all out.

-Jeremy Parsons
http://alephmodular.sourceforge.net/