THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 14/01/2009 at 10:52, xxxxxxxx wrote:
Cinema 4D Version: 9.6
Platform: Mac OSX ;
im totally new to mac, just got my first mini mac today.
so i installed xcode 3.1 on leopard 10.5, and thought i was ready to go.
I followed the xcode compile steps in the c4d api, but i get like 9000 errors.
The first one says it couldnt find coreservices.h .
So do I need additional sdk's / api's besides xcode to compile c4d plugins on mac ?
is there a step by step guide somewhere that tells how to setup xcode projects ?
the instructions in the c4d api dont say anything about additional include dirs or libs, so ididnt change anything in the c4dsdk example.
actually even the build button for the sdk-examples is greyed out in xcode 3.1.
On 14/01/2009 at 11:00, xxxxxxxx wrote:
i just used the mac search tool, seems that this file is on my hd inside the developer dir. so the question is why it wasnt found during the compile..
On 14/01/2009 at 11:06, xxxxxxxx wrote:
Did you start your project using the cinema4dsdk.xcodeproj file as a template for your project? This will alleviate much anguish and hair loss.
On 14/01/2009 at 11:17, xxxxxxxx wrote:
yes i opened cinema4dsdk.xcodeproj, right-clicked the c4dsdkexample target and chose build c4dsdk..
i just wanted to rebuild the example stuff to see if everything is setup correctly..
it looks like the include <CoreServices/CoreServices.h> doesnt work, even though that file exists in the Developer-dir.
I had assumed that xcode would setup itself and the os to be aware of the sdk location. maybe i sould re-install xcode ?
On 14/01/2009 at 11:43, xxxxxxxx wrote:
Did you do this necessary step as outlined in the SDK xcode_universalbinary_migration.pdf?
It is important that you open the XCode preferences pane and change the path where XCode saves intermediate and build files. Choose a customized location somewhere on your hard drive, so that your project folders will stay clean. NEVER choose a path that is within C4D or the plugin directory!
I pointed it to a location in my Users folder.
I don't use Xcode 3.1 to build for R9.6; only R11. Otherwise, I'm using Xcode 2.4.1 for earlier C4D versions.
On 14/01/2009 at 11:52, xxxxxxxx wrote:
thanks for the info. i changed it but it makes no difference. neither R9.6 nor R11 can build the _api dependance.
i'll try to get xcode 2.4.1 and see if that works better.
On 14/01/2009 at 11:59, xxxxxxxx wrote:
Are you trying to build within the Applications folder? This may not be a good idea since it is write protected (this is new in Leopard). Again, I copy the plugins and resource folders to a location in my Users folder and build from there. This makes it conceptually easy to track your plugin projects as well:
And so on. Each build by C4D version is in its relevant location with relative referencing to proper resources.
On 14/01/2009 at 12:15, xxxxxxxx wrote:
i unpacked the demo's into my documents folder, which is in the user folder afaik, so it shouldnt be a problem..
when i check the sdk path in the project settings its alright also: Developer/SDKs/MacOSX10.4u_blah/..
On 14/01/2009 at 12:29, xxxxxxxx wrote:
i just changed the include in question by hand, to read "Developer/SDKs/..CoreServices.h" instead of <CoreServices/CoreServices.h> this solved the error in question, but now its cant find the next include CarbonCore.h ..
So it has definitely sth to do with the include paths.
i bet its really simple but as im new to mac its giving me a hard time. also its strange bc the default sdkexamples are supposed to work all by themselves without changing config afaik..
i'll poke around with the xcode settings some, maybe i find sth out..
On 15/01/2009 at 03:51, xxxxxxxx wrote:
couldnt figure it out still...
it fails to build the _api project, bc the include of the CoreServices Framework somehow doesnt work, even though the files are in their default position (/Developer/SDKs/..)
if anybody else ever had a problem with this i'd apprecciate any hints.
On 15/01/2009 at 06:20, xxxxxxxx wrote:
alright, i got it working now (tested with R9.6 and R11).
using the unchanged cinema4d sdk project, i had to do the following changes to the settings of both projects, cinema4dsdk and _api:
- change architecture to 'standard(32Bit Universal)'
- change Base SDK to 'MacOSX 10.4'
- change active architecture to 'ppc' (instead of i386)
On 15/09/2009 at 23:15, xxxxxxxx wrote:
Thanks for sharing.