Changes between Version 1 and Version 2 of Ticket #51516, comment 120


Ignore:
Timestamp:
Jun 2, 2024, 2:53:13 PM (4 weeks ago)
Author:
RJVB (René Bertin)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #51516, comment 120

    v1 v2  
    44> Then we might rename and copy that one library into the base installation, and use it if it and libcurl exist.
    55
    6 That could also be a solution, but rather than building all of MacPorts "base" it would be better in that case to add a standalone build system to the Pextlib component!
    7 You don't want to build against `${prefix}/lib/libcurl` though, because of the potential of openssl version clashing. Though I suppose a `port:pextlib` (that's what we're talking about here) could simply be built against the same openssl version that libcurl may be using too (if installed `+ssl`).
     6That could also be a solution, but rather than building all of MacPorts "base" it would be better in that case to add a standalone build system to the Pextlib component (and make it a git submodule of the "base" repo so it can be checked out as a standalone component too)!
     7You don't want to build against `${prefix}/lib/libcurl` though, because of the potential of openssl version clashing. Though I suppose a `port:pextlib` (that's what we're talking about here) could simply be built against the same openssl version that libcurl may be using too (if installed `+ssl`).\\
    88EDIT: for some reason even I didn't consider the possibility of a `port:pextlib` but it does seem to be the cleanest solution. It and the dedicated curl port could even be subports.
    99