Monami

Is the procedure for debugging external as changed?

I couldn't find anything new in the Max5 API reference document and this:

https://cycling74.com/twiki/bin/view/ProductDocumentation/XcodeDebugging

the runtime launches and show me a bogus object when it should actually either crash or stop at one break point....

debugging-external-code

Make sure that your build path is in the search path of Max.

My sdk-build folder (which is somewhere in my Documents folder) is in my max search path... but the runtime don't seamed to find it.

If I copy the runtime in the sdk-build (and point the debugger executable there), for some weird unknown reason to me, when the runtime launches from the Debugger, I only have the MaxRuntime menu and the other like the File menu is not there.

The only way I found, was using the runtime from the max5 folder and manualy copy the mxo once it is build each time I am building it...

Yes a tedious workflow, but I manage to make it work...

I wonder if there is not an easier solution... Is there a way that the runtime launche the test patch instead of always opening it though the file menu?

My sdk-build folder (which is somewhere in my Documents folder) is in my max search path... but the runtime don't seamed to find it. 

If I copy the runtime  in the sdk-build (and point the debugger executable there), for some weird unknown reason to me, when the runtime launches from the Debugger, I only have the MaxRuntime menu and the other like the File menu is not there.

The Max Runtime does not actually use Max's searchpath. So you have a few things you can try to do for debugging.

1. move the sdk folder into the Cycling '74 folder.

2. build a standalone application with Max, and set the options for the searchpath in the standalone external before building.

3. load the extern by opening a patcher that is in the same folder as the .mxo/.mxe executable.

4. manually load your extern after the runtime launches by dragging the extern from the Finder/Windows Explorer onto the Max window.

The Max Runtime does not actually use Max's searchpath.  So you have a few things you can try to do for debugging.

1. move the sdk folder into the Cycling '74 folder.
2. build a standalone application with Max, and set the options for the searchpath in the standalone external before building.
3. load the extern by opening a patcher that is in the same folder as the .mxo/.mxe executable.
4. manually load your extern after the runtime launches by dragging the extern from the Finder/Windows Explorer onto the Max window.

Debugging external code