THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 06/05/2004 at 12:09, xxxxxxxx wrote:
Cinema 4D Version: 8.503
Platform: Windows ; Mac ;
Language(s) : C++ ;
As some of you may know, the free set of MS compilers is not enough to compile plugins for Cinema, coz you need the Windows header files and lib.exe to create the required API library.
Are there any technical or legal reasons that would prevent Maxon (or me, for that matter) to distribute the compiled _api_v8_rel.lib?
Of course the library works only with that specific version of the API and only with the MS compiler.
Any comments or deeper insight?
As always, thanks a lot!
On 07/05/2004 at 00:32, xxxxxxxx wrote:
Without knowing anything about the legal ramifications of the original question, a clever way around it would be to include the API files directly in the plugin project. This is the way it was done before R8. The drawback is that the API files has to be recompiled for every plugin.
On 07/05/2004 at 00:39, xxxxxxxx wrote:
Mh, but that still requires the Windows header files, or am I wrong here?
If I'm wrong, why are they required to build the library then?
On 07/05/2004 at 07:55, xxxxxxxx wrote:
You can get windows.h free as part of Microsoft's Platform SDK.
But according to one of the MAXON programmers, distributing a prebuilt lib file would be fine. Thanks for your effort in bringing a free compiler to C4D.
On 07/05/2004 at 08:55, xxxxxxxx wrote:
Actually I think that the praise should go to remotion, who provided the first useable description of the whole process.
All I'm trying to do is to automate that task and make it easier accessible to others.
On 09/05/2004 at 16:16, xxxxxxxx wrote:
I didn't test it, but "link /lib" should behave like "lib". I will do some tests the next days. I'm currently working on a Python script for dependency extraction. Together with GNU make the build process should become quite comfortable.
On 10/05/2004 at 04:27, xxxxxxxx wrote:
Yes,"link /lib" is working.