Stop setting -D_LIB*_DISABLE_VISIBILITY_ANNOTATIONS while building user code

This actually gets set by default by the installed config headers,
depending on how the libraries were configured.

Also, the -Xclang -flto-visibility-public-std workaround doesn't
seem to be necessary while building these test apps (but it might
potentially be necessary if building more complicated apps).
This commit is contained in:
Martin Storsjö authored and Martin Storsjo committed 2017-10-19 11:10:43 +03:00
1 parent fe547b6317
commit a53599c175
1 file changed
+2 -2
+2 -2
View File
@@ -281,10 +281,10 @@ RUN cd /build/hello && \
RUN cd /build/hello && \
for arch in armv7 aarch64 x86_64 i686; do \
$arch-w64-mingw32-clang++ hello.cpp -o hello-cpp-$arch.exe -fno-exceptions -D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -Xclang -flto-visibility-public-std -D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS || exit 1; \
$arch-w64-mingw32-clang++ hello.cpp -o hello-cpp-$arch.exe -fno-exceptions || exit 1; \
done
RUN cd /build/hello && \
for arch in armv7 x86_64 i686; do \
$arch-w64-mingw32-clang++ hello-exception.cpp -o hello-exception-$arch.exe -fsjlj-exceptions -D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -Xclang -flto-visibility-public-std -D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS || exit 1; \
$arch-w64-mingw32-clang++ hello-exception.cpp -o hello-exception-$arch.exe -fsjlj-exceptions || exit 1; \
done