Compiling after 10.1 -> 10.5 Upgrade?

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 29/10/2007 at 01:52, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   10.5 
Platform:   Windows  ;   
Language(s) :     C++  ;

---------
Hi,

after i upgraded my R10.1 to R10.5, I have a problem: I can't compile my sources anymore.

1. When I open my .vcproj VisualStudio2003 gives me an error message, telling me that the api_v8 project does not exist. Right, in 10.1 it was right there, but in 10.5 it is not.

2. When I try to open the .vcproj with all the example plugins that came with R10.5, VisualStudio2003 tells me the project file would be in a wrong version. Do I really have to upgrade to VisualStudio2005 just to compile my plugin in R10.5 ? That would be stupid :-(

So I thought it would be best to use a separate (non-upgraded) installation of R10.1 to develop my plugin there. But how should I debug if something bad happens in 10.5 ?

+ + +

Conclusion:
Is there a standard way to compile my plugins in R10.5?
Would it be a good idea to compile them in 10.5, anyway? Will they still run in R10.1?

Thanks in advance for any help and tips!

Best regards & greetings,
Jack

P.S.: One more thing. In a moment of bright thought I made a backup of my whole cinema4dsdk folder before I started the 10.5 installer.
Good idea, because after running the installer, my old sources were all deleted. It would be nice if the installer would ask me if (and where) it should backup the existing cinema4dsdk folder.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 29/10/2007 at 07:16, xxxxxxxx wrote:

Howdy,

One thing that I do on the PC is have two Maxon folders. One in the "Program Files" folder and another one somewhere else. The one in the Program Files folder is always the most current version which I update with the installer. Then I make a copy of that in the other folder. It's the other folder where I do my developing, and in that folder I have separate folders for all versions going back to 9.1. This way I can do my initial development in 9.1 and then test it's compatibility with all other versions. So far, I've been lucky that I'm not using any critical api functions that will require me to develop the plugins in R10, so my plugins are compatible with R9.1 and up.

I do that so that the api that I'm using for development doesn't get overwritten by the latest upgrade. I have the same setup on my Mac, only on there my versions go back to 7.3. Maybe I should clean that really old stuff off of there, eh?

Adios,
Cactus Dan

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 29/10/2007 at 08:44, xxxxxxxx wrote:

1 and 2: 10.5 is strictly VS2005. I found this out the hard way as well as I was building the 10.1 32-bit version in VS6.0 (without problems). But 10.5 doesn't even have a dsw/dsp anymore, only a VS2005 vcproj. And my 10.1 build was crashing in 10.5. You may also find your plugins built in earlier versions of VS are flaky in 10.5 (but only testing will verify that). You'll want to upgrade.

Plugins built for a later version typically won't run in earlier versions of Cinema 4D.

Dan is correct here - this is my standard procedure as well. Typically, I build the cinema4dsdk in-situ to test the build, see that the sdk plugins works, and acquire the api library. Then the resource folder is copied to my development folder and all development is done there. It is simple enough to add a Post-Build Event to copy the built plugin and res folder to the Cinema 4D install and run Cinema 4D. Here's a typical Post-Build Event set for my build:

copy /Y "F:\3D Graphics\Cinema 4D\C++ SDK\Projects\interPoser Pro\Commercial\R10.5\interPoser Pro.cdl" "D:\Program Files\MAXON\CINEMA 4D R10.5 Demo\Plugins\KuroyumeDZ\interPoser Pro"
copy /Y "F:\3D Graphics\Cinema 4D\C++ SDK\Projects\interPoser Pro\res\*.*" "D:\Program Files\MAXON\CINEMA 4D R10.5 Demo\Plugins\KuroyumeDZ\interPoser Pro\res"
copy /Y "F:\3D Graphics\Cinema 4D\C++ SDK\Projects\interPoser Pro\res\description\*.*" "D:\Program Files\MAXON\CINEMA 4D R10.5 Demo\Plugins\KuroyumeDZ\interPoser Pro\res\description"
copy /Y "F:\3D Graphics\Cinema 4D\C++ SDK\Projects\interPoser Pro\res\strings_us\*.*" "D:\Program Files\MAXON\CINEMA 4D R10.5 Demo\Plugins\KuroyumeDZ\interPoser Pro\res\strings_us"
copy /Y "F:\3D Graphics\Cinema 4D\C++ SDK\Projects\interPoser Pro\res\strings_us\description\*.*" "D:\Program Files\MAXON\CINEMA 4D R10.5 Demo\Plugins\KuroyumeDZ\interPoser Pro\res\strings_us\description"
"D:\Program Files\MAXON\CINEMA 4D R10.5 Demo\CINEMA 4D Demo.exe"

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 30/10/2007 at 03:20, xxxxxxxx wrote:

OK, thanks guys. Fortunately, I did the same thing, I have 3 copied of the R10 on my hard disk. One for upgrading & working with, another 10.1 for developing, and just another 10.1 in its original state after a fresh installation (so I don't need to run the installer again when I screw anything up).

Just wanted to check if there's any possibility to port and compile my plugins to 10.5.

Will it be safe to build the plugins in a 10.1 environment, copy them to the 10.5 folder and start the 10.5 for debugging from within VisualStudio?

Greetings,
Jack

P.S.: Dan, did my post card arrive? ;-)

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 30/10/2007 at 08:10, xxxxxxxx wrote:

Howdy

> Quote: P.S.: Dan, did my post card arrive? ;-)
>
> * * *
>
> * * *

Yes, it arrived yesterday after noon. ;o)

Adios,
Cactus Dan