hi jamie,

with xcode3 you can add MaxRT as an executable, so that it launches on run and i guess you can do the same via the scheme settings in xcode4/5. Unfortunately i don't think it's possible to supply a .maxpat file as an argument on the command line (that would be very useful if anyone at C74 is listening)

oli

Thanks Oli,

I just edited my question to say that I'd managed to launch the runtime via the build scheme "Executable" setting, but your reply just beat me to it!

+1 for the ability to pass a patch path to the runtime.

Jamie

Actually... thinking about this a bit more, it needs more than just the path to the patch, it needs the path to the external being tested (or it needs to be in Max's path).

For Pd externals in my Xcode scheme, I set the Executable to the path to the pd binary and then set the Arguments Passed On Launch list to:

This means I can be debugging my external with a single keyboard shortcut.

It would be great if the Max Runtime supported similar arguments.

Jamie

Ive only just started to do this... but what Ive done, is create a max project with my test patch in it, set it to use the external that is built by Xcode.

then in Xcode, set executable in scheme to be max runtime add an argument that is my max project

hit run... everything works as expected.

p.s. i use project as you can specify search path for externals etc, whereas I cannot find a way to do this just with a patch. (the patch works passed as an argument, but cannot find the external - which is I assume the issue you are having?)

Actually no, If I pass the path to my patch in "Arguments Passed on Launch" in Xcode, it just launches the Max RT, but doesn't load the patch.

I'm using Max 5.0.5. Which version do you have? Maybe the ability to pass the path to a patch as an argument was added in Max 6?

Yup, just confirmed this works with the Max 6 RT. I haven't used projects yet, but it sounds like that is the way to go.

Thanks!

Ah... an alternative to using projects is to copy the external to the Max6 RT extensions folder in a Pre-actions script in the scheme settings. e.g.

cp -rf ${BUILT_PRODUCTS_DIR}/.mxo /Applications/Max\ 6.1\ Runtime/Cycling\ \'74/extensions/

i find leaving the object binary in the same folder as the help patch is sufficient for it to be found on launch. I don't like putting half finished stuff in my max search path

In this instance, I'm developing a library so just copying the .mxo next to the test patch won't cut it.

I do, however, have a Post-action deleting the the .mxo after the RT exits, as I agree, it's bad practice leaving these things around in non-temporary locations.