[llvm-dev] Statically linking against libc++ (original) (raw)
C Bergström via llvm-dev llvm-dev at lists.llvm.org
Mon Apr 10 01:42:54 PDT 2017
- Previous message: [llvm-dev] Statically linking against libc++
- Next message: [llvm-dev] Statically linking against libc++
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-DBUILD_SHARED_LIBS=OFF should be exactly that, but as I think someone else indicated there's a bit of work for it to actually be what it advertises to be.
This could get gray when you consider that you really need to decide - did you mean compiler internal libs or runtime stuff. libomp.so vs libLLVM.so is two entirely different use cases.
Did you want to disable ever being able to use a shared lib or just build a static version of the compiler so that it's portable.
Shameless self promotion, but this does the latter while preserving the former.. Nice clean wrapper around everything that makes a compiler that is portable and has all the pieces you need bundled together.. https://github.com/pathscale/clang-suite
To avoid confusion - that link depends only on open source stuff
On Mon, Apr 10, 2017 at 3:55 PM, Carsten Mattner via llvm-dev <llvm-dev at lists.llvm.org> wrote:
On Mon, Apr 10, 2017 at 4:59 AM, Mehdi Amini <mehdi.amini at apple.com> wrote:
Note that -DBUILDSHAREDLIBS=OFF is not a special settings, this is the default. Is there a so=NEVER setting?
LLVM Developers mailing list llvm-dev at lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
- Previous message: [llvm-dev] Statically linking against libc++
- Next message: [llvm-dev] Statically linking against libc++
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]