THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 05/12/2012 at 17:46, xxxxxxxx wrote:
Cinema 4D Version: 13/14
Platform: Windows ;
Language(s) : C++ ;
the whole sdk compiles correct in debug and release
but i can see plugins inside cinema4d in debug (compile) only
what may cause this problem?
On 05/12/2012 at 19:00, xxxxxxxx wrote:
most obvious thing would be another platform - 32/64 bit.
On 05/12/2012 at 19:50, xxxxxxxx wrote:
explain more please
On 06/12/2012 at 00:49, xxxxxxxx wrote:
I think littledevil means, that it may be because you compiled for 32 bit, but
started the 64 bit Cinema 4D. I can also not think of another reason .. ^^
On 06/12/2012 at 05:53, xxxxxxxx wrote:
that's why i asked i don't understand
i know well that .cdl work for 32 bit and .cdl64 work for 64 bit
but i think another reason ...not sure though ...may be some (initializing) is done automatically in debug mode so i can see plugins ..but in release that doesn't happend
On 06/12/2012 at 07:35, xxxxxxxx wrote:
It's not due to some difference between the debug and release build. If you're using the cinema4dsdk project as the basis for any new project you create, it should all just work. If you're setting up the project (including compiler and linker options) yourself from scratch, then you've done something wrong. I can't think of any other reason either.
One obvious question is, when you build in release mode, does it actually build the executable at all? In other words, if it builds a .cdl or .cdl64 but the plugin doesn't appear in Cinema, there's something wrong in the code which is preventing it from running. If it doesn't get built, you should be getting an error from the compiler or linker.
On 06/12/2012 at 11:58, xxxxxxxx wrote:
well i checked the differences between linker in debug mode and release mode ...debug mode got 1 more path for cinema4d\resources\_api_lib ...while release doesn't ...but it doesn't give errors ...may be it's the one making the problem