[MacPorts] #69352: v8-8.3: does not install libv8.dylib

[MacPorts]

#69352: v8-8.3: does not install libv8.dylib
-------------------------+--------------------------
  Reporter:  ryandesign  |      Owner:  barracuda156
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  v8-8.3      |
-------------------------+--------------------------

Comment (by barracuda156):

 Replying to [comment:2 ryandesign]:
 > I assume this is a limitation of the "v8-cmake" fork you're using. Here
 is their issue tracking this:
 >
 > https://github.com/bnoordhuis/v8-cmake/issues/60
 >
 > I am not working on fixing that. I am merely responding to another
 user's request to add the php v8js module and am blocked by the fact that
 it looks for and does not find libv8.dylib. And it's not just that the
 v8-8.3 port doesn't install the shared library libv8.dylib; it also
 doesn't install a static library named libv8.a. It installs nine separate
 static libraries with a "libv8_" prefix but no libv8.a.
 >
 > There must exist some build of v8 (maybe the original official version?)
 that can build a single v8 shared library, otherwise the php v8js module
 would not have been programmed to require it. Can we switch to that
 version of v8 instead of "v8-cmake"?

 1. I may be completely off here, but can’t static libs be used
 interchangeably with dynamic, as long as we talk about ports and not
 something like operating system development?
 For `R-V8` I have just patched its configure to use the correct libs.
 After 2–3 rebuilds it worked fine (I had to figure out which ones it
 uses).

 2. I am not against switching to another build system in principle, though
 I would prefer not to use a horrible one that NodeJS uses. That one is
 just bad, whatever it is.
 V8, AFAIR, uses `gn`? I actually made a port for it:
 https://ports.macports.org/port/gn
 But I never used this build system, and perhaps nothing in Macports uses
 it yet. If anyone makes a portfile for V8 on `gn` build system, I will
 happily test that.

 3. Finally, there is no need to use identical build system for different
 versions of V8, as long as those are distinct ports (I mean, we do not
 want a zoo of build systems, but two different are fine). It is perhaps
 better to use a newer V8 on current macOS versions anyway. So that could
 be introduced without CMake, if that is preferable.

 I could take a look at using `gn` myself, but perhaps not very soon. If we
 have someone already familiar with it who can help here, it would be
 great.

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