THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 01/11/2005 at 03:50, xxxxxxxx wrote:
User Information:
Cinema 4D Version: 9.1
Platform: Mac ;
Language(s) : C++ ;
---------
Hello,
i have seen, that the new codewarrior 10 is now available.
is it possible to compile my mac plugins with this version ?
if not, which version do i need ?
best regards
ralph
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 01/11/2005 at 07:13, xxxxxxxx wrote:
I haven't heard anyone who has tried CW10, so please report your results. The recommended version is CW8 and above, so CW10 might work. Has anyone else tried?
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 01/11/2005 at 07:32, xxxxxxxx wrote:
hi,
i have ordered it. i hope, that i can make my first codewarrior tests with my quickstairs plugin today.
i hope, i'll find a way to get my plugin compiled. i've never seen codewarrior before 
maybe i'll have some questions about the setup of a pluginproject...
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 01/11/2005 at 10:43, xxxxxxxx wrote:
The next update of C4D, soon to be released, will support CW10. For the current versions you need to change c4d_pmain.cpp so that it includes MWException.h instead of NMWException.h.
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 01/11/2005 at 11:10, xxxxxxxx wrote:
so it is NOT possible do compile my plugin ??????
d.... and now i can't return my cw 
again thrown money out of the window only, because i wanted to bring the plugin to the mac ....
but thanks for the information !
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 01/11/2005 at 11:12, xxxxxxxx wrote:
In order to compile it with the current versions of C4D you need to change c4d_pmain.cpp so that it includes MWException.h instead of NMWException.h.
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 02/11/2005 at 01:51, xxxxxxxx wrote:
sorry, there was a missunderstanding
i've tried to compile and it worked fine!
i didn't changed the files, you told me, because i don't know where to change it! but it seems, that it doesnt matter, my plugin compiled without errors !!!
the sdk samples compiled (width some warnings) too.
the only thing is the compiling time. my plugin needed about 15 minutes to compile (!!!!) width optimization and about 4 minutes without. that's very slow, so i think, that i will develop on windows and unse the codewarrior only for the final compilation.
Codewarrior 10 seems to work fine!
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 02/11/2005 at 13:24, xxxxxxxx wrote:
since 3 hours i try to find the place, where i should change MWException.h instead of NMWException.h.
i cant find it. the c4d_pmain.cpp doesn't include one of the files above.
if i make a search through the whole project files, the result is 0!
can you tell me, where i should change the include ?
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 02/11/2005 at 13:33, xxxxxxxx wrote:
Well, if your plugins compile they should probably work fine without any changes. The programmers said that the change was necessary for them to get it to compile in CW10, but perhaps this backward compatibility bug has been fixed in your copy. Anyway, have a look on line 36 of c4d_pmain.cpp in R9.101 and see if changing it makes any difference at all:
#include <NMWException.h>
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 03/11/2005 at 13:55, xxxxxxxx wrote:
ahh i found the reason: i test it with 9.1, but i compile it width my old 8.5 sdk, so that they can use it too. and there is no #include <NMWException.h> - no wonder, why i cant find it !
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 15/11/2005 at 14:19, xxxxxxxx wrote:
Hope you can give me a hand.
I just updated to CW 10, and had the same error with the NMWExeption.h mentioned above.
After changing the line 36 in c4d_pmain.cpp to #include <MWException.h> I still get these errors with C4D v9.1:
Error : the file 'MWException.h' cannot be opened
c4d_pmain.cpp line 36 #include <MWException.h>
Error : undefined identifier '__register_fragment'
c4d_pmain.cpp line 121 __, __exception_table_start__, __exception_table_end__, __RTOC());
Error : undefined identifier '__unregister_fragment'
c4d_pmain.cpp line 153 __unregister_fragment( fragmentID );
Build of target "CINEMA4D SDK (Debug)" in project "cinema4dsdk.prj" failed because a subtarget or subproject build failed
Any ideas?
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 15/11/2005 at 16:52, xxxxxxxx wrote:
Might I also remind everyone that Rui is sitting here (in the previous topic) with the exact same errors as Arndt!
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 16/11/2005 at 01:42, xxxxxxxx wrote:
Hello,
I just got the solution by Philip:
Open the API project settings (both release and debug) and go to Access Paths. Add
{Compiler}MacOS Support/Libraries/Runtime/(Runtime_Common)
to System Paths.
This works fine for me now.
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 17/11/2005 at 09:20, xxxxxxxx wrote:
I tried to do that and when I open the project, I still get the following messages:
The following access path in target "_api_v8 (Debug)" of project "_api_v8.prj" cannot be found:
{Compiler}MacOS Support/Libraries/Runtime/(Common Sources)
The following access path in target "_api_v8 (Final)" of project "_api_v8.prj" cannot be found:
{Compiler}MacOS Support/Libraries/Runtime/(Common Sources)
And, when I try to compile, I get these errors:
Error: the file 'MWException.h' cannot be opened
c4d_pmain.cpp line 43 #include <MWException.h>
Error: undefined identifier '__register fragment'
c4d_pmain.cpp line 132 __, __register_table_start__,__exception_table_end__,RTOC());
Error: undefined identifier '__unregister fragment'
c4d_pmain.cpp line 170 __unregister_fragment( fragmentID );
Error: the file 'MWException.h' cannot be opened
c4d_pmain.cpp line 43 #include <MWException.h>
Error: undefined identifier '__register fragment'
c4d_pmain.cpp line 132 __, __register_table_start__,__exception_table_end__,RTOC());
Error: undefined identifier '__unregister fragment'
c4d_pmain.cpp line 170 __unregister_fragment( fragmentID );
Could not find or load the file "_api_v8_mac_deb.lib" for target "CINEMA SDK (Debug)" for project "cinema4dsdk_2.prj"
Why am I having all these problems?
Rui Batista
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 17/11/2005 at 09:29, xxxxxxxx wrote:
Error: the file 'MWException.h' cannot be opened
c4d_pmain.cpp line 43 #include <MWException.h>
maybe you should check the path to MWException.h ?
this was one error in my tests...
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 17/11/2005 at 09:58, xxxxxxxx wrote:
The file MWException.h is located at {Compiler}MacOS Support/Libraries/Runtime/(Runtime_Common) and also at {Compiler}MacOS X Support/Libraries/Runtime/(Runtime_Common)
right beside the MWException.cpp file.
Isn't that the correct place?
Rui Batista
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 17/11/2005 at 10:17, xxxxxxxx wrote:
Hi Rui,
please try the follwing thing.
While you are in CW 10 with your project open, double click on the "_api_v8.prj" right next to the list of your source files.
After this, choose Edit>_api_v8.prj (Debug) Settings... and check the Access paths settings there as well (even if the right pass is already in the list). Just click on the MacOS Supprt/Libraries/Runtime/(Runtime_Commmon) entry for the System Paths again and click on the Change... button below. Choose the exact same path again. That did it for me, as it seems that the api itself has to use that path, too.
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 17/11/2005 at 10:23, xxxxxxxx wrote:
YES!!! That did it!!!
Thank you all!!
Oh, by the way, shouldn't it be MacOS X Support, instead of MacOS Support, if I'm compiling for OSX?
Rui Batista