• 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: Building a large framework
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building a large framework


  • Subject: Re: Building a large framework
  • From: "email@hidden" <email@hidden>
  • Date: Tue, 27 Aug 2013 10:30:37 +0100

To be honest I don't think this is a way forward.
I don't want to add this sort of complexity (which the docs discourage anyway).

At present I have a Cocoa framework project.
Adding the auto generated source to the project (or to a new project) causes endless indexing.

So I need to find the best way of getting the auto generated sources compiled and linked into the main framework project.

Regards

Jonathan


On 27 Aug 2013, at 06:00, Appa Rao Mulpuri <email@hidden> wrote:

Hi Jonathan,

Divide your large framework in to sub frameworks and bundle them in a Umbrella framework.

- Apparao

From: "email@hidden" <email@hidden>
Date: Mon, 26 Aug 2013 22:57:45 +0100
To: <email@hidden>
Subject: Building a large framework

I am trying to put together a framework that uses a fair amount of generated code.
At  present the target contains some 2800 generated .m and .h files.
I can alternatively generate monolithic output as 1 large (5MB) .m and 1 large (2MB) .h file.

Attempting to add the individual or monolithic files to a standard Xcode project results in endless indexing.
The googlable tips about turning off indexing don't seem to wash anymore on Xcode 4.6.3
Cleaning, rebuilding etc is fairly futile.

So I create an external build system project (first draft of makefile is below).
Now when I add files to the project it whips through the indexing in a spritely manner.

Hopefully the makefile will do the job but it is more tedious to maintain.

I would appreciate any insight on getting standard Xcode cocoa  projects from choking on large numbers of input files.

CC=clang 

# compiler vars
CINCLUDE:= -I/Library/Frameworks/Mono.framework/headers/mono-2.0 
CFRAMEWORKS:= -F ../../../../../products -F/Library/Frameworks
CVERBOSITY:= -v
CDEBUG:= -g
COBJC:= -x objective-c -arch $(ARCHS) -fexceptions
CWARNINGS:= -Wall -Werror

# link vars
LFRAMEWORKS:= -framework Foundation -framework Cocoa -framework Dubrovnik
LLIBRARIES:= -lobjc

CFLAGS= $(CWARNINGS) $(COBJC) $(CVERBOSITY) $(CDEBUG) $(CFRAMEWORKS) $(CINCLUDE) -c $(SOURCE) 
LDFLAGS=$(LLIBRARIES) $(LFRAMEWORKS)

SOURCES = $(wildcard *.m)

OBJECTS = $(SOURCES:.m=.o)

all: $(OBJECTS)

Regards

Jonathan









_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: email@hidden
This email and any attachments are confidential, and may be legally privileged and protected by copyright. If you are not the intended recipient dissemination or copying of this email is prohibited. If you have received this in error, please notify the sender by replying by email and then delete the email completely from your system. Any views or opinions are solely those of the sender. This communication is not intended to form a binding contract unless expressly indicated to the contrary and properly authorised. Any actions taken on the basis of this email are at the recipient's own risk.

 _______________________________________________
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

  • Follow-Ups:
    • Re: Building a large framework
      • From: Fritz Anderson <email@hidden>
References: 
 >Re: Building a large framework (From: Appa Rao Mulpuri <email@hidden>)

  • Prev by Date: Re: Building a large framework
  • Next by Date: Re: Building a large framework
  • Previous by thread: Re: Building a large framework
  • Next by thread: Re: Building a large framework
  • Index(es):
    • Date
    • Thread