JamPlus

I have just pushed my fix for Apple's bug. The fix changes ~clean:Project to !clean:Project.

Anyway, I have spent my spare time the past two weeks trying to convince Xcode 4.0.1 and then 4.0.2 to work correctly. Schemes do not resolve executables properly, at least for iOS targets. Hovering an executable for the tooltip where the executable resides results in the wrong directory path; it isn't clear to me how Xcode 4 is determining which directory to use when changing between a Debug and Release scheme. Schemes don't remember iOS executables after they have been set manually. Altering the PRODUCT_NAME field results in a property PRODUCT_NAME.app directory being created, but then the wrong executable name is built in there.

And all of this has nothing to do with JamPlus.

If someone who is smarter than me can show me how Xcode 4 is supposed to work, I would appreciate it.

I found that I can't just open an XCode workspace -- XCode just complains about a missing 'project.xproj' file

However, if I 'show contents' on the XCode workspace package, and browse to 'mytestapp.xcodeproj' - it opens, but hits the aforementioned assert.

However, if I hit 'continue' about 15 times in a row, it gets past the assert and I can continue to use Xcode.

I haven't gotten as far as debugging yet though... I'm still trying to get my project to compile properly. I'll get on to that today.

David Cowan wrote:

I found that I can't just open an XCode workspace -- XCode just complains about a missing 'project.xproj' file

I don't have any issues opening an Xcode 4 workspace. Do the JamPlus sample workspaces work for you?

However, if I hit 'continue' about 15 times in a row, it gets past the assert and I can continue to use Xcode.

There should be no assert with the fix I pushed. Do you have the fix?

I'm running with the latest binary thats on the jamplus.org files download section -- I haven't gotten any fixes yet.

Generating the Xcode workspaces for the samples doesn't quite work for me...
Building the 'samples/iphone/opengles' using the supplied Create...sh shell results in

Creating build environment...
Reading platform [*] and config [*]...
Reading platform [*] and config [release]...
Reading platform [*] and config [releaseltcg]...
Reading platform [*] and config [debug]...
Reading platform [iphone] and config [*]...
Reading platform [iphone] and config [release]...
Reading platform [iphone] and config [releaseltcg]...
Reading platform [iphone] and config [debug]...
Reading platform [iphonesimulator] and config [*]...
Reading platform [iphonesimulator] and config [release]...
Reading platform [iphonesimulator] and config [releaseltcg]...
Reading platform [iphonesimulator] and config [debug]...
Writing generated projects...
: command not foundpace.sh: line 2:

Also, I ended up having to make some minor changes to the sample Jamfile (and my own jamfiles) to get it compiling
The rule setup for C.MacOSX_SDK had to have the SDK_Version number and a target (*) added... i.e.

C.MacOSX_SDK * : $(PLATFORM) : 4.3 ;

Without the (*) target -- I kept getting errors about Entitlements.plist and Resource.plist not being able to be copied... I narrowed it down to the definition of isysroot in one of the setup functions not being set if the target was blank.

I also duped the declarations for SDK 4.2 in the iphone-gcc.jam and make some 4.3 ones (I'm working on a clean install of OSX with only the latest Xcode, so I didn't have any older SDK installs)

David Cowan wrote:

I'm running with the latest binary thats on the jamplus.org files download section -- I haven't gotten any fixes yet.

Ah, you'll want latest from Git. There have been a number of important updates. I planned to release a new build again when Xcode 4 was working, but I should probably do it before.

I also duped the declarations for SDK 4.2 in the iphone-gcc.jam and make some 4.3 ones (I'm working on a clean install of OSX with only the latest Xcode, so I didn't have any older SDK installs)

4.3 support is in Git.

Thanks for the detailed response.

Sweet... I'll update tonight, and let you know how I get on :)

Thanks Joshua!

OK, gave the new git version a go... I had to completely delete my existing Xcode workspace, but the assertion problem seems to have been fixed now.

However, when trying to open the project workspace by double clicking on the package - I get
'Project /Users/Dave/Projects/Engine/Workspaces.Xcode cannot be opened because it is missing its project.pbxproj file.'

If I right click on the workspace package and 'Show Package Contents', then browse to "_workspace.xcode_"... if I double click on 'project.workspace.xcodeproj', it opens just fine

I'm still working towards actually getting it to the stage where I can debug though - so I can't confirm if the debugging info and suchlike actually work.

Dave

Ive been digging through this again today and found a work around :

If i click on the application in the product folder, then look at its properties :

Under the executable if i set the deployment target to 10.6 i can now debug from within xcode... perhaps we need to set one more variable...