<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 10, 2017, at 6:49 AM, Carsten Mattner <<a href="mailto:carstenmattner@gmail.com" class="">carstenmattner@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Mon, Apr 10, 2017 at 8:42 AM, C Bergström <<a href="mailto:cbergstrom@pathscale.com" class="">cbergstrom@pathscale.com</a>> wrote:<br class=""><blockquote type="cite" class="">-DBUILD_SHARED_LIBS=OFF should be exactly that, but as I think<br class="">someone else indicated there's a bit of work for it to actually be<br class="">what it advertises to be.<br class=""></blockquote><br class="">Mehdi wrote it's correct for all of the listed dynlibs to be<br class="">installed.<br class=""></div></div></blockquote><div><br class=""></div><div>I can be wrong as well :)</div><div><br class=""></div><div>But here that’s not my reading of the documentation: <a href="http://llvm.org/docs/CMake.html" class="">http://llvm.org/docs/CMake.html</a></div><div><br class=""></div><div><dt style="font-family: 'Lucida Grande', 'Lucida Sans Unicode', Geneva, Verdana, sans-serif; font-size: 14px;" class=""><strong class="">BUILD_SHARED_LIBS</strong>:BOOL</dt><dd style="margin-top: 3px; margin-bottom: 10px; margin-left: 30px; -webkit-hyphens: auto; font-family: 'Lucida Grande', 'Lucida Sans Unicode', Geneva, Verdana, sans-serif; font-size: 14px;" class=""><div style="margin-right: 0px; margin-bottom: 0.5em; margin-left: 0px; -webkit-hyphens: auto; margin-top: 0px !important;" class="">Flag indicating if each LLVM component (e.g. Support) is built as a shared library (ON) or as a static library (OFF). Its default value is OFF. On Windows, shared libraries may be used when building with MinGW, including mingw-w64, but not when building with the Microsoft toolchain.</div></dd><div class=""><br class=""></div></div><div><br class=""></div><div><br class=""></div><div>This applies to the individual LLVM component. I don’t think the shared lib you mentioned are part of this.</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""><blockquote type="cite" class="">This could get gray when you consider that you really need to decide<br class="">- did you mean compiler internal libs or runtime stuff. libomp.so vs<br class="">libLLVM.so is two entirely different use cases.<br class=""></blockquote><br class="">Yep, I'm talking about zero LLVM libs needed at runtime after linking,<br class="">unlike say libstdc++ and libgcc needed in your typical Linux<br class="">executable.<br class=""></div></div></blockquote><div><br class=""></div><div>When I build clang, I always get libc++.so and libc++.a ; I don’t think there is an option to have clang always link libc++ statically afterward though. I believe it requires to opt-in explicitly when you link with clang.</div><div><br class=""></div></div>— <div class="">Mehdi</div><div class=""><br class=""></div></body></html>