Xcode Eclipse Mac OS X Toolchain

Xcode Eclipse Mac OS X Toolchain

And I wanted to use the Mac OS X toolchain that is provided with Xcode.

I am running OS X (10.7.4) Xcode 4.3.2, and I checked, and I do have Command Line Tools installed.

When I go to Eclipse - Preferences - New CDT Project Wizard - Toolchains: all I see is GNU Autotools Toolchain I dont see the Mac OS X GCC toolchain.

How do I get the Mac OS X GCC toolchain to appear in the toolchain selection in Eclipse.

Provide details and share your research But avoid Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

Not the answer youre looking for Browse other questions tagged xcode eclipse gcc toolchain or ask your own question.

Choose the target CPU architecture x86 (64-bit) and click Apply so you can also update the libraries next.

In my last post on remote development of CUDA applications, I covered NSEEs cross compilation mode.

In this post I will focus on the using NSEEs synchronized project mode.

In this scenario, the code is compiled natively on the target system as Figure 1 shows.

The remote target system can be a CUDA-supported x8664 Linux target or an ARM-based platform like the Jetson TK1 system.

I am using Mac OS X 10.8.5 on my host system (with Xcode 5.1.1 installed) and 64-bit Ubuntu 12.04 on my target system.

Then download the latest 64-bit CUDA 6.5 package for Mac (Im using cuda6.5.14mac64.pkg ) and double-click to install the package.

Please note that if you have a Jetson TK1 as your target system, the current Jetson TK1 OS image for L4T (Linux for Tegra) does not contain the latest CUDA 6.5 toolkit.

This support will be available in a future release (Rel21.2), but in the meantime you can use the CUDA 6.0 toolkit archive.

You can check the L4T version with the following command.

Click on File-New-CUDA CC Project to launch the project creation wizard.

Enter project name particles, select Import CUDA Sample, as the project type and select CUDA Toolkit 6.5 from the available tool chains.

The remaining options in the wizard let you choose which GPU and CPU architectures to generate code for.

First, we will choose the GPU code that the nvcc compiler should generate.

Nsight will default to the GPU architecture that it detects on the host system.

On my Mac OS X system I have a Geforce GT 650M, so Nsight defaults PTX (virtual ISA) and GPU SASS code generation to SM3.0.

My target Linux system also has a kepler GPU so SM3.0 is the correct architecture for Nsight to target.

But if your target system has an older GPU, then check the SM1.1 or SM2.0 PTX check box to generate PTX code that the CUDA driver will JIT (just-in-time) compile to the architecture on the target system.

Note if you have an ARM target you can also select ARM as the target CPU architecture.

Click Finish and you should see the particles sample opened in Nsight and ready to use.

Nsight will index all the headers when it opens the project for the first time, so let it complete this operation before creating a remote build on the target system.

In the properties UI click on Build-Target Systems which shows the UI for selecting the remote connection settings.

Click on Manage and then click Add to enter the host IP address and user name of the target system.

When you click Finish you will see the entry for the new target system that you just added.

Next, click on Browse to choose a project path on the target system and click on Manage to choose the toolkit path from the target system.

In the dialog that pops up you can click on Detect to let Nsight auto-detect the installed toolkit path for you.

Xcode Eclipse For Mac