• 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: Xcode-users Digest, Vol 2, Issue 436
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode-users Digest, Vol 2, Issue 436


  • Subject: Re: Xcode-users Digest, Vol 2, Issue 436
  • From: Ladd Van Tol <email@hidden>
  • Date: Thu, 18 Aug 2005 12:02:57 -0700

PBTOMAKE is horribly broken, and is a bad example of how to go about things. Fortunately, it's much easier than you'd think to parse the Xcode project file format. The "project.pbxproj" file is a kind of plist, and once you understand the keying scheme it uses, you can repurpose the data without too much trouble. Xcode 2.1 projects are now even easier to understand, thanks to the comments that are automatically inserted.

I've written a converter that can turn most Xcode 2.0/2.1 projects into a roughly equivalent Makefile. This saved us a lot of time on a Linux project we were doing. Due to licensing constraints, I'm not sure that I can release this, but I would be happy to provide tips on how to write your own version -- it took me about two days to get working makefile output, and another day to add dependency analysis.

If you were to pay attention to some of the more complex features like target dependencies, build configurations, or custom build phases, this could become considerably more involved, but is still doable.

- Ladd

On Aug 18, 2005, at 5:09 AM, Finlay Dobbie wrote:

On 18/08/05, Jack Nutting <email@hidden> wrote:

On 8/18/05, Finlay Dobbie <email@hidden> wrote:

On 18/08/05, Jack Nutting <email@hidden> wrote:

Apparently, the requirements include that you convert your xcode
project to a Makefile project (there is a script)


Last I looked, PBTOMAKE was fundamentally flawed and didn't work in anything except the most trivial of cases.


That's too bad (and not too surprising).


To be honest, it's kind of lame that Xcode's build system is private and opaque.


-- Finlay
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40criticalpath.com


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: 
 >Re: Xcode-users Digest, Vol 2, Issue 436 (From: Stefan Werner <email@hidden>)
 >Re: Xcode-users Digest, Vol 2, Issue 436 (From: Finlay Dobbie <email@hidden>)
 >Re: Xcode-users Digest, Vol 2, Issue 436 (From: Jack Nutting <email@hidden>)
 >Re: Xcode-users Digest, Vol 2, Issue 436 (From: Finlay Dobbie <email@hidden>)
 >Re: Xcode-users Digest, Vol 2, Issue 436 (From: Jack Nutting <email@hidden>)
 >Re: Xcode-users Digest, Vol 2, Issue 436 (From: Finlay Dobbie <email@hidden>)

  • Prev by Date: Re: Adding a symlink (not its target) to a project (libz.dylib post security update)
  • Next by Date: Re: sourcecode.cpp vs. sourcecode.cpp.cpp?
  • Previous by thread: Re: Xcode-users Digest, Vol 2, Issue 436
  • Next by thread: Re: Still doesn't work - Re: Launch failed with error code -2857
  • Index(es):
    • Date
    • Thread