• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: managing xcode projects vs going back to makefiles
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: managing xcode projects vs going back to makefiles


  • Subject: Re: managing xcode projects vs going back to makefiles
  • From: Gabriel Beauchemin <email@hidden>
  • Date: Wed, 26 May 2010 11:24:43 -0400

Take a look at cmake http://www.cmake.org/

Basically, you can generate projects(or makefiles)  from a simple
text-based project description.


On Wed, May 26, 2010 at 9:23 AM, Stéphane Beauchemin
<email@hidden> wrote:
> Hi Everyone,
>
>
>
> We have a bunch of static libraries that need to be compiled on OS X.
> Currently all the libraries are managed in Xcode projects. Almost all of our
> code is cross-platform (running on windows and gaming console); so our IDE
> of choice is normally Visual Studio but except for mac OS X. My colleagues
> are having hard time with the XCode projects : they say that XCode project
> don’t play nice with SVN... which is true. Sometime you make small
> modifications in Xcode project and you and up with huge differences when
> doing a diff with old version of the project. I know that Xcode project are
> in xml but it doesn’t seem possible to edit files by hand since Xcode add an
> ID next to each item.
>
>
>
> Another problem with Xcode project is that they can’t be edited on a windows
> computer. The dev that adds an object to a library need to walk to a mac,
> open the Xcode project make the changes and commit (we haven’t found any
> good remote desktop application for remotely access a Mac from a PC).
>
> For those reasons, we are thinking of switching to using makefiles.
> Makefiles can be edited with any text editor and it is easy to see changes
> you have made to it. Going back to makefiles seems a bit dumb when you have
> a tool like Xcode, but it seems the only solution. I am sure I am not the
> only one out there hitting problems like this. Any thought, suggestions?
>
>
>
> Thanks,
>
>
>
> Stephane
>
> P.S. : We are also looking at using things like premake.
>
>
>
>  _______________________________________________
> 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
>
>
 _______________________________________________
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

References: 
 >managing xcode projects vs going back to makefiles (From: Stéphane Beauchemin <email@hidden>)

  • Prev by Date: Re: managing xcode projects vs going back to makefiles
  • Next by Date: Re: managing xcode projects vs going back to makefiles
  • Previous by thread: Re: managing xcode projects vs going back to makefiles
  • Next by thread: Re: managing xcode projects vs going back to makefiles
  • Index(es):
    • Date
    • Thread