THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 08/01/2009 at 15:26, xxxxxxxx wrote:
Cinema 4D Version:
according to the C++ - C4d-SDK-HTML for R11, there should be a example-SDK-Project with all necessary setting to learn and start from.
But where is it to find ?
On 08/01/2009 at 15:43, xxxxxxxx wrote:
Cinema 4D install folder under plugins/cinema4dsdk maybe? ;)
On 08/01/2009 at 16:54, xxxxxxxx wrote:
Thanks Robert, I found it.
Now I tried to build the SDK Examples according to this tutorial: http://www.astrofish.com/tutorials/c4dtagplugin/index.html , but Visual C++ 2005 exits with this fault:
2>LINK : fatal error LNK1181: Eingabedatei "..\..\resource\_api_lib\_api_win32_release.lib" kann nicht geöffnet werden.
Any ideas what's wrong ?
The required file _api_win32_release.lib seems not to exist anywhere.
On 08/01/2009 at 19:06, xxxxxxxx wrote:
That is an old tutorial. You should just be opening the cinema4dsdk.vcproj in VS2005. Unless you are doing 64-bit, there shouldn't be any changes required. I'm using VS2005 for both 32-bit and 64-bit and these compiled without warnings/errors on Windows XP Pro (32/64). Which version of VS2005? The Express edition may be problematic - need to search here for previous posts about it.
On 09/01/2009 at 03:41, xxxxxxxx wrote:
Thanks for the reply, Robert.
I didn't do any changes to the cinema4dsdk.vcproj, simply loaded it in C++ and compiled.
Is the missing : "..\..\resource\_api_lib\_api_win32_release.lib" generated during the compiler-process (by C++) or should it already be there ?
The folder where it should be located is the C4d-resource-folder, not a folder inside the sdk-plugin. But the R11-C4d-folder doesn't contain this fle.
I use the actual available version of visual studio C++ express, version 8.0.50727.42 (RTM.050727-4200) and .NET 2.0.50727 SP2. Maybe I need to change some settings of C++ after loading the cinema4dsdk.vcproj-file ?
Thanks for any help.
Btw., very nice plugins, Robert ;)
On 09/01/2009 at 03:53, xxxxxxxx wrote:
Check if the Project Dependencies of the 'cinema4dsdk' project depend on '_api' project within the VS project.
On 09/01/2009 at 13:01, xxxxxxxx wrote:
yes, that's the case.
The checkbox _api has a hook.
Should I deactivate it for the compilation ?
Maybe any folder-settings or compiler-settings that need to be changed ?
On 09/01/2009 at 13:46, xxxxxxxx wrote:
The checkbox for '_api' has to be active. You have to make sure the api lib has been compiled.
Anyway there should be actually nothing required to change. You just load the VS project and hit compile. I have no idea why it is not working for you.
On 09/01/2009 at 15:35, xxxxxxxx wrote:
maybe it's because I didn't install my C4D in the default c:-Path and instead in a custom path on another partition?
Maybe the Compiler/linker does not find some files in this case ?
On 10/01/2009 at 06:42, xxxxxxxx wrote:
I have two log-files here , first is the one that describes the usual fault,
second one occurs when I build the _api with C++_2008 and then recompile the C4D-SDK with C++_2005 and give it the needed '_api_win32_release.lib' during the compilation process by copiing it in the demanded folder.
On 11/01/2009 at 08:32, xxxxxxxx wrote:
Try the following: open cinema4dsdk.vcproj (not dsw or dsp or anything) and press STRG+ALT+F7 to compile the whole project. If it doesn't work, there might be s.th. wrong with your vc installation. Is it "Express" or "Professional"? Express won't work without installing Platform SDK, I think.
On 11/01/2009 at 12:59, xxxxxxxx wrote:
Hi Klaus, thanks for the help.
The Strg+Alt+F7 gave the same fault result.
I use VS_2005_C++ Express Edition. I installed it right how the downloadable MS-installer did it automatically.
And I think you have the absolute right idea, I just found the info on a site of Microsoft.
I definetely need to download and install the Microsoft Windows Server 2003 R2 Platform SDK to produce 32 and 64 bit code.
With the blank C++-install, only .net apps are possible, but no 32 & 64 bit native apps.
Thanks, I will post if that was the solution.
On 11/01/2009 at 15:27, xxxxxxxx wrote:
Ok, got it fixed ;)
Thanks to Klaus' advice, I found this site:
There is all explained about getting the C++ express-edition to produce native 32 & 64bit code.
Now it all works fine and compiles without any error.
Thanks again, Klaus.
On 11/01/2009 at 15:54, xxxxxxxx wrote:
One last question for the moment,
for building a 64 bit .cdl (.cdl64), is this possible out of a 32bit XP-C++-Installation or do I have to install C++ on a 64bit system to produce 64bit-cdl's ?
How do you handle this ?
On 11/01/2009 at 16:10, xxxxxxxx wrote:
Yes, if you have the 64 bit target installed. I'm not so sure that Express has 64 bit capability but if so, that's it. Unfortunately, you have to install VS with the 64bit target. You could try "Add or Remove Programs" to see if you can do additional feature installions otherwise it would need to be a reinstall.
On 12/01/2009 at 00:44, xxxxxxxx wrote:
C++ Express has in the 32bitXP-installation a 64 bit target that can be selected, but when I compile with that, no cdl64 is generated, instead the compiler skips all necessary steps.
But no problem, I have a 64bit system where I can install the whole stuff again and try if it works there.