mac: Pull a prebuilt libc++-static.a.

third_party/libc++-static/README.chromium

Index: third_party/libc++-static/README.chromium
diff --git a/third_party/libc++-static/README.chromium b/third_party/libc++-static/README.chromium
new file mode 100644
index 0000000000000000000000000000000000000000..95dcb1d22dfc03b05988b171d25b8c5640d93185
--- /dev/null
+++ b/third_party/libc++-static/README.chromium
@@ -0,0 +1,57 @@
+Short Name: libcxx
+Name: Descriptive name of the package
+Short Name: Name the package is distributed under (ex. libxml, openssl, etc)
+Security Critical: Yes
+License: MIT
+Version: r245965
+
+To upload:
+  python ~/depot_tools/upload_to_google_storage.py -b chromium-libcpp third_party/libc++-static.a
+
+To initialize gsutil's credentials:
+  python ~/depot_tools/third_party/gsutil/gsutil config
+
+  That will give a URL which you should log into with your web browser. The
+  username should be the one that is on the ACL for the "chromium-libcpp"
+  bucket (probably your @google.com address). Contact the build team for help
+  getting access if necessary.
+
+  Copy the code back to the command line util. Ignore the project ID (it's OK
+  to just leave blank when prompted).
+
+gsutil documentation:
+  https://developers.google.com/storage/docs/gsutil
+
+
+To build:
+
+cd /tmp/

[Mark Mentovai, 2015/10/22 21:54:27]

This is basically a script. Can you make it a real build.sh or something?

[Nico, 2015/10/22 22:05:41]

Yeah, I really should. Will do.

+mkdir tmp
+cd tmp
+svn co --force https://llvm.org/svn/llvm-project/libcxx/trunk@245965 libcxx
+svn co --force https://llvm.org/svn/llvm-project/libcxxabi/trunk@245965 libcxxabi
+
+mkdir libcxxbuild
+cd libcxxbuild
+mkdir libcxx
+mkdir libcxxabi
+cd libcxx
+
+sed -i '' 's/"default"/"hidden"/g' ../../libcxx/include/__config
+
+c++ -c -nostdinc++ -I../../libcxx/include/ -O3 -std=c++11 -fstrict-aliasing ../../libcxx/src/*.cpp -fvisibility=hidden -fvisibility-inlines-hidden -mmacosx-version-min=10.6 -arch i386 -arch x86_64

[Mark Mentovai, 2015/10/22 21:54:27]

Whose c++, Chrome’s or the system’s? Preferably Chrome’s, right?

[Nico, 2015/10/22 22:05:41]

That'd be better, yes. Will change.

+
+cd ../libcxxabi
+sed -i '' 's/"default"/"hidden"/g' ../../libcxxabi/src/*
+sed -i '' 's/push(default)/push(hidden)/g' ../../libcxxabi/src/*
+
+c++ -c -nostdinc++ -I../../libcxx/include/ -I../../libcxxabi/include -O3 -std=c++11 -fstrict-aliasing ../../libcxxabi/src/*.cpp -fvisibility=hidden -fvisibility-inlines-hidden -mmacosx-version-min=10.6 -arch i386 -arch x86_64

[Mark Mentovai, 2015/10/22 21:54:27]

Where do these object files go?

[Nico, 2015/10/22 22:05:41]

Note the subtle first * in `libcxx*/*.o` in the libtool line below :-)

[Mark Mentovai, 2015/10/22 22:57:45]

Nico wrote:
DOH!

+
+cd ..
+
+libtool -static -o libc++-static.a libcxx*/*.o
+
+And then:
+cp libc++-static.a path/to/chrome/src/third_party/libc++-static
+cd path/to/chrome/src
+python ~/depot_tools/upload_to_google_storage.py -b chromium-libcpp third_party/libc++-static.a

[Mark Mentovai, 2015/10/22 21:54:27]

depot_tools should be in the PATH for most people, and
upload_to_google_storage.py is +x, so this can just be
“upload_to_google_storage.py -b …”