Changes between Initial Version and Version 1 of Ticket #70127
- Timestamp:
- May 31, 2024, 11:22:57 PM (4 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #70127 – Description
initial v1 8 8 9 9 But libcurl is only called from pextlibs `curl.c` as far as I've seen, and my hack has shown that a pextlib built with quite "old" curl headers from the system works fine with a newer libcurl. 10 That should mean that pextlib ought to be able to `dlopen` libcurl from a number of supported locations (including for instance $prefix/libexec/curl`) and load the required symbols at runtime using `dlsym`. The libcurl at that special location could then be provided by a properly groomed port, probably even a subport of `port:curl`.10 That should mean that pextlib ought to be able to `dlopen` libcurl from a number of supported locations (including for instance `$prefix/libexec/curl`) and load the required symbols at runtime using `dlsym`. The libcurl at that special location could then be provided by a properly groomed port, probably even a subport of `port:curl`. 11 11 12 12 Using `dlopen` instead of using an `@rpath` style dependency is more work but should provide more resilience against the special libcurl failing to load because of a missing dependency. If however dyld will in that case just load the next libcurl in the rpath then that solution would be less work, and could even be handled in a post-install script.