diff options
| author | Martin Storsjö <martin@martin.st> | 2023-11-07 11:48:12 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-11-07 11:48:12 +0200 |
| commit | 0d3eeac8c0f45410398a87f72ae38ea6ae1c3073 (patch) | |
| tree | 31510c5fd7d4ce58840f04ef5d527c6c245fc84c /lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp | |
| parent | 0a362f12ec60a49a054befec8620a8e69523af54 (diff) | |
| download | llvm-0d3eeac8c0f45410398a87f72ae38ea6ae1c3073.zip llvm-0d3eeac8c0f45410398a87f72ae38ea6ae1c3073.tar.gz llvm-0d3eeac8c0f45410398a87f72ae38ea6ae1c3073.tar.bz2 | |
[clang-repl] Fix BUILD_SHARED_LIBS symbols from libclangInterpreter on MinGW (#71393)
A few symbols within libclangInterpreter have got explicit dllexport
attributes, in order to make them exported (and thus visible at runtime)
in any build, not only when they are part of e.g. a DLL libclang-cpp,
but also when they are part of a plain .exe.
Due to the explicit dllexports, these symbols would sidestep the regular
MinGW logic of exporting all symbols if there are no dllexports.
Therefore, for libclang-cpp, a separate fix was made in
592e935e115ffb451eb9b782376711dab6558fe0, to pass --export-all-symbols
to the build of libclang-cpp.
If building with BUILD_SHARED_LIBS enabled, then the same issue appears
in libclangInterpreter; pass the same flag --export-all-symbols there as
well, to make sure all symbols are visible, not only the ones that are
explicitly marked as dllexport.
Diffstat (limited to 'lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp')
0 files changed, 0 insertions, 0 deletions