search

kstenerud / iOS-Universal-Framework

An XCode project template to build universal frameworks (arm7, arm7s, and simulator) for iOS / iPhone.
2.95k stars 473 forks source link

This is *NOT* a universal framework build #164

Open dawee opened 10 years ago

dawee commented 10 years ago

With XCode 5 and iOS-Universal-Framework (master - 66a8d64e6021ea958a3dc674f72f53b134b81f13).

I tried to build a fresh created project with command line :

xcodebuild -configuration Release UFW_ACTION=archive clean build

And I get this log :

UFW (M iphoneos): INFO: Note: This is NOT a universal framework build. To build as a universal framework, do an archive build.

UFW (M iphoneos): INFO: To do an archive build from command line, use "xcodebuild -configuration Release UFW_ACTION=archive clean build"

tomasebrennan commented 10 years ago

I've had the same issue but only when trying to run this command on our build server. On my local machine I don't get this warning. Is this something to do with the installation of the Universal Framework? I'm pretty sure I installed the it correctly or at least in the same manner on both machines.

tomasebrennan commented 10 years ago

I've figured out why I was having this issue.

Let's say I was building a Fake Framework called MyFramework. On my local machine I'd created the project in Documents/MyFramework . Within the MyFramework folder was my project and it was from within this folder that I ran "xcodebuild -configuration Release UFW_ACTION=archive clean build".

My issue was that after setting up a job to build MyFramework on jenkins, the root folder was now called workspace not MyFramework. Running the archive command from within this workspace folder gave me the log:

"UFW (M iphoneos): INFO: Note: This is NOT a universal framework build. To build as a universal framework, do an archive build."

My quick solution was to put my entire project into a folder called MyFramework and then pushed that to jenkins and ran the archive command from within the MyFramework folder. After doing this that offending log was gone.

I can't say I really understand why the name of the root folder needed to be the same as the Framework I was building, but this worked for me.