|
1 | | -// |
2 | | -// CryptoSwift-Shared.xcconfig |
3 | | -// |
4 | | -// Generated by BuildSettingExtractor on 02/04/2018 |
5 | | -// https://github.com/dempseyatgithub/BuildSettingExtractor |
6 | | -// |
7 | | - |
8 | 1 | CLANG_ANALYZER_LOCALIZABILITY_NONLOCALIZED = YES |
9 | | - |
10 | | -// Require Only App-Extension-Safe API |
11 | | -// |
12 | | -// When enabled, this causes the compiler and linker to disallow use of APIs that are not |
13 | | -// available to app extensions and to disallow linking to frameworks that have not been |
14 | | -// built with this setting enabled. |
15 | | - |
16 | 2 | APPLICATION_EXTENSION_API_ONLY = YES |
17 | | - |
18 | | - |
19 | | - |
20 | | -// Compatibility Version |
21 | | -// |
22 | | -// Determines the compatibility version of the resulting library, bundle, or framework |
23 | | -// binary. See [Dynamic Library Design |
24 | | -// Guidelines](https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/DynamicLibraries/100-Articles/DynamicLibraryDesignGuidelines.html#//apple_ref/doc/uid/TP40002013-SW19) |
25 | | -// in [Dynamic Library Programming |
26 | | -// Topics](https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/DynamicLibraries/000-Introduction/Introduction.html) |
27 | | -// for details on assigning version numbers of dynamic libraries. |
28 | | - |
29 | 3 | DYLIB_COMPATIBILITY_VERSION = 1 |
30 | | - |
31 | | - |
32 | | - |
33 | | -// Current Library Version |
34 | | -// |
35 | | -// This setting defines the current version of any framework built by the project. As |
36 | | -// with `CURRENT_PROJECT_VERSION`, the value must be an integer or floating point number, |
37 | | -// such as `57` or `365.8`. By default, it is set to `$(CURRENT_PROJECT_VERSION)`. See |
38 | | -// [Dynamic Library Design |
39 | | -// Guidelines](https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/DynamicLibraries/100-Articles/DynamicLibraryDesignGuidelines.html#//apple_ref/doc/uid/TP40002013-SW19) |
40 | | -// in [Dynamic Library Programming |
41 | | -// Topics](https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/DynamicLibraries/000-Introduction/Introduction.html) |
42 | | -// for details on assigning version numbers of dynamic libraries. |
43 | | - |
44 | 4 | DYLIB_CURRENT_VERSION = 1 |
45 | | - |
46 | | - |
47 | | - |
48 | | -// Dynamic Library Install Name Base |
49 | | -// |
50 | | -// Sets the base value for the internal `install path` (`LC_ID_DYLIB`) in a dynamic |
51 | | -// library. This will be combined with the `EXECUTABLE_PATH` to form the full install |
52 | | -// path. Setting `LD_DYLIB_INSTALL_NAME` directly will override this setting. This |
53 | | -// setting defaults to the target's `INSTALL_PATH`. It is ignored when building any |
54 | | -// product other than a dynamic library. |
55 | | - |
56 | 5 | DYLIB_INSTALL_NAME_BASE = @rpath |
57 | 6 |
|
58 | | - |
59 | | - |
60 | | -// Enable Bitcode |
61 | | -// |
62 | | -// Activating this setting indicates that the target or project should generate bitcode |
63 | | -// during compilation for platforms and architectures that support it. For Archive |
64 | | -// builds, bitcode will be generated in the linked binary for submission to the App |
65 | | -// Store. For other builds, the compiler and linker will check whether the code complies |
66 | | -// with the requirements for bitcode generation, but will not generate actual bitcode. |
67 | | - |
68 | 7 | ENABLE_BITCODE = YES |
69 | | - |
70 | | - |
71 | | - |
72 | | -// Enable Bitcode |
73 | | -// |
74 | | -// Activating this setting indicates that the target or project should generate bitcode |
75 | | -// during compilation for platforms and architectures that support it. For Archive |
76 | | -// builds, bitcode will be generated in the linked binary for submission to the App |
77 | | -// Store. For other builds, the compiler and linker will check whether the code complies |
78 | | -// with the requirements for bitcode generation, but will not generate actual bitcode. |
79 | | - |
80 | 8 | ENABLE_BITCODE[sdk=macosx*] = NO |
81 | 9 |
|
82 | | - |
83 | | - |
84 | | -// Installation Directory |
85 | | -// |
86 | | -// The directory in which to install the build products. This path is prepended by the |
87 | | -// `DSTROOT`. |
88 | | - |
89 | 10 | INSTALL_PATH = $(LOCAL_LIBRARY_DIR)/Frameworks |
90 | | - |
91 | | - |
92 | | -// Runpath Search Paths |
93 | | -// |
94 | | -// This is a list of paths to be added to the `runpath` search path list for the image |
95 | | -// being created. At runtime, `dyld` uses the `runpath` when searching for dylibs whose |
96 | | -// load path begins with `@rpath/`. See [Dynamic Library Programming |
97 | | -// Topics](https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/DynamicLibraries/000-Introduction/Introduction.html). |
98 | | - |
99 | 11 | LD_RUNPATH_SEARCH_PATHS = $(inherited) @executable_path/Frameworks @loader_path/Frameworks |
100 | | - |
101 | | -// Info.plist File |
102 | | - |
103 | 12 | INFOPLIST_FILE = Info.plist |
104 | | - |
105 | | -// Product Bundle Identifier |
106 | | -// |
107 | | -// A string that uniquely identifies the bundle. The string should be in reverse DNS |
108 | | -// format using only alphanumeric characters (`A-Z`, `a-z`, `0-9`), the dot (`.`), and |
109 | | -// the hyphen (`-`). This value is used as the `CFBundleIdentifier` in the `Info.plist` |
110 | | -// of the built bundle. |
111 | | - |
112 | 13 | PRODUCT_BUNDLE_IDENTIFIER = com.krzyzanowskim.${PRODUCT_NAME:rfc1034identifier} |
113 | | - |
114 | | - |
115 | | - |
116 | | -// Product Name |
117 | | -// |
118 | | -// This is the basename of the product generated by the target. |
119 | | - |
120 | 14 | PRODUCT_NAME = $(TARGET_NAME) |
121 | | - |
122 | | - |
123 | | - |
124 | | -// Skip Install |
125 | | -// |
126 | | -// If enabled, don't install built products even if deployment locations are active. |
127 | | - |
128 | 15 | SKIP_INSTALL = YES |
0 commit comments