[MacPorts] #49711: [cpp-netlib][0.11.2][new port]

MacPorts noreply at macports.org
Mon Dec 14 06:58:08 PST 2015


#49711: [cpp-netlib][0.11.2][new port]
-------------------------+--------------------------------
  Reporter:  nikkoara@…  |      Owner:  macports-tickets@…
      Type:  submission  |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  cpp-netlib  |
-------------------------+--------------------------------

Comment (by nikkoara@…):

 Replying to [comment:9 raimue@…]:
 > Replying to [comment:8 nikkoara@…]:
 > > The CMake infrastructure of the cpp-netlib project builds either
 shared libraries or static libraries. It does not contain provisions to
 build both. The selection hinges entirely on the CMake macro
 BUILD_SHARED_LIBS: if on, it builds shared libs, etc. If this is
 considered to be a limitation from the Macports framework pov there is
 little I can do about it.
 >
 > If this port builds either static or shared libraries, it does not make
 sense to provide two variants. This would only be one choice, which could
 be addressed with a single `+static` variant. Although in this case, I do
 not see any reason to provide static libraries at all. I would just
 default to shared libraries and leave out the static libraries completely.

 I see what you are saying. Use only one variant (has to be +shared) and in
 its absence, build the other/default kind of libraries. Because cpp-netlib
 CMake scripts default to building static libraries, the variant would be
 +shared: when present, build shared libs, when absent (or explicit
 "-shared"?) build default/static.

 >
 > > > Compilation failed on my system. I am no CMake expert and have no
 idea where to look further for this. I did not see any mention of the
 problem in `CMakeOutput.log`, but if required I could provide it.
 > >
 > > Could you please attach that and your invocation of ports? I would
 like to take a look at it.
 >
 > I attached both `CMakeOutput.log` and `main.log`. I do not know what
 other parameters could be different on my system if it worked for you.

 You attempted to install the the port with the default variant, i.e.,
 static, but your boost installation only installed the shared Boost
 libraries. See in main.log, about line 120. The failure occurs during
 configuration but I don't remember having done this for me during the
 testing of the port. I expect this kind of errors to be loud and early,
 right after invocation, because of the +static variant and the check for
 Boost statics that is inside it. Is that check not performed unless the
 user puts +static explicitly on the command line?

-- 
Ticket URL: <https://trac.macports.org/ticket/49711#comment:10>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list