LuxC4D 0.06 64bit, C4D R11.5

[abstrax]

Hi all,

Sorry for the lack of any updates the last weeks. I just didn't have time for any work on LuxC4D. At least I set up now Visual Studio Express 2008 and modified it to support 64bit builds. That means I can build now 64bit plugins for C4D on Windows. While doing that I also updated the project files and source to build for C4D R11.5. I will update the Hg repository, when it's running again.

For Macintosh I will check, if I can build 64bit plugins on Mac OS 10.4. If I can, I will post them in this thread, if not, this might take a little longer.

For the last version 0.06c of LuxC4D please go to http://www.luxrender.net/forum/viewtopic.php?f=29&t=3064

As you can see, there are now a lot of combinations between different versions of Mac OS and C4D and bitness (32/64 bit). That means it's quite hard for me to make sure that all of them work. This is where I'm relying on you: I.e., please let me know if there are problems with any of these combinations. Thanks.

I hope everything works fine.

Cheers,
Marcus

EDIT: Removed plugin archives to avoid that people download the broken version.

[Phoenix]

Wow thanks, great, the development goes on!

Relating to Studio Express 2008 and 64 bit:
Please could you explain in detail and step by step how exactly you managed it to set it up to be able to build 64 bit builds?

I read about it before but it didn't work for me, but perhaps I missed something and/or did something wrong.
All my informations about it are from here: http://jenshuebel.wordpress.com/2009/02 ... t-targets/

[abstrax]

Sure it's going on. No worries. I'm just slow as a snail due to lack of time

That was the description I was using. The important thing is to install a current Windows SDK. In my case I was using the latest SDK for Windows 7, Vista and XP, you can download here:

http://www.microsoft.com/downloads/deta ... laylang=en

I was using the 64bit installer. So the installation was going to c:\program files and not(!) to c:\program files (x86). So all the paths given in the article have to be changed to c:\program files. You don't have to move the dll though as it's already the 32bit dll in the vcpackages directory. (Don't ask my why...)

Tell me if it doesn't work. I will then try to help out

Cheers,
Marcus

[Phoenix]

Sure it's going on. No worries. I'm just slow as a snail due to lack of time

That was the description I was using. The important thing is to install a current Windows SDK. In my case I was using the latest SDK for Windows 7, Vista and XP, you can download here:

http://www.microsoft.com/downloads/deta ... laylang=en

I was using the 64bit installer. So the installation was going to c:\program files and not(!) to c:\program files (x86). So all the paths given in the article have to be changed to c:\program files. You don't have to move the dll though as it's already the 32bit dll in the vcpackages directory. (Don't ask my why...)

Tell me if it doesn't work. I will then try to help out

Cheers,
Marcus

Thank you for the info, I have to test that.

Edit:
Okay, I think, the VCExppress setup for x64 worked.

But if I try to compile a C4D plugin for x64 the linking fails and I get the following error message:

2>LINK : fatal error LNK1181: cannot open input file 'kernel32.lib'

I even don't know, why "kernel32.lib" is demanded. I guess it's related to the API.

Any idea?

But, as it's rather OT perhaps we should better discuss this private. Do you use Skype?

[abstrax]

Thank you for the info, I have to test that.

Edit:
Okay, I think, the VCExppress setup for x64 worked.

But if I try to compile a C4D plugin for x64 the linking fails and I get the following error message:

2>LINK : fatal error LNK1181: cannot open input file 'kernel32.lib'

I even don't know, why "kernel32.lib" is demanded. I guess it's related to the API.

Any idea?

But, as it's rather OT perhaps we should better discuss this private. Do you use Skype?

The solution to the problem is very likely to add the Windows SDK direectories to the VC directory settings under Tools -> Options... -> Projects and Solutions -> VC++ Directories. You have to do this for the platforms Win32 and x64:

• For the executables you have to add $(WindowsSdkDir)\bin.
• For the includes you have to add $(WindowsSdkDir)\include.
• For the libraries you have to add $(WindowsSdkDir)\lib.

Then it should work. Here are 3 screenshots with the settings of the executables, includes and libraries sections of platform x64 in my installation:

vs2008expr_includes.png (11.56 KiB) Viewed 3047 times

And yes I use Skype, but I will send you a PM for that.

Cheers,
Marcus

[Phoenix]

Am I making the right assumption when I feel like these extra directories are something I may have to construct. I am a bit lost...

You have to download and install the appropriate Windows SDK (if you haven't done it yet) and refer to the respective paths in VCExpress as described above.