Re: Building a large framework
Re: Building a large framework
On 27 Aug 2013, at 19:40, Fritz Anderson <email@hidden> wrote:
> While showering (and believe me, that's not an image you want to linger on), I thought of this:
Bath time is a critical component in all the best software projects. The agile guys missed a trick there.
>
> Create a standalone Xcode framework project with two, and only two files:
>
> /*************** BREAK BREAK BREAK ***************/
>
> Good stuff removed here.
>
> I have no idea whether xcodebuild would choke on such a monolith. You could do the same divide-and-conquer trick with separate .h/.m files for portions of the whole. Have lots and lots of RAM.
>
Adding this level of indirection is a neat trick and it turned out to be pretty trivial to try this out in my case.
My code generator can spit out 2 such monolithic .h and .m files that represent the entire framework (it can also spit out class sized code lumps too).
Even with the just the two host files present (the monoliths are included in the hosts) Xcode goes into Got to get this stuff indexed pronto mode.
Xcodebuild eschews the indexing and just gets on with the building but chokes up on the 100,000 or so LOC.
The divide and conquer trick - say having 100 host m files might work but its trickier to setup. I may try this tomorrow though.
Having individual .m and .h files makes for friendlier browsing too.
The ideal would be to run xcodebuild on a .pbxproj file that the code generator dynamically updates (using /usr/libexec/PlistBuddy ?)with the 100s of .m files to be built.
Time to run some hot water…
Thanks
Jonathan
_______________________________________________
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