Changes between Initial Version and Version 1 of Ticket #51516, comment 113
- Timestamp:
- Jun 2, 2024, 12:48:28 PM (6 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #51516, comment 113
initial v1 1 1 Come to think of it ... before my current hack I used a `DYLD_LIBRARY_PATH` and/or `DYLD_INSERT_LIBRARIES` (and their Linux equivalents) to overload the system libcurl with the one from MacPorts. That was tricky because of how MacPorts controls the environment and because of the side-effects `DYLD_LIBRARY_PATH` can have. 2 2 3 I *think* a rewrite of `curl.c` can be avoided if we can simply try to `dlopen` an appropriate (tested etc) libcurl from the `port` driver command before it loads the Pextlib extension. It looks like this would require either a glue library that provides at least a stub Tcl package loader function (`Curl_Init()` ) or else adding a Tcl extension (https://wiki.tcl-lang.org/page/dlopen+extension).3 I *think* a rewrite of `curl.c` can be avoided if we can simply try to `dlopen` an appropriate (tested etc) libcurl from the `port` driver command before it loads the Pextlib extension. It looks like this would require either a glue library that provides at least a stub Tcl package loader function (`Curl_Init()`, so that Tcl's `load` can be used) or else adding a Tcl extension (https://wiki.tcl-lang.org/page/dlopen+extension). A glue library seems a little more appropriate.