• Nano
• Home
• Licence
• Mailing List
• Screenshots
• Version History
• Getting Started
• Quick Start
• Building Nano
• Getting the Code
• Contributing Code
• Reporting Bugs
• Nano Features
• High Performance
• Nano Features
• Nano Views
• Nano Resources
• Custom Cursors
• Custom Menu Items
• Building Applications
• Building Applications
• Adding Documents
• Adding Preferences
• Adding One-Line Undo
• Adding Software Update
• Using Controllers
• Using Carbon Events
• Using HIViews
• Using Functors
• Reference Guide
• Utility Code
• Class Overview
• Coding Standards

Building Nano

Nano expects Xcode 2.4 or higher, and is typically built with gcc 4.x.

Xcode Configuration

All Nano projects contain Debug and Release configurations. These configurations obtain their values from external .xcconfig files, contained in Support/Xcode/Configuration.

These .xcconfig files will maximize warnings in debug builds and minimize the final binary size in release builds. The details of each configuration can be adjusted to meet your own needs, since Nano does not require these particular choices.

By default, debug builds are performed for the current architecture while release builds are built as Universal Binaries. This behaviour can be changed by adjusting the ARCHS setting in the .xcconfig files.

Nano Projects

Nano projects do not apply any settings at the project level, and are customized at the target level. Targets contain minimal customisations, with most configuration performed through .xcconfig files.

Nano is typically built as a stand-alone static library, however this style of build is not required. Nano can also be built by including the relevant source code directly in your project.

Language Settings

If compiling Nano source directly in your project, you will need to apply the correct language settings to individual source files; all source should be built as C++, except those .cpp files which also contain Objective-C.

Unfortunately a bug in Xcode (rdar://5259110) means that the per-file language setting is ignored if the target-level language setting is set to anything other than "by file type".

As such, you will need to set the language setting individually for those files who do not match Xcode's extension-based rules (.c files must be modified to C++, and .cpp files that use Objective-C must be set to Obj-C++).