trying to compile, only 2 errors left !
First and beforehand, i know that there are plenty wrong things in that code. It comes from PureData, the fdn~ external, and i butchered it to ensure, in a first time, there would be only the big errors left. I didn't do the outlets/inlets translation rightly so far, i may have borked things when i replaced all t_int with int...
The wort thing apparently seems related to the use of a nested function. Nested functions are not part of c standard, but allowed by most gcc compilers. Apple disabled it by default, it is possible to re enable it by adding a -fnested-functions in the "other C flags" field of the project build infos. Thus, the "Nested functions are disabled" error message went away.
But there are still 2 errors left, at the same line as where that nested function thing was giving trouble (line 475) :
error: expected '=', ',', ';', 'asm' or '__attribute__' before '->' token
error: expected expression before '->' token
I attached the bugging source in case anyone would feel like giving it an eye. Thanks in advance !
I spy with my little eye…
In line 472 you've got the keyword 'float' hanging around with nothing attached to it and no semicolon. So, it looks like the first 'x' in line 474 is being treated as part of a variable declaration, at which point the '->' token won't parse (although one any of the tokens the compiler enumerates would, conceivably, parse. If the compiler doesn't complain until line 475, well, compilers do that sometimes.
No guarantees, but I'd ^W the float.
HtH -- P
Thanks a lot ! What an eye !...
I straightforward removed that floating "float" and now, just 1 error ... it is as follows :
"_IS_DENORMAL", referenced from:
_fdn_perform in fdn~.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
apparently it happens during the linking stage.
maybe it is time that i go back to the original source and do correct things ?..
Hi Vichug,
you have the macros IS_DENORM_FLOAT and IS_DENORM_DOUBLE defined in z_sampletype.h
Just use the appropriate one in place of IS_DENORMAL.
As an alternative (and probably better) option you can replace the whole line of code with FIX_DENORM_FLOAT or FIX_DENORM_DOUBLE.
As you have it right now, the 100% correct way to do it would be the following:
for(j=0;jAlso, your external won't work unless you add C74_EXPORT between int and main.
As a piece of advice, I would perform all calculations in double precision.
Let me know if it all compiles and works successfully.
Cheers
- Luigi
That's a lot of things that i don't understand yet... and i'll need to come back to this in two days or so
(but basically, it means _IS_DENORMAL was a macro for a function of a Pd library, which doesn't exist in Max right ? if i understood well. and there exists _IS_DENORMAL_FLOAT and _IS_DENORMAL_DOUBLE in Max api ? also the FIX )
@Luigi : is C74_EXPORT a new thing ?
Thanks a lot anyway
Yes, the C74_EXPORT is a "new thing"...
You need it if you want your external to work in Max 6.
Please look at the example projects in the latest SDK.
- Luigi
Hey, back on topic : i finally succeeded a compilation ! yay ! and it instantiates without crashing max ! even shows an inlet ! not saying the hting is working though, but that's a first step... now to create signal inlet and outlet and make sure it works...
Raja, you're assuming right that i'm a total noob when it comes to c and compiling :D and Luigi, on that C74_export thing, i'm still using sdk 6.0.4 which doesn't understand this. Is that necessary since max 64 bits ? I'm not sure i understand what this does do, and why it's necessary all of a sudden if it's not related to that.
C74_EXPORT is orthogonal to 64-bit, but it does make make some project maintenance stuff easier (e.g. on Windows you don't need to create multiple .def files). You should be able to copy it from the newer SDK back to the older SDK if you desire to use it in the older SDK.