Xcode build settings


Xcode build locations may mislead developers hoping to fully control the output of the IDE. While we can use CONFIGURATION_BUILD_DIR for the xcodebuild tool during continuous integration, IDE generates files in different locations, and sometimes we want to control it too.



First, misleading part:


Per-configuration Build Products Path states "build/Debug-iphoneos", however it's not true - the output is controlled by the workspace settings (File -> Workspace Settings... -> Advanced):


However, using workspace settings is not flexible enough and may have some issues. In particular, we can't save these settings into the version control: it's per-user basis, and we do not usually want to save xcuserdata directory into the VCS.

It looks like the Xcode GUI for the Build Locations section is not always working properly, and it shows the build location for the legacy mode by default (Xcode prior version 4) where SYMROOT settings (Build Product Path) was used. However, the documentation for settings is correct:

Per-configuration Build Products Path

CONFIGURATION_BUILD_DIR

The base path where build products will be placed during a build for a given configuration. By default this is set to `$(BUILD_DIR)/$(CONFIGURATION)`.

Workspace settings does set up this BUILD_DIR and by modifying this particular setting, we can control the build products output. The same about intermediate build files:

Per-configuration Intermediate Build Files Path

CONFIGURATION_TEMP_DIR

The base path where intermediates will be placed during a build for a given configuration. By default this is set to `$(PROJECT_TEMP_DIR)/$(CONFIGURATION)`.

BUILD_DIR and PROJECT_TEMP_DIR do not have entries in the Build Settings page, but we can set those up with User-Defined Settings:

BUILD_DIR = $(SRCROOT)/Build/Products
PROJECT_TEMP_DIR = $(SRCROOT)/Build/Intermediates

Please note that you can set up any paths there, the example refers to the path relative to the project root with the names consistent with the default ones.

Comments

Post a Comment

Popular posts from this blog

Web application framework comparison by memory consumption

Memory consumption is slightly specific to my area of software development now, but I did some research recently and maybe these results can be useful for others. Of course, I know that precious comparison is very difficult to carry out, but actually I needed only overall picture. And let me admit that results are pretty interesting and even frustrated (at least for me). As a basis I took so-starving project, and measured initial RSS (Resident Set Size) of the each process (local development webservers). Platform: x86_64 Linux (latest Ubuntu with all updates). As a reference, here is the RSS of the interpreters in interactive console mode: Interpreter Version RSS (kB) stackless python 2.6.4 3916 ruby (via irb) 1.8.7 4664 python 2.7.1 5624 php 5.3.5 6924 v8 (via node.js shell) 2.5.9.9 8796 One more reference - the most simplest WSGI app ( example  in the Python documentation). It's RSS: 7336 Kb , so I assume it's almost impossible to consume l
Read more

Trac Ticket Workflow

Trac is the wiki and issue tracking system that is the most used for my software development projects. Let me share few hints about its ticket workflow, especially about the statuses, the roles of the participants, and let me give an example of the workflow config. But if you are interested in other things like Trac plugins, source browser, customizing, etc, let me know. All the information given below regards the workflow described at the end of the article. The original Trac workflow is missed vital features like the support for ticket verifying, or the required ticket statuses range, so I do not use it in my projects. The description of the main statuses: new - the ticket has been created; in-progress - the developer has began to work with the ticket; fixed - the ticket is fixed (the problem issued in the ticket is solved); verified - the ticket is verified (tester or PM has verified that the ticket is fixed correctly); closed - the ticket is closed (it's not
Read more

Shellcode detection using libemu

Shellcode can be seen as a list of instructions that has been developed in a manner that allows it to be injected in an application during runtime. Each security researcher face the shellcodes during their work, and in this article I'll show how to detect shellcodes using Python (via libemu Python binding). Few words about libemu : libemu is a small library written in C offering basic x86 emulation and shellcode detection using GetPC heuristics. Intended use is within network intrusion/prevention detections and honeypots. The information on the site is not actual in some places, so I'll give direct and clear instruction how to get and install libemu. Clone the git repository: $ git clone git://git.carnivore.it/libemu.git Firstly, configure, make and install libemu itself (without binding): $ autoreconf -v -i $ ./configure --prefix=/opt/libemu $ make $ sudo make install If you set up prefix as shown above, you have to add the library path to /etc/ld.so.conf file
Read more