JamPlus

As far as I am aware, the published build of JamPlus on the Mac just works. You don't need to specify a path to the Jambase.

What Mac OS X version are you running? All of my machines are on 10.6 now, but JamPlus used to work on 10.4 and 10.5. I never tested below 10.4.

I re-installed OSX and XCode 3.2.5 (my mac was a bodge of old compilers and tools, and crap left over from when my wife was using it, so I decided to start with a clean slate).

My status is thus...

1. iOS projects build (samples\iPhone\opengles sample) - (iPhone, iPhoneSimulator, iPad, iPadSimulator) -- however, I don't seem to be able to run them -- XCode complains that I have no provisioned devices connected. My understanding was that I didn't need to provision any devices to run the emulator?

2. Attempting to build (samples\macosx\cf or macosx\glut) - results in

Daves-Mac:glut Dave$ jam -a PLATFORM=macosx32
*** found 8 target(s)...
*** updating 2 target(s)...
@ C.CC <glut>main.o 
@ C.Link <glut>glut.release 

    g++ -arch i386 -framework GLUT -framework OpenGL -o glut.release main.o  

: command not found
: No such file or directory.1: 
*** failed C.Link <glut>glut.release ...
*** failed updating 1 target(s)...
*** updated 1 target(s)...
*** finished in 0.08 sec

However -- cutting/pasting the cmdline from the jam process into the command line directly - correctly builds 'main.o'
The same thing happens at the link stage, and again, I can link by hand if I issue the same command line.

Any pointers where I can start poking/prodding?

Thanks

Are you using the snapshot JamPlus binaries directly?

It really looks like a whitespace issue. Jam has always handed the contents of the actions directly to batch file or shell script. In a shell script's case, CRLF is bad.

Did you checkout the sources with Git and have a core.autocrlf setting of 'true'?

Got the compilation and workspace generation problems sorted for now -- it was mostly to do with global/system wide paths and environment variables.

However -- I'm still stuck trying to run the sample programs on the simulator...

E.g. in the samples/opengles sample, I generate an Xcode workspace using the shell command in that folder, and successfully build the iphonesimulator project target.
However, when it comes to running, I get -

"Error Starting Executable"
"No provisioned iOS device is connected"

However - if I compile and run a fresh Xcode sample (Create new iOS project) - the simulator starts fine.

What am I missing?

Thanks

David Cowan wrote:

Got the compilation and workspace generation problems sorted for now -- it was mostly to do with global/system wide paths and environment variables.

I'd be curious as to which and what I can build in to avoid the problem in the future.

However -- I'm still stuck trying to run the sample programs on the simulator...

E.g. in the samples/opengles sample, I generate an Xcode workspace using the shell command in that folder, and successfully build the iphonesimulator project target. However, when it comes to running, I get -

"Error Starting Executable" "No provisioned iOS device is connected"

Did you select Simulator in the build dropdown instead of Device? I'm referring to the top two items on the dropdown. Then the list of build configurations follow. Obviously, you need an iphonesimulator configuration. The executable target and architecture should be fine as the defaults.