[crossfire] Am interested in porting to Mac

[Alex Schultz]

Amorya North wrote:

>>
     
      You may want to build it within the existing framework and link 
     
     >>
     
      directly to the C code in the common directory, because that way this 
     
     >>
     
      native MacOS client could eventually become an official part of the 
     
     >>
     
      source tree, and one advantage of that is that many protocol changes 
     
     >>
     
      would be handled from the code in the common directory which would 
     
     >>
     
      then make handling such changes in the MacOS port very easy.
     
     >
     
     
     >
     
     
     >
     
      Yeah, that'd be good. I use an IDE instead of makefiles, so it 
     
     >
     
      wouldn't be tied into the build system (unless someone else helps me 
     
     >
     
      out there), but I could keep all my code in one folder (macos/ or 
     
     >
     
      something) and any Mac users who want to compile from source could 
     
     >
     
      open the project file from within there.
     
     
It absolutely doesn't need to be tied into the make build system, the 
win32 compile of the gtk client for one uses a MSVC project file for the 
building, though I'm sure that there would probably be someone willing 
to attempt to help integrate it into the make build system. For a 
location to put your project file for your IDE I would personally 
suggest making something along the lines of what the make_win32/ 
directory does for the win32 builds. Also, yes I highly suggest putting 
it in one folder as you say in something like a macos/ directory. 
(personally I would suggest calling it cocoa/ instead as it's not so 
much a macos port as much as a cocoa port IMHO)

Alex Schultz