The maintenance of the embedXcode template is really difficult due to Apple secrecy around and lack of documentation on Xcode.

So I'm considering switching from Xcode to another IDE.

Here's an open letter to Apple Xcode team. Feel free to send it to members of the Apple Xcode team you know.

Thank you for your help

Quote from: Open Letter to Apple Xcode Team

Dear Xcode Team,

Xcode offers superior features and ergonomics compared with other IDEs running on OS X. Unfortunately, its restricted documentation prevents from using many of its features.

I'm using Xcode as a development tool for embedded computing platforms. As at today, the embedXcode template supports Arduino, Diligent chipKIT with MPIDE, Texas Instruments' Launchpad with Energia, Leaflab Maple, Teensy, Wiring, and has received a warm welcome from the embedded computing community.

The issues I'm currently facing are mostly linked to the lack of available documentation.The books available on Xcode focus on how to use the tool, not on how to customise it. Similarly, Apple doesn't provide any clues about its inner structure. For example, keywords used by the templates are not documented. Neither is using other tool-chains, albeit the specific Toolchains folder.

Is Xcode solely limited OS X and iOS development?By just releasing some documentation on Xcode inner organisation and customisation, Apple can easily make Xcode the best choice for developers.

Otherwise, I'd have no option but to switch to another IDE and to abandon OS X.

The new Distribute target creates a specific folder Distribution which contains:• all the headers and code files, • documentation in PDF if available, • and main sketch --.pde or .ino-- in a folder with the appropriate name.

# List the libraries to be excluded# For example, WiFi may crash on Arduino 1.0.2# For example, Esplora may crash on Arduino 1.0.3# For example, Firmata may crash on Teensy 3.0#EXCLUDE_LIBS = Firmata WiFi WiFi/utility Esplora

It seems the Processing IDE is reaching its limits with the new Arduino products.

Thank you for reporting this issue. Please keep me informed of the result as I'm focused on the 1.5.x release