Set build settings deployment target for iOS (iPhone/iPad) and OSX (32/64); without this Xcode defaults to latest and then will refuse to deploy to older targets. Tested with Xcode 5.
With iOS7 the status bar no longer hides when told to, the fix is described here http://stackoverflow.com/questions/18059703/cannot-hide-status-bar-in-ios7 and means setting UIViewControllerBasedStatusBarAppearance to true in the info plist file.
Allow C.Provision to be called with a filename. The existing behaviour (search for profile based on ID) still functions, but initially it will check if the profile is being passed by filename. We have found this much better, as we now store our profiles in our code repository, and then call C.Provision like:

C.Provision OurGame : "$(Root)/iOS/Provisions/OurGameDev.mobileprovision" ;

This means when the profile needs updating (new device, feature, expired, etc.) we can simply save the new profile into the above location and everything continues working. Previously we had to exact the PROFILE_ID from the profile, and then update the Jamfile.

Also, this fixes an issue where the embedded provision wouldn't update (inside the bundle) when the profile changed (the time stamp check reported the file inside the bundle was newer, the problem is it was newer but the wrong file).
Write the code signing identity specified via C.CodeSign into the Xcode project, as Xcode 5 by default will insist on signing the .app that JamPlus makes with the identity specified in the project.
Fix a compilation error in luasupport.c for older compilers
Documentation: Update some of the C module documentation against nextgen changes
Enhance the multipass build fix started in 2896348ecf05baba92eb5db4abfcecdcd6ffacba
Bootstrapping: Copy lua-tilde.dll as part of the bootstrapping process
Documentation: Updates
Remove writefile from the jam_action flags in the Lua support
Documentation: Updates
Support $@() as an alias for @()
Support @() in actions when the response flag is not being used
Add ^^^() to create a response file without specifying response as an action flag
C module: Handle spaces in the path during the Visual C++ link
Disable command-line and environment variable splitting at spaces
JamToWorkspace: Quote the Jambase.jam include to handle spaces in the path
C module: Use xcode-select --print-path on OS X
Bootstrapping: Add bootstrap.sh
JamToWorkspace: Fix Xcode generation when configurations are not available

When generating a workspace for multiple platforms, some platforms may
have configurations not available on other platforms (i.e. adhoc/
distribution for iOS/OSX aren't available for Tizen). This previously
caused the workspace generation to fail with:

-------------------------------------------------------------------------------
-- ...bin/scripts/ide/xcode.lua:182: attempt to index field '?' (a nil value):
-------------------------------------------------------------------------------
stack traceback:
	...usNextGen/bin/macosx32/../scripts/JamToWorkspace.lua:121: in function <...usNextGen/bin/macosx32/../scripts/JamToWorkspace.lua:97>
	.../bin/scripts/ide/xcode.lua:182: in function 'XcodeHelper_GetProjectExportInfo'
	.../bin/scripts/ide/xcode.lua:582: in function 'Write'
	.../bin/macosx32/../scripts/JamToWorkspace.lua:554: in function 'DumpProject'
	.../bin/macosx32/../scripts/JamToWorkspace.lua:664: in function 'DumpWorkspace'
	.../bin/macosx32/../scripts/JamToWorkspace.lua:988: in function <.../bin/macosx32/../scripts/JamToWorkspace.lua:702>
	[C]: in function 'xpcall'
	.../bin/macosx32/../scripts/JamToWorkspace.lua:1066: in main chunk
	[C]: ?
--------------------------------------------------------------------------------------------------

This commit if checks to avoid accessing nil which resolves the issue (I
appreciate there are some higher level issues about what should happen for
an 'adhoc' 'tizen' build, but regardless this commit hopefully will be seen
as an improvement on the current situation).