File: README

package info (click to toggle)
libkml 1.3.0~r864%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 27,396 kB
  • ctags: 13,514
  • sloc: cpp: 65,998; sh: 19,598; ansic: 13,333; python: 3,289; makefile: 2,645; xml: 1,806; php: 223; java: 195; ruby: 109; perl: 108
file content (27 lines) | stat: -rw-r--r-- 1,182 bytes parent folder | download | duplicates (9)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
This Xcode project has two targets:
  - An OS X Framework directly usable as an embedded Framework in other Xcode
    projects.
  - A static library, suitable for programs that cannot link dynamically with
    libkml (e.g. iPhone projects).

The static library is self-explantory.

The standard installation path for an OS X Framework created in Xcode is:
$(HOME)/Library/Frameworks

To enable an embeddable Framework, the installation path in this project is
set to: @executable_path/../Frameworks

For more information on this, see:
http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPFrameworks/Tasks/CreatingFrameworks.html

A traditional Framework has all its header files in a single Headers
directory in the Framework bundle. Since libkml has its header files spread
throughout multiple levels of directory hierarchy, there is some extra
manipulation necessary in order for all include paths to be satisfied. If you
want to see the gory details, see the "Run Script" build phase of the LibKML
target. However, as an end user of the Framework all you need to do is:
#include <LibKml/LibKml.h>.

The Xcode project was made with Xcode 3.1.3 on OS X 10.5.8