Compling R15 plugins in VS2010?
-
On 09/09/2013 at 14:46, xxxxxxxx wrote:
User Information:
Cinema 4D Version:
Platform:
Language(s) : C++ ;---------
Can we still use Visual Studio 2010 to compile plugins in R15?
VS 2010 uses toolset v100. And I've heard that R15 requires toolset v110.I was planning on trying it out myself on the R15 demo. But the download is really large. And I don't want to download it if VS2010 is no longer supported.
-ScottA
-
On 09/09/2013 at 16:57, xxxxxxxx wrote:
VS 2012 is required to compile the R15 SDK.
Cheers,
-Niklas -
On 09/09/2013 at 17:31, xxxxxxxx wrote:
Ouch!
I hate the look of the UI in VS2012.
Plus. I'm using OS Vista64. And VS2012 & VS2013 don't run on it. !Cry[URL-REMOVED]
This is very bad news for me.Another question:
When we install plugins someone compiled with VS2012 in R13&R14. We also have to install the MSVC 11.0 Redistributable in order to use them.
I really, really hate that. Which is another reason why I've stuck with VS2010.
Did I hear correctly that people using R15 will no longer be forced to install the MSVC 11.0 Redistributable if they use a plugin compiled with R15?-ScottA
[URL-REMOVED] @maxon: This section contained a non-resolving link which has been removed.
-
On 10/09/2013 at 01:27, xxxxxxxx wrote:
Hi Scott,
maybe you can find a way to use the VS2010 IDE with the MSVC110. Just an idea that it might be
possible, but I haven't tried it myself. I don't like the look of either of them, I don't use VS for other
than debugging. And on Mac, don't use XCode at all. PS: But don't take me as an example for that,
officially we do not support anything other than VS and XCode
Originally posted by xxxxxxxx
When we install plugins someone compiled with VS2012 in R13&R14. We also have to install the MSVC 11.0 Redistributable in order to use them.
This is correct. Over the last half a year or so, I solely compiled my plugins with MSVC110 for R13,
R14 and R15. Only few users had problems with this. Many applications you install require the 110
redistributables, too, so they may have taken care of that already. Installing the redistributables
however is simple and just 3 steps.Originally posted by xxxxxxxx
Did I hear correctly that people using R15 will no longer be forced to install the MSVC 11.0 Redistributable if they use a plugin compiled with R15?
Yes, this is also correct. The R15 installer takes care of installing the 110 redistributables to your
system. But if you copy&paste a Cinema 4D installation to another windows installation, you may
have to install the redistributables yourself.Best,
-Niklas -
On 11/09/2013 at 00:06, xxxxxxxx wrote:
I managed to compile the SDK project successfully. It is easy actually.
Go to Property Pages/Configuration Properties/General. There is a switch Platform Toolset. Set it to v100.
No idea if this could break things. The examples seem to work fine though. -
On 11/09/2013 at 09:43, xxxxxxxx wrote:
Michael, are you sure you changed the Platform Toolset to v100 when compiling the R15 SDK? You actually
need the v110 Toolset.Best,
-Niklas -
On 12/09/2013 at 00:28, xxxxxxxx wrote:
Well, quite sure ...
Whatever works.
Have you never tried to use your pre-r15 make scripts with the v100 toolset on it? -
On 12/09/2013 at 05:31, xxxxxxxx wrote:
Hm okay, this is interesting. I was under the impression that the v110 Toolkit is required since officially
you should use VS 2012 for compiling. I am not that familiar with the IDE to be honest.My make scripts do not specify the toolset, you have to execute the vcvarsall.bat before using them.
And I've been using the compiler which was delivered with the Windows 7 SDK ever since I've been
writing C++ plugins. I'll take a look at the exact version of the compiler, but my plugins require the
MSVC110.DLL redistributable which lead me to the conclusion it was the v110 toolset.
Best,
-Niklas -
On 12/09/2013 at 08:06, xxxxxxxx wrote:
Michael,
Are you using Windows7 or Vista?
-ScottA
-
On 13/09/2013 at 01:52, xxxxxxxx wrote:
Windows7
Hm okay, this is interesting. I was under the impression that the v110 Toolkit is required since officially you should use VS 2012 for compiling. I am not that familiar with the IDE to be honest.
I suppose the maxon devs switched to VC2012 and want to be on the safe side regarding compatibility problems with older versions. Can't tell what could go wrong here as i am not that technically versed.
My make scripts do not specify the toolset, you have to execute the vcvarsall.bat before using them.
And I've been using the compiler which was delivered with the Windows 7 SDK ever since I've been
writing C++ plugins. I'll take a look at the exact version of the compiler, but my plugins require the
MSVC110.DLL redistributable which lead me to the conclusion it was the v110 toolset.Ah interesting, i was thinking that there might be a compiler switch because i can also select the v90 toolkit. Now after checking, i see that the compilation commands are identical.