Skip to content
Browse files

changed gitignore file and updated xcconfig files

  • Loading branch information...
1 parent cadc451 commit 4151d99cec63440bf7f58041862a75d635eb0685 @couchdeveloper committed Jul 18, 2012
View
2 .gitignore
@@ -15,7 +15,7 @@ DerivedData
## exclude user specific files and folders
-user.*
+$user.*
#exclude generated html files in folder "doc":
View
4 Bench/Bench.debug.xcconfig
@@ -8,8 +8,8 @@
JP_ROOT = "$(SRCROOT)/../Source"
-#include "../Xcode.config/user.boost.xcconfig"
-#include "../Xcode.config/user.ICU.xcconfig"
+#include "../Xcode.config/$user.boost.xcconfig"
+#include "../Xcode.config/$user.ICU.xcconfig"
BENCH_HEADER_SEARCH_PATHS = $(JP_ROOT) $(BOOST_HEADER_SEARCH_PATHS) $(ICU_HEADER_SEARCH_PATHS)
View
4 Bench/Bench.release.xcconfig
@@ -4,8 +4,8 @@
JP_ROOT = "$(SRCROOT)/../Source"
-#include "../Xcode.config/user.boost.xcconfig"
-#include "../Xcode.config/user.ICU.xcconfig"
+#include "../Xcode.config/$user.boost.xcconfig"
+#include "../Xcode.config/$user.ICU.xcconfig"
BENCH_HEADER_SEARCH_PATHS = $(JP_ROOT) $(BOOST_HEADER_SEARCH_PATHS) $(ICU_HEADER_SEARCH_PATHS)
View
2 Bench/unicode_conversion/unicode_conversion.debug.xcconfig
@@ -3,4 +3,4 @@
//
-#include "../../Xcode.config/user.ICU.xcconfig"
+#include "../../Xcode.config/$user.ICU.xcconfig"
View
2 Bench/unicode_conversion/unicode_conversion.release.xcconfig
@@ -2,4 +2,4 @@
// unicode_conversion.release.xcconfig
//
-#include "../../Xcode.config/user.ICU.xcconfig"
+#include "../../Xcode.config/$user.ICU.xcconfig"
View
281 Bench/user.bench-results/AGJsonParser Benchmark.txt
@@ -1,281 +0,0 @@
-ag-macbookpro:Release$ ./AGJsonParser
-Mon Mar 12 16:22:09 2012
-
-Clang version 3.1 (tags/Apple/clang-318.0.54)
-2012-03-12 16:22:09.713 AGJsonParser[32914:707] Start Bench
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Using a NSString as input and interface method:
-parseString:options:error: (JPJsonParser)
-options: (JPJsonParserCreateMutableContainers) 0
-Input file: Test-UTF8-esc.json, size: 24539, encoding: NSUTF8StringEncoding
-AGJsonParser: elapsed time for parsing:
-min: 0.649 ms, max: 0.994 ms, avg: 0.674 ms
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Using a NSData with UTF-8 content as input and interface method:
-parseData:options:error: (JPJsonParser)
-options: JPJsonParserCreateMutableContainers
-The input encoding will be detected automatically
-Input file: Test-UTF8-esc.json, size: 24539, encoding: NSUTF8StringEncoding
-2012-03-12 16:22:11.308 AGJsonParser[32914:707] JPJsonParser: elapsed time for parsing:
-min: 0.552 ms, max: 0.907 ms, avg: 0.575 ms
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Class JPJsonParserUsing a NSData with UTF-8 content as input and interface method:
-+parseData:options:error:
-options: none
-The input encoding will be detected automatically
-Input file: Test-UTF8-esc.json, size: 24539, encoding: NSUTF8StringEncoding
-2012-03-12 16:22:12.027 AGJsonParser[32914:707] JPJsonParser: elapsed time for parsing:
-min: 0.551 ms, max: 1.136 ms, avg: 0.562 ms
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Class JPJsonParserUsing a NSData with UTF-8 content as input and interface method:
-+parseData:options:error:
-options: none
-The input encoding will be detected automatically
-Input file: Test-UTF8-esc.json, size: 24539, encoding: NSUTF8StringEncoding
-2012-03-12 16:22:12.743 AGJsonParser[32914:707] JPJsonParser: elapsed time for parsing:
-min: 0.552 ms, max: 0.953 ms, avg: 0.559 ms
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Class JPJsonParserUsing a NSData with UTF-8 content as input and interface method:
-+parseData:semanticActions:
-Semantic Actions: JPStreamSemanticActions
-The input encoding will be detected automatically
-Input file: Test-UTF8-esc.json, size: 24539, encoding: NSUTF8StringEncoding
-2012-03-12 16:22:12.855 AGJsonParser[32914:707] AGJsonParser: elapsed time for parsing:
-min: 0.105 ms, max: 0.198 ms, avg: 0.110 ms
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Timing includes destruction of objects, too
-Using a NSData with UTF-8 content as input and interface method:
-parseData:options:error: (JPJsonParser)
-options: JPJsonParserCreateMutableContainers
-The input encoding shall be set explicitly
-Input file: Test-UTF8-esc.json, size: 24539, encoding: NSUTF8StringEncoding
-2012-03-12 16:22:13.584 AGJsonParser[32914:707] JPJsonParser: elapsed time for parsing:
-min: 0.710 ms, max: 1.217 ms, avg: 0.727 ms
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Asynchronous Parser, using a NSData with UTF-8
-content as input.
-Timing measures the average time including destruction
-of JSON objects. The semantic actions object is kept alive,
-giving it and advantage, since key strings are cached.
-This test is not directly comparable to the others.
-Input file: Test-UTF8-esc.json, size: 24539, encoding: NSUTF8StringEncoding
-2012-03-12 16:22:14.444 AGJsonParser[32914:707] JPJsonParser: elapsed time for parsing 1000 documents:
-average: 0.857 s
-
---------------------------------------------
-Running bench_JSONKit1 1000 times.
---------------------------------------------
-using a NSData with UTF-8 content as input,
-interface method: mutableObjectWithData: (JSONDecoder),
-JKParseOptionFlags = 0
-Input file: Test-UTF8-esc.json, size: 24539, encoding: NSUTF8StringEncoding
-2012-03-12 16:22:15.130 AGJsonParser[32914:707] JSONKit: elapsed time for parsing:
-min: 0.536 ms, max: 0.957 ms, avg: 0.547 ms
-
---------------------------------------------
-Running bench_JSONKit2 1000 times.
---------------------------------------------
-Timing includes destruction of objects
-using a NSData with UTF-8 content as input,
-interface method: mutableObjectWithData: (JSONDecoder),
-JKParseOptionFlags = 0
-Input file: Test-UTF8-esc.json, size: 24539, encoding: NSUTF8StringEncoding
-2012-03-12 16:22:15.812 AGJsonParser[32914:707] JSONKit: elapsed time for parsing:
-min: 0.669 ms, max: 1.093 ms, avg: 0.681 ms
-
---------------------------------------------
-Running bench_JSONKitString1 1000 times.
---------------------------------------------
-using a NSString as input,
-interface method: mutableObjectWithData: (JSONDecoder),
-JKParseOptionFlags = 0
-Input file: Test-UTF8-esc.json, size: 24539, encoding: NSUTF8StringEncoding
-2012-03-12 16:22:16.630 AGJsonParser[32914:707] JSONKit: elapsed time for parsing:
-min: 0.631 ms, max: 1.093 ms, avg: 0.663 ms
-
---------------------------------------------
-Running NSJSONSerialization bench 1000 times.
---------------------------------------------
-using a NSData with UTF-8 content as input,
-interface method: JSONObjectWithData:options:error:,
-options: NSJSONReadingMutableContainers
-Input file: Test-UTF8-esc.json, size: 24539, encoding: NSUTF8StringEncoding
-2012-03-12 16:22:17.659 AGJsonParser[32914:707] NSJSONSerialization: elapsed time for parsing:
-min: 0.824 ms, max: 9.050 ms, avg: 0.850 ms
-
---------------------------------------------
-Running NSJSONSerialization bench 1000 times.
---------------------------------------------
-Timing includes destruction of objects, too
-using a NSData with UTF-8 content as input,
-interface method: JSONObjectWithData:options:error:,
-options: NSJSONReadingMutableContainers
-Input file: Test-UTF8-esc.json, size: 24539, encoding: NSUTF8StringEncoding
-2012-03-12 16:22:18.668 AGJsonParser[32914:707] NSJSONSerialization: elapsed time for parsing:
-min: 0.998 ms, max: 1.583 ms, avg: 1.006 ms
-
-
-
-//=====================================
-
-
-ag-macbookpro:Release$ ./AGJsonParser
-Mon Mar 12 16:23:53 2012
-
-Clang version 3.1 (tags/Apple/clang-318.0.54)
-2012-03-12 16:23:53.064 AGJsonParser[32951:707] Start Bench
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Using a NSString as input and interface method:
-parseString:options:error: (JPJsonParser)
-options: (JPJsonParserCreateMutableContainers) 0
-Input file: Test-UTF8.json, size: 24274, encoding: NSUTF8StringEncoding
-AGJsonParser: elapsed time for parsing:
-min: 0.551 ms, max: 0.872 ms, avg: 0.558 ms
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Using a NSData with UTF-8 content as input and interface method:
-parseData:options:error: (JPJsonParser)
-options: JPJsonParserCreateMutableContainers
-The input encoding will be detected automatically
-Input file: Test-UTF8.json, size: 24274, encoding: NSUTF8StringEncoding
-2012-03-12 16:23:54.506 AGJsonParser[32951:707] JPJsonParser: elapsed time for parsing:
-min: 0.548 ms, max: 0.784 ms, avg: 0.561 ms
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Class JPJsonParserUsing a NSData with UTF-8 content as input and interface method:
-+parseData:options:error:
-options: none
-The input encoding will be detected automatically
-Input file: Test-UTF8.json, size: 24274, encoding: NSUTF8StringEncoding
-2012-03-12 16:23:55.221 AGJsonParser[32951:707] JPJsonParser: elapsed time for parsing:
-min: 0.544 ms, max: 1.111 ms, avg: 0.561 ms
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Class JPJsonParserUsing a NSData with UTF-8 content as input and interface method:
-+parseData:options:error:
-options: none
-The input encoding will be detected automatically
-Input file: Test-UTF8.json, size: 24274, encoding: NSUTF8StringEncoding
-2012-03-12 16:23:55.952 AGJsonParser[32951:707] JPJsonParser: elapsed time for parsing:
-min: 0.548 ms, max: 0.899 ms, avg: 0.572 ms
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Class JPJsonParserUsing a NSData with UTF-8 content as input and interface method:
-+parseData:semanticActions:
-Semantic Actions: JPStreamSemanticActions
-The input encoding will be detected automatically
-Input file: Test-UTF8.json, size: 24274, encoding: NSUTF8StringEncoding
-2012-03-12 16:23:56.059 AGJsonParser[32951:707] AGJsonParser: elapsed time for parsing:
-min: 0.104 ms, max: 0.214 ms, avg: 0.105 ms
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Timing includes destruction of objects, too
-Using a NSData with UTF-8 content as input and interface method:
-parseData:options:error: (JPJsonParser)
-options: JPJsonParserCreateMutableContainers
-The input encoding shall be set explicitly
-Input file: Test-UTF8.json, size: 24274, encoding: NSUTF8StringEncoding
-2012-03-12 16:23:56.803 AGJsonParser[32951:707] JPJsonParser: elapsed time for parsing:
-min: 0.708 ms, max: 1.179 ms, avg: 0.742 ms
-
---------------------------------------------
-Running AGJsonParser bench 1000 times.
---------------------------------------------
-Asynchronous Parser, using a NSData with UTF-8
-content as input.
-Timing measures the average time including destruction
-of JSON objects. The semantic actions object is kept alive,
-giving it and advantage, since key strings are cached.
-This test is not directly comparable to the others.
-Input file: Test-UTF8.json, size: 24274, encoding: NSUTF8StringEncoding
-2012-03-12 16:23:57.636 AGJsonParser[32951:707] JPJsonParser: elapsed time for parsing 1000 documents:
-average: 0.832 s
-
---------------------------------------------
-Running bench_JSONKit1 1000 times.
---------------------------------------------
-using a NSData with UTF-8 content as input,
-interface method: mutableObjectWithData: (JSONDecoder),
-JKParseOptionFlags = 0
-Input file: Test-UTF8.json, size: 24274, encoding: NSUTF8StringEncoding
-2012-03-12 16:23:58.334 AGJsonParser[32951:707] JSONKit: elapsed time for parsing:
-min: 0.527 ms, max: 0.866 ms, avg: 0.557 ms
-
---------------------------------------------
-Running bench_JSONKit2 1000 times.
---------------------------------------------
-Timing includes destruction of objects
-using a NSData with UTF-8 content as input,
-interface method: mutableObjectWithData: (JSONDecoder),
-JKParseOptionFlags = 0
-Input file: Test-UTF8.json, size: 24274, encoding: NSUTF8StringEncoding
-2012-03-12 16:23:59.031 AGJsonParser[32951:707] JSONKit: elapsed time for parsing:
-min: 0.664 ms, max: 1.164 ms, avg: 0.695 ms
-
---------------------------------------------
-Running bench_JSONKitString1 1000 times.
---------------------------------------------
-using a NSString as input,
-interface method: mutableObjectWithData: (JSONDecoder),
-JKParseOptionFlags = 0
-Input file: Test-UTF8.json, size: 24274, encoding: NSUTF8StringEncoding
-2012-03-12 16:24:00.182 AGJsonParser[32951:707] JSONKit: elapsed time for parsing:
-min: 0.691 ms, max: 1.785 ms, avg: 0.718 ms
-
---------------------------------------------
-Running NSJSONSerialization bench 1000 times.
---------------------------------------------
-using a NSData with UTF-8 content as input,
-interface method: JSONObjectWithData:options:error:,
-options: NSJSONReadingMutableContainers
-Input file: Test-UTF8.json, size: 24274, encoding: NSUTF8StringEncoding
-2012-03-12 16:24:01.166 AGJsonParser[32951:707] NSJSONSerialization: elapsed time for parsing:
-min: 0.763 ms, max: 1.108 ms, avg: 0.804 ms
-
---------------------------------------------
-Running NSJSONSerialization bench 1000 times.
---------------------------------------------
-Timing includes destruction of objects, too
-using a NSData with UTF-8 content as input,
-interface method: JSONObjectWithData:options:error:,
-options: NSJSONReadingMutableContainers
-Input file: Test-UTF8.json, size: 24274, encoding: NSUTF8StringEncoding
-2012-03-12 16:24:02.138 AGJsonParser[32951:707] NSJSONSerialization: elapsed time for parsing:
-min: 0.937 ms, max: 1.537 ms, avg: 0.970 ms
-
-
-
View
39 Bench/user.bench-results/json_parser Benchmark.txt
@@ -1,39 +0,0 @@
-===============================
-Parser Benchmark
-===============================
-Mon Mar 12 16:28:37 2012
-
-Clang version 3.1 (tags/Apple/clang-318.0.54)
-using vector<char> iterators
-start parsing 1000 times ...
-SemanticActionsTest average elapsed time for:
-push string (0): 0.000 ms
-pop operations: 0.000 ms
-array push_back operations(0): 0.000 ms
-object insert operations(0): 0.000 ms
-Input encoding: UTF-8
-Unicode noncharacter handling: SignalErrorOnUnicodeNoncharacter
-
-Basic Json Parser Options:
- Check For Duplicate Keys: YES
- Parse Multiple Documents: NO
- Check For Spurious Trailing Bytes: NO
-
-Extensions
- Allow Comments: NO
- Allow Control Characters: NO
- Allow Leading Plus In Numbers: NO
- Allow Leading Zeros In Integers: NO
-
-Log Level: LogLevelWarning
-Semantic Actions elapsed time:0.000 µs
-Semantic Actions number of parsed items:
- string-cache size: 35
- max stack items: 91
-Performance counters:
-push string: 0.000 µs
-build array: 0.000 µs
-build object: 0.000 µs
-
-... end parsing
-JsonParser: elapsed time: min: 0.422 ms, max: 5.209 ms, avg: 0.442 ms
View
1,115 Bench/user.bench-results/unicode_conversion Benchmark.txt
@@ -1,1115 +0,0 @@
-Mon Mar 12 16:33:27 2012
-
-Clang version 3.1 (tags/Apple/clang-318.0.54)
-=====================================
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-8
- 100% single bytes.
-
-JP: 2.866 µs
-ICU: 2.206 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-8
- 100% double bytes.
-
-JP: 6.307 µs
-ICU: 3.405 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-8
- 100% triple bytes.
-
-JP: 9.752 µs
-ICU: 4.196 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-8
- 100% quad bytes.
-
-JP: 13.898 µs
-ICU: 20.071 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-8
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 9.767 µs
-ICU: 8.756 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-8
- 80% single 15% double 5% triple bytes.
-
-JP: 6.033 µs
-ICU: 4.803 µs
-
-
-=====================================
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-8
- 100% single bytes.
-
-JP: 1.816 µs
-ICU: 4.087 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-8
- 100% single bytes.
-
-JP: 2.154 µs
-ICU: 4.076 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-8
- 100% double bytes.
-
-JP: 5.176 µs
-ICU: 7.646 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-8
- 100% double bytes.
-
-JP: 5.964 µs
-ICU: 7.645 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-8
- 100% triple bytes.
-
-JP: 8.810 µs
-ICU: 11.647 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-8
- 100% triple bytes.
-
-JP: 10.781 µs
-ICU: 11.606 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-8
- 100% quad bytes.
-
-JP: 13.148 µs
-ICU: 17.000 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-8
- 100% quad bytes.
-
-JP: 14.335 µs
-ICU: 16.988 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-8
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 10.864 µs
-ICU: 12.265 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-8
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 9.247 µs
-ICU: 12.469 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-8
- 80% single 15% double 5% triple bytes.
-
-JP: 6.688 µs
-ICU: 7.306 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-8
- 80% single 15% double 5% triple bytes.
-
-JP: 5.602 µs
-ICU: 7.528 µs
-
-
-=====================================
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-8
- 100% single bytes.
-
-JP: 4.366 µs
-ICU: 11.794 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-8
- 100% single bytes.
-
-JP: 4.366 µs
-ICU: 11.723 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-8
- 100% double bytes.
-
-JP: 5.606 µs
-ICU: 15.356 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-8
- 100% double bytes.
-
-JP: 5.832 µs
-ICU: 15.307 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-8
- 100% triple bytes.
-
-JP: 7.623 µs
-ICU: 19.336 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-8
- 100% triple bytes.
-
-JP: 7.728 µs
-ICU: 19.261 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-8
- 100% quad bytes.
-
-JP: 12.375 µs
-ICU: 22.186 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-8
- 100% quad bytes.
-
-JP: 12.247 µs
-ICU: 22.113 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-8
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 9.775 µs
-ICU: 19.476 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-8
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 9.914 µs
-ICU: 19.729 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-8
- 80% single 15% double 5% triple bytes.
-
-JP: 7.283 µs
-ICU: 15.111 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-8
- 80% single 15% double 5% triple bytes.
-
-JP: 7.174 µs
-ICU: 15.133 µs
-
-
-=====================================
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-16LE
- 100% single bytes.
-
-JP: 2.602 µs
-ICU: 5.930 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-16BE
- 100% single bytes.
-
-JP: 2.587 µs
-ICU: 6.349 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-16LE
- 100% double bytes.
-
-JP: 5.667 µs
-ICU: 13.581 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-16BE
- 100% double bytes.
-
-JP: 5.667 µs
-ICU: 13.382 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-16LE
- 100% triple bytes.
-
-JP: 7.905 µs
-ICU: 15.504 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-16BE
- 100% triple bytes.
-
-JP: 7.932 µs
-ICU: 15.356 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-16LE
- 100% quad bytes.
-
-JP: 11.456 µs
-ICU: 21.620 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-16BE
- 100% quad bytes.
-
-JP: 12.033 µs
-ICU: 21.586 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-16LE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 9.470 µs
-ICU: 15.654 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-16BE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 9.345 µs
-ICU: 15.737 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-16LE
- 80% single 15% double 5% triple bytes.
-
-JP: 5.833 µs
-ICU: 10.246 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-16BE
- 80% single 15% double 5% triple bytes.
-
-JP: 5.783 µs
-ICU: 9.974 µs
-
-
-=====================================
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-16LE
- 100% single bytes.
-
-JP: 1.215 µs
-ICU: 6.009 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-16LE
- 100% single bytes.
-
-JP: 1.634 µs
-ICU: 6.070 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-16BE
- 100% single bytes.
-
-JP: 2.331 µs
-ICU: 6.040 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-16BE
- 100% single bytes.
-
-JP: 2.667 µs
-ICU: 5.968 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-16LE
- 100% double bytes.
-
-JP: 4.370 µs
-ICU: 6.006 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-16LE
- 100% double bytes.
-
-JP: 4.370 µs
-ICU: 6.043 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-16BE
- 100% double bytes.
-
-JP: 2.441 µs
-ICU: 6.047 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-16BE
- 100% double bytes.
-
-JP: 2.185 µs
-ICU: 6.002 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-16LE
- 100% triple bytes.
-
-JP: 7.140 µs
-ICU: 6.002 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-16LE
- 100% triple bytes.
-
-JP: 7.143 µs
-ICU: 6.062 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-16BE
- 100% triple bytes.
-
-JP: 6.755 µs
-ICU: 6.066 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-16BE
- 100% triple bytes.
-
-JP: 6.755 µs
-ICU: 6.089 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-16LE
- 100% quad bytes.
-
-JP: 7.939 µs
-ICU: 12.413 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-16LE
- 100% quad bytes.
-
-JP: 8.357 µs
-ICU: 12.469 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-16BE
- 100% quad bytes.
-
-JP: 9.929 µs
-ICU: 12.412 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-16BE
- 100% quad bytes.
-
-JP: 10.336 µs
-ICU: 12.357 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-16LE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 7.758 µs
-ICU: 7.600 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-16LE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 7.739 µs
-ICU: 7.671 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-16BE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 8.271 µs
-ICU: 7.672 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-16BE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 9.047 µs
-ICU: 7.468 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-16LE
- 80% single 15% double 5% triple bytes.
-
-JP: 4.490 µs
-ICU: 5.976 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-16LE
- 80% single 15% double 5% triple bytes.
-
-JP: 4.784 µs
-ICU: 6.037 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-16BE
- 80% single 15% double 5% triple bytes.
-
-JP: 5.169 µs
-ICU: 6.055 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-16BE
- 80% single 15% double 5% triple bytes.
-
-JP: 5.716 µs
-ICU: 6.002 µs
-
-
-=====================================
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-16LE
- 100% single bytes.
-
-JP: 3.171 µs
-ICU: 13.755 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-16LE
- 100% single bytes.
-
-JP: 3.171 µs
-ICU: 13.739 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-16BE
- 100% single bytes.
-
-JP: 1.600 µs
-ICU: 13.747 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-16BE
- 100% single bytes.
-
-JP: 2.776 µs
-ICU: 13.819 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-16LE
- 100% double bytes.
-
-JP: 3.171 µs
-ICU: 13.758 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-16LE
- 100% double bytes.
-
-JP: 3.171 µs
-ICU: 13.736 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-16BE
- 100% double bytes.
-
-JP: 1.600 µs
-ICU: 13.758 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-16BE
- 100% double bytes.
-
-JP: 2.776 µs
-ICU: 13.725 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-16LE
- 100% triple bytes.
-
-JP: 3.171 µs
-ICU: 13.765 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-16LE
- 100% triple bytes.
-
-JP: 3.171 µs
-ICU: 13.739 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-16BE
- 100% triple bytes.
-
-JP: 1.600 µs
-ICU: 13.989 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-16BE
- 100% triple bytes.
-
-JP: 2.776 µs
-ICU: 13.686 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-16LE
- 100% quad bytes.
-
-JP: 3.186 µs
-ICU: 17.640 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-16LE
- 100% quad bytes.
-
-JP: 3.492 µs
-ICU: 17.655 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-16BE
- 100% quad bytes.
-
-JP: 3.590 µs
-ICU: 17.618 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-16BE
- 100% quad bytes.
-
-JP: 4.509 µs
-ICU: 17.561 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-16LE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 3.537 µs
-ICU: 15.205 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-16LE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 3.631 µs
-ICU: 15.100 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-16BE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 2.451 µs
-ICU: 15.164 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-16BE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 3.262 µs
-ICU: 14.930 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-16LE
- 80% single 15% double 5% triple bytes.
-
-JP: 3.171 µs
-ICU: 13.762 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-16LE
- 80% single 15% double 5% triple bytes.
-
-JP: 3.171 µs
-ICU: 13.758 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-16BE
- 80% single 15% double 5% triple bytes.
-
-JP: 1.600 µs
-ICU: 13.746 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-16BE
- 80% single 15% double 5% triple bytes.
-
-JP: 2.776 µs
-ICU: 13.759 µs
-
-
-=====================================
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-32LE
- 100% single bytes.
-
-JP: 2.950 µs
-ICU: 8.704 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-32BE
- 100% single bytes.
-
-JP: 3.051 µs
-ICU: 8.109 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-32LE
- 100% double bytes.
-
-JP: 5.369 µs
-ICU: 16.260 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-32BE
- 100% double bytes.
-
-JP: 5.949 µs
-ICU: 15.654 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-32LE
- 100% triple bytes.
-
-JP: 7.988 µs
-ICU: 18.224 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-32BE
- 100% triple bytes.
-
-JP: 8.264 µs
-ICU: 17.660 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-32LE
- 100% quad bytes.
-
-JP: 10.404 µs
-ICU: 22.449 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-32BE
- 100% quad bytes.
-
-JP: 10.785 µs
-ICU: 22.404 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-32LE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 9.435 µs
-ICU: 18.692 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-32BE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 9.552 µs
-ICU: 17.976 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-32LE
- 80% single 15% double 5% triple bytes.
-
-JP: 6.033 µs
-ICU: 12.971 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-8 to UTF-32BE
- 80% single 15% double 5% triple bytes.
-
-JP: 5.840 µs
-ICU: 12.281 µs
-
-
-=====================================
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-32LE
- 100% single bytes.
-
-JP: 1.955 µs
-ICU: 8.937 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-32LE
- 100% single bytes.
-
-JP: 2.534 µs
-ICU: 8.930 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-32BE
- 100% single bytes.
-
-JP: 2.323 µs
-ICU: 8.369 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-32BE
- 100% single bytes.
-
-JP: 2.685 µs
-ICU: 8.332 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-32LE
- 100% double bytes.
-
-JP: 2.489 µs
-ICU: 8.934 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-32LE
- 100% double bytes.
-
-JP: 4.374 µs
-ICU: 8.938 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-32BE
- 100% double bytes.
-
-JP: 2.625 µs
-ICU: 8.377 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-32BE
- 100% double bytes.
-
-JP: 4.404 µs
-ICU: 8.316 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-32LE
- 100% triple bytes.
-
-JP: 6.759 µs
-ICU: 8.912 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-32LE
- 100% triple bytes.
-
-JP: 7.155 µs
-ICU: 8.919 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-32BE
- 100% triple bytes.
-
-JP: 6.778 µs
-ICU: 8.392 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-32BE
- 100% triple bytes.
-
-JP: 4.814 µs
-ICU: 8.324 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-32LE
- 100% quad bytes.
-
-JP: 9.929 µs
-ICU: 13.234 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-32LE
- 100% quad bytes.
-
-JP: 10.332 µs
-ICU: 13.257 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-32BE
- 100% quad bytes.
-
-JP: 9.929 µs
-ICU: 13.219 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-32BE
- 100% quad bytes.
-
-JP: 7.969 µs
-ICU: 13.178 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-32LE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 8.460 µs
-ICU: 10.328 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-32LE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 7.638 µs
-ICU: 10.374 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-32BE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 8.670 µs
-ICU: 9.665 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-32BE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 7.434 µs
-ICU: 9.689 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-32LE
- 80% single 15% double 5% triple bytes.
-
-JP: 5.226 µs
-ICU: 8.930 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-32LE
- 80% single 15% double 5% triple bytes.
-
-JP: 5.523 µs
-ICU: 8.927 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16LE to UTF-32BE
- 80% single 15% double 5% triple bytes.
-
-JP: 5.327 µs
-ICU: 8.361 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-16BE to UTF-32BE
- 80% single 15% double 5% triple bytes.
-
-JP: 5.048 µs
-ICU: 8.328 µs
-
-
-=====================================
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-32LE
- 100% single bytes.
-
-JP: 1.204 µs
-ICU: 16.635 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-32LE
- 100% single bytes.
-
-JP: 1.607 µs
-ICU: 16.664 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-32BE
- 100% single bytes.
-
-JP: 1.272 µs
-ICU: 16.118 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-32BE
- 100% single bytes.
-
-JP: 1.604 µs
-ICU: 15.940 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-32LE
- 100% double bytes.
-
-JP: 1.204 µs
-ICU: 16.589 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-32LE
- 100% double bytes.
-
-JP: 1.603 µs
-ICU: 16.603 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-32BE
- 100% double bytes.
-
-JP: 1.321 µs
-ICU: 16.084 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-32BE
- 100% double bytes.
-
-JP: 1.604 µs
-ICU: 15.948 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-32LE
- 100% triple bytes.
-
-JP: 1.204 µs
-ICU: 16.615 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-32LE
- 100% triple bytes.
-
-JP: 1.603 µs
-ICU: 16.619 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-32BE
- 100% triple bytes.
-
-JP: 1.294 µs
-ICU: 16.080 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-32BE
- 100% triple bytes.
-
-JP: 1.607 µs
-ICU: 15.982 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-32LE
- 100% quad bytes.
-
-JP: 1.600 µs
-ICU: 18.405 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-32LE
- 100% quad bytes.
-
-JP: 1.999 µs
-ICU: 18.473 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-32BE
- 100% quad bytes.
-
-JP: 1.645 µs
-ICU: 18.518 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-32BE
- 100% quad bytes.
-
-JP: 2.112 µs
-ICU: 18.352 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-32LE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 1.995 µs
-ICU: 17.821 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-32LE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 2.308 µs
-ICU: 17.595 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-32BE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 2.147 µs
-ICU: 17.331 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-32BE
- 60% single 25% double 10% triple 5% quad bytes.
-
-JP: 2.346 µs
-ICU: 17.004 µs
-
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-32LE
- 80% single 15% double 5% triple bytes.
-
-JP: 1.204 µs
-ICU: 16.630 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-32LE
- 80% single 15% double 5% triple bytes.
-
-JP: 1.603 µs
-ICU: 16.623 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32LE to UTF-32BE
- 80% single 15% double 5% triple bytes.
-
-JP: 1.351 µs
-ICU: 16.054 µs
-
--------------------------------------------
- Converting 1000 code units in UTF-32BE to UTF-32BE
- 80% single 15% double 5% triple bytes.
-
-JP: 1.607 µs
-ICU: 15.937 µs
-
View
17 CHANGES.md
@@ -41,3 +41,20 @@
#### Issues
* Documentation generator Appledoc generates documentation for private classes and categories.
+
+
+
+### Version 0.4 beta
+
+#### Changes
+
+* .gitignore: changed 'user.' to '$user.' as a file name prefix in order to ingore user specific files. This affects the xcconfig files which users of the JPJson package requires to rename their user specific xcconfig files, e.g from "user.boost.xcconfig" to "$user.boost.xcconfig".
+
+* JPJsonWriter: fixed a bug in converting NSNumber objects whose underlaying type equals BOOL and whose address is not equal `kCFBooleanTrue` or not equal `kCFBooleanFalse`.
+
+* JPJsonWriter: improved performance and memory foot print when serializing NSString objects whose internal encoding is not Unicode.
+
+* Updated Project settings for iOS applications and iOS static library to match the Apple recommended way to link against a static library (which resolves an issue when archiving a project, but does not fix the issue when evaluating the dependecies - which has still bugs in Xcode 4.3.3).
+
+* The recommended version for boost in now 1.50
+
View
2 Examples/FoundationExamples/common.xcconfig
@@ -2,7 +2,7 @@
// common.xcconfig
//
-#include "../../Xcode.config/user.boost.xcconfig"
+#include "../../Xcode.config/$user.boost.xcconfig"
// Source Root Path
View
10 INSTALL.md
@@ -29,7 +29,7 @@ If you are only interested in compiling the JPJson *libraries* which you need fo
### Installing Boost
-The JPJson lib depends on [boost](http://www.boost.org/). In order to build JPJson libraries, you need to install boost on your *developer machine*, unless you haven't done it so far. For JPJson it suffices to just download the most recent boost archive and put the decompressed folder anywhere on your local disk and you are done. The version of boost shall be the newest one, which is at the time of writing v1.49.0.
+The JPJson lib depends on [boost](http://www.boost.org/). In order to build JPJson libraries, you need to install boost on your *developer machine*, unless you haven't done it so far. For JPJson it suffices to just download the most recent boost archive and put the decompressed folder anywhere on your local disk and you are done. The version of boost shall be the newest one, which is at the time of writing v1.50.0.
Other ways to install boost is to use one of the package managers available for Mac OS X, for instance [MacPorts](http://www.macports.org/) or [Homebrew](http://mxcl.github.com/homebrew/).
@@ -155,11 +155,11 @@ Note: Don't add a trailing '/'.
The JPJson package requires a few user specific Xcode config files. There are three template files as default config files and these are probably already fine, but there is the need to rename the default Xcode config files in order to prevent them to be tracked by the VCS.
-Locate the Xcode config files prefixed with `default` with the JPJson package and change the prefix from `default` to `user`:
+Locate the Xcode config files prefixed with `default` with the JPJson package and change the prefix from `default` to `$user`:
-`default.boost.xcconfig` becomes `user.boost.xcconfig`
-`default.gtest.xcconfig` becomes `user.gtest.xcconfig`
-`default.ICU.xcconfig` becomes `user.ICU.xcconfig`
+`default.boost.xcconfig` becomes `$user.boost.xcconfig`
+`default.gtest.xcconfig` becomes `$user.gtest.xcconfig`
+`default.ICU.xcconfig` becomes `$user.ICU.xcconfig`
You probably don't need to make changes to the configuration itself, but in case you have, these files are kept as user settings and will not be tracked by git.
View
9 JPJson.xcworkspace/contents.xcworkspacedata
@@ -321,9 +321,6 @@
<FileRef
location = "group:NSURLConnectionDownload/NSURLConnectionDownload.xcodeproj">
</FileRef>
- <FileRef
- location = "group:DemoApp/DemoApp.xcodeproj">
- </FileRef>
</Group>
<FileRef
location = "group:FoundationExamples/FoundationExamples.xcodeproj">
@@ -481,13 +478,13 @@
</FileRef>
</Group>
<FileRef
- location = "group:user.boost.xcconfig">
+ location = "group:$user.boost.xcconfig">
</FileRef>
<FileRef
- location = "group:user.gtest.xcconfig">
+ location = "group:$user.gtest.xcconfig">
</FileRef>
<FileRef
- location = "group:user.ICU.xcconfig">
+ location = "group:$user.ICU.xcconfig">
</FileRef>
<FileRef
location = "group:JP_link_static_lib.xcconfig">
View
2 Libraries/Mac OS X Libraries/common.xcconfig
@@ -3,7 +3,7 @@
//
-#include "../../Xcode.config/user.boost.xcconfig"
+#include "../../Xcode.config/$user.boost.xcconfig"
// Source Root Path
View
2 Libraries/iOS Libraries/iOS.debug.xcconfig
@@ -2,7 +2,7 @@
// iOS.debug.xcconfig
//
-#include "../../Xcode.config/user.boost.xcconfig"
+#include "../../Xcode.config/$user.boost.xcconfig"
// Source Root Path
JP_ROOT = "$(SRCROOT)/../../Source"
View
2 Libraries/iOS Libraries/iOS.release.xcconfig
@@ -2,7 +2,7 @@
// iOS.release.xcconfig
//
-#include "../../Xcode.config/user.boost.xcconfig"
+#include "../../Xcode.config/$user.boost.xcconfig"
// Source Root Path
JP_ROOT = "$(SRCROOT)/../../Source"
View
6 Test/Test.debug.xcconfig
@@ -6,6 +6,6 @@
// Source Root Path
JP_ROOT = $(SRCROOT)/../Source
-#include "../Xcode.config/user.boost.xcconfig"
-#include "../Xcode.config/user.gtest.xcconfig"
-#include "../Xcode.config/user.ICU.xcconfig"
+#include "../Xcode.config/$user.boost.xcconfig"
+#include "../Xcode.config/$user.gtest.xcconfig"
+#include "../Xcode.config/$user.ICU.xcconfig"
View
6 Test/Test.release.xcconfig
@@ -5,6 +5,6 @@
// Source Root Path
JP_ROOT = $(SRCROOT)/../Source
-#include "../Xcode.config/user.boost.xcconfig"
-#include "../Xcode.config/user.gtest.xcconfig"
-#include "../Xcode.config/user.ICU.xcconfig"
+#include "../Xcode.config/$user.boost.xcconfig"
+#include "../Xcode.config/$user.gtest.xcconfig"
+#include "../Xcode.config/$user.ICU.xcconfig"
View
2 Xcode.config/default.ICU.xcconfig
@@ -3,7 +3,7 @@
//
//
// This file is meant for a template for user settings. Don't change this file!
-// In your project, rename this file to user.ICU.xconfig
+// In your project, rename this file to $user.ICU.xconfig
//
// This configuration is only required in the test suite. The following
View
2 Xcode.config/default.boost.xcconfig
@@ -3,7 +3,7 @@
//
//
// This file is meant for a template for user settings. Don't change this file!
-// In your project, rename this file to user.boost.xconfig
+// In your project, rename this file to $user.boost.xconfig
//
// Configuration for boost.
View
2 Xcode.config/default.gtest.xcconfig
@@ -2,7 +2,7 @@
// default.gtest.xcconfig
//
// This file is meant for a template for user settings. Don't change this file!
-// In your project, rename this file to user.gtest.xconfig
+// In your project, rename this file to $user.gtest.xconfig
//

0 comments on commit 4151d99

Please sign in to comment.
Something went wrong with that request. Please try again.