1 Xestia Calendar OS X Development
2 ====================================
4 Xestia Calendar uses Xcode to build the application for OS X.
6 Step 1: Location of Frameworks and Libraries
7 ============================================
9 When you open up the Xcode project for the first time, you will see the
10 Frameworks & Libraries section will contain several red (missing) items.
12 The required frameworks & libraries are:
18 Click on each framework that is in red and then the little folder icon
19 on the right hand side to locate each library.
21 You may need to set these libraries up again so that they are copied over
22 during the Copy Files phase.
24 Where possible, please build the libraries as "fat" binaries (with i686
27 Step 2: Setup user Settings
28 ===========================
30 The following user settings are used for finding frameworks and libraries
33 =========================================================================
34 | Setting Name | Setting Description |
35 =========================================================================
36 | CURL_FRAMEWORKPATH | Path to the cURL framework |
37 | SQLITE3_FRAMEWORKPATH | Path to the libsqlite3 framework |
38 | LIBXML2_PATH | Path to the libxml2 library |
39 =========================================================================
41 To add the user settings, select the project, click on Build Settings,
42 click on the add button and select the Add User Setting button, enter one
43 of the setting names from above with the value set as the path to where
49 Select the bitmapcode target first and click on the Run button at the
50 top of the Xcode window. This will build and run the bitmapcode helper
51 which will generate the required code and headers for the images used
54 Now select the Xestia Calendar target and click on the Run button
55 again at the top of the Xcode window. This will build and run Xestia
58 At the end of the build process, it will copy the frameworks and libraries
59 over into the executable.
61 Release executables tend to be smaller but cannot be debugged as easily
62 compared to the Debug executables.