THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 23/03/2010 at 14:06, xxxxxxxx wrote:
You must compile the whole API. I'm rather sceptical that the generated code runs in Cinema though, because dynamic linking is quite compiler specific.
I assume that you're trying to link an Intel compiled library?
In this case I'd rather go for process communication... Though this could be limited assuming that you work on fluid sim stuff here.
Kabe
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 23/03/2010 at 14:25, xxxxxxxx wrote:
I highly assume it should work as there are intel compiler specific definitions in the api (makes no sense if it wasn´t targeted at being built with the intel compiler)
Though compiling the API works I still get lots of warnings for it. That seems strange to me in the first place. For example for the datatype typedefs and also NULL. So I assume there is maybe an intel compiler specific settings setup available somewhere in the api. Hope the support can give me info on this.
And nope, I am not linking any other libraries. Actually I am not using external libraries at all in any of my code.
thanks anyway.
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 23/03/2010 at 20:23, xxxxxxxx wrote:
Just out of curiosity:
Why would you like to use the Intel compiler?
Trying to get an Microsoft-free household?
Kabe
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 24/03/2010 at 01:04, xxxxxxxx wrote:
Ok, I found the Intel vsprops and changed this accordingly in the project settings of my project and the api project. Then converted the projects inside to use the Intel compiler but I still get these warnings:
NULL defined to 0 (type is integer not pointer)
non-pointer conversion from "VLONG={__int64}" to "Bool={int}" may lose significant bits
non-pointer conversion from "unsigned __int64" to "LONG={long}" may lose significant bits
non-pointer conversion from "VLONG={__int64}" to "LONG={long}" may lose significant bits
Com´on, there are intel specific vsprops coming with the api so there should be someone knowing how to set this up.
Originally posted by xxxxxxxx
Just out of curiosity:
Why would you like to use the Intel compiler?
Trying to get an Microsoft-free household?Kabe
Optimized code.
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 24/03/2010 at 01:41, xxxxxxxx wrote:
Have you checked _types.h? Seems like the NULL definition in stdlib.h is pointing there. At least on the Mac side there are a number of compiler specific definitions.
Hope it helps
Kabe
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 30/03/2010 at 10:10, xxxxxxxx wrote:
thanks Kabe but _types.h? There is no such file on windows. Also NULL is the preprocessor definition of the API. I think the support should be able to clear this up.
Does really noone from the support know how to compile the api with the intel compiler? I tried converting the default SDK and API in the demo and also there I get the according errors. Does this mean it´s not possible to successfully use the Intel Compiler with the c4d api?
The api calls some preprocessor specific pragmas when the _ICL definition is available (apparently this is a definition that should be there when using the Intel compiler according to the comments in the api) but it seems that although converted to using the intel compiler this definition is not available.
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 31/03/2010 at 03:05, xxxxxxxx wrote:
I asked the developers.
cheers,
Matthias
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 31/03/2010 at 09:49, xxxxxxxx wrote:
Great and thanks!
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 19/04/2010 at 02:44, xxxxxxxx wrote:
Any news on this from the devs?
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 19/04/2010 at 03:16, xxxxxxxx wrote:
Basically you just have to redirect to the Intel project property sheets.
Giving support for the Intel compiler (or any other third party compiler) is unfortunatly beyond the scope of the MAXON SDK support.
cheers,
Matthias