kcoul

Is testing if the max-includes compile properly as simple a matter as following the steps in the SDK, outputting a dll file, and then renaming it to the mxe extension, and placing it into the max search path?

I have tried this and the objects don't show up in max as having any inlets or outlets, they are dead objects! What am I doing wrong?

dll-mxe

> Is testing if the max-includes compile properly as simple a matter as

> following the steps in the SDK, outputting a dll file, and then renaming it

> to the mxe extension, and placing it into the max search path?

> I have tried this and the objects don't show up in max as having any

> inlets or outlets, they are dead objects! What am I doing wrong?

Check page 17 in the "WritingExternals.pdf" It explains the steps to create

your own project from an existing one. It's very easy so you don't have to

and you can tell vs to output a mxe file instead of dll so you don't have to

On 2/25/07, Kieran Coulter  wrote:
>
>
> Is testing if the max-includes compile properly as simple a matter as
> following the steps in the SDK, outputting a dll file, and then renaming it
> to the mxe extension, and placing it into the max search path?
>
> I have tried this and the objects don't show up in max as having any
> inlets or outlets, they are dead objects! What am I doing wrong?

Hi Kieran,
Check page 17 in the "WritingExternals.pdf" It explains the steps to create
your own project from an existing one. It's very easy so you don't have to
set all of the settings by your self.

and you can tell vs to output a mxe file instead of dll so you don't have to
rename it.

dll->mxe?