THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 23/11/2006 at 15:27, xxxxxxxx wrote:
Cinema 4D Version: 9.5-10.0
Platform: Mac OSX ;
Language(s) : C++ ;
Last time that I compiled my R9.5 and R10 UB plugin, no problems. Now all of a sudden, I get these errors:
_error: declaration of 'void* operator new(size_t) throw (std::bad_alloc)' throws different exceptions
error: declaration of 'void* operator new throw (std::bad_alloc)' throws different exceptions
error: declaration of 'void* operator delete(void* ) throw ()' throws different exceptions
error: declaration of 'void* operator delete throw ()' throws different exceptions_
This is contention between c4d_memory.h and XCode's new.h. Not sure if it was an Apple update, install of actual R10 (as compared to demo), or what. If it is related to exceptions, well I need exceptions for one of the libs used for the plugin. Any suggestion on how I might work around this without nullifying any possibility of compiling/linking this into a plugin?
On 23/11/2006 at 16:19, xxxxxxxx wrote:
Got it. Order of includes (?). The order and included files hadn't changed - very weird.
Back to final two compiles...
On 10/07/2008 at 11:26, xxxxxxxx wrote:
can you tell me which includes you mean here as I have the same problem here (just on PC)
On 10/07/2008 at 17:25, xxxxxxxx wrote:
I don't know - it's been a year and a half and this was Xcode complaining.
It may be related to exceptions and it sounds like I changed the order of <c4d.h> and <new.h>. Are you including any Windows headers?
On 11/07/2008 at 03:08, xxxxxxxx wrote:
nope, no windows headers only STL. Never had a problem, but now I installed the 2008 express version at home and after conversion from my project it gives me these errors.
I am using exceptions but turning it off doesn´t work. The errors remain. I will try changing some includes when I am home, maybe it helps. Otherwise I´ll be needing to install my full version at home too. But it´s strange anyway that this always happens.
On 30/03/2009 at 07:29, xxxxxxxx wrote:
I reinstalled OSX 10.5.6, Xcode and C4D R10.111 and now i have the same problem. Do you guys by any chance remeber the solution? This is weird, becuase i had the same config before (same osx, same xcode, same c4d) and no problems at all!
Ok, i just remembered that i did something else. I needed exceptions and enabled "C++ Exceptions" in the project settings. If i disable them the errors disappear. the problem is, i really need exceptions.
here are the errors i get when exceptions are enabled:
Any idea how i could get it to work?
On 02/04/2009 at 00:03, xxxxxxxx wrote:
solved. it was really just the order of includes. im using tinyxml and putting the tinyxml.h before c4d.h solved it!
On 02/04/2009 at 00:41, xxxxxxxx wrote:
This is also what the docu recommends.
from the 'Stability and Testing' chapter:
CINEMA 4D and OS code
-Include OS headers before CINEMA 4D headers
On 02/04/2009 at 02:22, xxxxxxxx wrote:
yes Matthias, i will definitely check the manual next time!
now... i ran into the next problem. after fixing all the includes im now getting a linker error on all files using gNew:
i wonder were all those issues came from. i already regret reinstalling osx...
if anyone has a clue, please let me know
On 03/04/2009 at 02:27, xxxxxxxx wrote:
btw: building the c4d sdk examples with c++ eceptions enabled raises the same error.
On 07/04/2009 at 03:01, xxxxxxxx wrote:
ok here comes a stupid question: is it possible at all to build with c++ exceptions enabled under osx?
edit: C4D R10.111, OSX 10.5.6, latest Xcode