diff options
| author | Jon Turney <jon.turney@dronecode.org.uk> | 2018-06-02 18:12:10 +0100 |
|---|---|---|
| committer | Nirbheek Chauhan <nirbheek.chauhan@gmail.com> | 2018-06-07 12:57:39 +0000 |
| commit | 1f5c6d62bf1e88ae24dce79b5d7a586e8f783371 (patch) | |
| tree | dd60d405ef275549f2e7b108dd7867d3257f1e10 /mesonbuild/backend/ninjabackend.py | |
| parent | a7fc3fe3561c0b15a5263192a1645c765adf0ec2 (diff) | |
| download | meson-1f5c6d62bf1e88ae24dce79b5d7a586e8f783371.zip meson-1f5c6d62bf1e88ae24dce79b5d7a586e8f783371.tar.gz meson-1f5c6d62bf1e88ae24dce79b5d7a586e8f783371.tar.bz2 | |
More clearly explain portability issues with linking to a module
Refine #3277
According to what I read on the internet, on OSX, both MH_BUNDLE (module)
and MH_DYLIB (shared library) can be dynamically loaded using dlopen(), but
it is not possible to link against MH_BUNDLE as if they were shared
libraries.
Metion this as an issue in the documentation.
Emitting a warning, and then going on to fail during the build with
mysterious errors in symbolextractor isn't very helpful, so make attempting
this an error on OSX.
Add a test for that.
See also:
https://docstore.mik.ua/orelly/unix3/mac/ch05_03.htm
https://stackoverflow.com/questions/2339679/what-are-the-differences-between-so-and-dylib-on-osx
Diffstat (limited to 'mesonbuild/backend/ninjabackend.py')
0 files changed, 0 insertions, 0 deletions