Opened 11 years ago
Last modified 10 years ago
#42840 closed defect
cmake issues -bundle instead of -dynamiclib when creating shared modules — at Version 2
Reported by: | RJVB (René Bertin) | Owned by: | css@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.1 |
Keywords: | Cc: | egall@… | |
Port: | cmake |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
This is a follow-up to issue #40188. I was bitten by the cmake specificity while building KDE's Calligra suite, when the linker refused to link in 'bundle' shared objects (intended to act as plugins also) in x86_64 mode. Googling, I came across
http://www.wireshark.org/lists/wireshark-dev/201009/msg00231.html where one reads
"CMake is using -bundle rather than -dylib/-dynamiclib to build the asn1 plugin, probably so that it'll work even on versions of OS X where you can't dynamically load an MH_DYLIB."
AFAIK, that's a moot point since OS X 10.3 (or at least 10.4). I cannot decide whether a modification of the corresponding cmake formulas is something MacPorts can do during an installation, but it is possible. Finding all CMAKE_SHARED_MODULE_CREATE definitions in /opt/local/lib/cmake{,-2.8} and replacing -bundle with -dynamiclib resolves the linking problem I encountered.
Change History (2)
comment:1 Changed 11 years ago by cooljeanius (Eric Gallager)
Cc: | egall@… added |
---|
comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Keywords: | CMAKE_SHARED_MODULE_CREATE removed |
Owner: | changed from macports-tickets@… to css@… |
Is there an upstream bug report for this problem?
Cc Me!