Compiling under Mac R10 demo



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 08/10/2009 at 08:53, xxxxxxxx wrote:

    User Information:
    Cinema 4D Version:   R10 
    Platform:    Mac  ;  
    Language(s) :     C++  ;

    ---------
    Hi everyone,

    I'm trying to compile my plugin for the Mac using an old R10.008 demo version. When I compile the SDK example, I get a small executable (release version is 920K as opposed to 4.2Mb on R11). I also see that the C4D executable is about 23Mb in R10 compared to 64Mb in R11.

    In the Xcode Project menu the active architecture which can be selected is either ppc or i386, whereas the R11 version has ppc64 and x86_64 in that menu as well.

    So my question is, is it possible to compile and test UB plugins including 64 bit versions using the 10.008 demo on a Mac? I'm just wondering if this is restricted to 32 bit only, which would be disappointing. Everything is fine on the PC, so is it some configuration setting I'm missing? In the build configuration, the 64 and 32 bit versions for ppc and intel are shown as valid architectures, so I'm a bit puzzled about why this is happening. I should also say that the compiled plugin works fine in the C4D demo of R10. However, I can't test 32 and 64 bit operation as doing 'get info' for the C4D executable doesn't have the 'run in 32 bit' checkbox as later versions do.



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 08/10/2009 at 09:02, xxxxxxxx wrote:

    1. There is no MacOS 64-bit R10 version of Cinema 4D. 64-bit was introduced in R11 (requiring MacOS 10.5 and a 64-bit capable Mac computer).

    2. You should ALWAYS use the cinema4dsdk project as a template for your projects. I'm assuming you did. :)

    3. NEVER change the active architecture for C4D plugin builds in Xcode - it is already set (in the cinema4dsdk project) to create the proper Universal Binary dylib to cover all systems coverable. In 32-bit, you'll get two links (PPC and Intel 32-bit) which are combined into the dylib. In 64-bit, you'll get four links (PPC/Intel, 32/64-bit) which are combined into the dylib.

    4. Finally, Don't Use R10.008. It was inherently unstable and quickly updated to avoid crashes and other unstable behavior. Use R10.102 at least (software and SDK).



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 08/10/2009 at 11:30, xxxxxxxx wrote:

    Quote: Originally posted by kuroyume0161 on 08 October 2009
    >
    > * * *
    >
    > 1. There is no MacOS 64-bit R10 version of Cinema 4D. 64-bit was introduced
    > in R11 (requiring MacOS 10.5 and a 64-bit capable Mac computer).
    >
    > * * *

    Aha! That explains it. So, I should produce one Mac version for R10 and another one for R11+, is that correct?

    > Quote: _2. You should ALWAYS use the cinema4dsdk project as a template for your projects. I'm assuming you did. :)
    >
    > * * *
    _


    Yes, did that.

    > Quote: _3. NEVER change the active architecture for C4D plugin builds in Xcode - it is already set (in the cinema4dsdk project) to create the proper Universal Binary dylib to cover all systems coverable. In 32-bit, you'll get two links (PPC and Intel 32-bit) which are combined into the dylib. In 64-bit, you'll get four links (PPC/Intel, 32/64-bit) which are combined into the dylib.
    >
    > * * *
    _


    Yes, that's exactly what I got. I left the active architecture strictly alone! I just didn't understand why I didn't get a 64 bit build when using the R10 SDK. I wish Maxon would document this stuff somewhere (maybe they do and I haven't found it?).

    > Quote: 4. Finally, Don't Use R10.008. It was inherently unstable and quickly updated to avoid crashes and other unstable behavior. Use R10.102 at least (software and SDK).
    >
    > * * *
    >
    > * * *

    Oh, believe me, I would love to use a better version of R10. Since Maxon won't make a demo of it available, I'm reduced to using one from a book CD, and that's 10.008. Unless there's another source for the older demos, I'm stuck with this one.



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 08/10/2009 at 12:21, xxxxxxxx wrote:

    Yes, two versions, one for R10/R10.5 and another for R11+.

    An update is still available:

    R10 downloads

    Don't know if the SDK version being used would have any effect on people who use it with R10.102+ but either way, if you can use the update on the demo, the SDK would be updated as well.

    I would make a copy of the Cinema 4D install folder, call it CINEMA 4D R10.1 and install the update to that so that you don't corrupt the R10.008 install until you've verified the efficacy of the update application. Then you could just delete the R10.008 install folder and go on as usual.



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 08/10/2009 at 14:11, xxxxxxxx wrote:

    Many thanks for confirming the need for two versions, that's very helpful.

    In fact, I already tried the updater and it runs but tells you that it can't/won't update the demo version, so it looks like I'm stuck with 10.008 unfortunately.


Log in to reply