florent E

So I'm stuck on a very frustrating issue : I've coded a custom external using the SDK, in Visual Studio. I've add to Max's objects folder my custom externals' folder but when I add the object that I created to my patch, the autocompletion works but I get a "no such object" error. It does the same error when I try to use the exemple externals (whosyourdaddy for example or simplemax). Compilation seems to go well though...

The only 2 previous posts that I've found are these ones : 

https://cycling74.com/forums/probs-compiling-in-xcode/

https://cycling74.com/forums/external-building-tutorials/

I've tried the given solutions (folder organization, and c-file's name) but non have yet worked...

Hey guys!
So I'm stuck on a very frustrating issue : I've coded a custom external using the SDK, in Visual Studio. I've add to Max's objects folder my custom externals' folder but when I add the object that I created to my patch, the autocompletion works but I get a "no such object" error. It does the same error when I try to use the exemple externals (whosyourdaddy for example or simplemax). Compilation seems to go well though...
The only 2 previous posts that I've found are these ones : https://cycling74.com/forums/probs-compiling-in-xcode/ and https://cycling74.com/forums/external-building-tutorials/

c-externals-no-object

Are you maybe compiling 32bit versions and trying them out in 64bit Max?

Well that's definitely possible but then how can I compile my external in 64 bits version? do I specify the x64 directories instead of the max-includes/msp-includes directories in my Visual Studio project's preferences?

EDIT : I just read on the API's documentation that I should change the extension of the external to .mxe64. I'll try that right now

It's not just the file extension. You need to create a 64bit profile in visual studio which requires Win SDK 7.1. I recommend you do some research on how to compile for 64bit with VS. The good thing is once it is done you can simply reuse the profile to compile any external for both architectures.

Of course, with some things in mind that can differ in 64bit externals which is described in the Max SDK manual.

It's not just the file extension. You need to create a 64bit profile in visual studio which requires Win SDK 7.1. I recommend you do some research on how to compile for 64bit with VS. The good thing is once it is done you can simply reuse the profile to compile any external for both architectures.
Of course, with some things in mind that can differ in 64bit externals which is described in the Max SDK manual.


first try the 32 bit max version. Are your externals .64mxe or .mxe?

(and just to be sure, you added the sdk build folder to preferences?)

https://cycling74.com/sdk/MaxSDK-6.1.1/html/chapter_appendix_e.html

You have to change some build settings in Visual Studio. You did that okay?

first try the 32 bit max version. Are your externals .64mxe or .mxe?
is Max 32 or 64 bit?
(and just to be sure, you added the sdk build folder to preferences?)

some info on 64 bit here: https://cycling74.com/sdk/MaxSDK-6.1.1/html/chapter_appendix_e.html

You have to change some build settings in Visual Studio. You did that okay?


Oh according to your link Venetian, I can't use Visual Studio Express to compile my external for x64 architecture. I have to buy the Pro version!!

So I will try to use Max 32 bits and this if it works...

EDIT : to answer your question, I have added the directory where my externals are created to Max's file preferences, if that's what you meant

Oh according to your link Venetian, I can't use Visual Studio Express to compile my external for x64 architecture. I have to buy the Pro version!!
So I will try to use Max 32 bits and this if it works...
Thanks a lot for your help guys

EDIT : to answer your question, I have added the directory where my externals are created to Max's file preferences, if that's what you meant


Okay so now the external loads up (I get the "AmpCalc object is loaded" message but it still lights up in red and doesn't show the inlet and outlets... I'll try the help files and see how that turns out

Okayyy it works!!!!!!!! So I was using SDK version 6 instead of version 7, and then I just used the "dummy" help file to keep the configuration of the VS project, and copy/pasted my code and replaced all the instances of the name of my object to "dummy". It works correctly now!

You would have thought sdk 6 would work fine. Not sure why that would have been an issue.

C externals : no such object