[MacPorts] #65988: libdispatch: how to make linking to libblocksruntime work?

MacPorts noreply at macports.org
Thu Oct 13 16:58:11 UTC 2022

#65988: libdispatch: how to make linking to libblocksruntime work?
  Reporter:  barracuda156  |      Owner:  kencu
      Type:  submission    |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.7.2
Resolution:                |   Keywords:
      Port:  libdispatch   |

Comment (by kencu):

 by default the cmake PortGroup sets things up to configure and build for
 Makefiles, using "make".

 ninja has no idea how to build a Makefile, and that is why you see those
 weird ninja errors. ninja does not speak "Makefile".

 to build with ninja using MacPorts cmake PortGroup, you set this:

 cmake.generator Ninja

 and then everything else is automatic. See <https://github.com/macports
 /macports-ports/blob/master/_resources/port1.0/group/cmake-1.1.tcl> for
 all the gory details about how to make the cmake 1.1 PortGroup obey your

 Regarding not finding Blocks, as you can see none of your configure
 arguments are being used during your build, and you're relying on the
 build-in Blocks-finding cmake logic in that upstream repo. I guess it is
 not working -- my first thought is because libblocksruntime doesn't exist
 on MacOS (it is in libSystem.dylib).

 You'll have more success making this work to begin with if you do it on
 MacOSX 10.5 Leopard, probably Intel, which is where I will try it

Ticket URL: <https://trac.macports.org/ticket/65988#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS

More information about the macports-tickets mailing list