[MacPorts] #51737: New port libpointing

[MacPorts]

#51737: New port libpointing
--------------------------+--------------------------
  Reporter:  izzatbek@…   |      Owner:  ryandesign@…
      Type:  submission   |     Status:  assigned
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:  libpointing  |
--------------------------+--------------------------

Comment (by ryandesign@…):

 I've spent a little time looking at this now.

 The source code in GitHub indeed uses QMake as a configuration system. I
 can download that code and run `qmake && make` and it looks like a bunch
 of object files get compiled but no Mac library, and `make install` does
 nothing.

 But then you have building-and-packaging/mac/prepare which is a Python
 script that creates a whole different source distribution file for macOS
 including a new dynamically-generated Makefile which hardcodes the
 compiler as `g++`; overwrites `CPPFLAGS`, `CXXFLAGS` and `LDFLAGS` so I
 can't specify them at the command line; doesn't set the library's
 `install_name` or `compatibility_version` or `current_version` when
 compiling it; and has an `install` target that doesn't support `DESTDIR`
 and uses the deprecated `-r` flag of the `cp` command. This distribution
 file is what you have uploaded to GitHub Releases as libpointing-
 mac-1.0.1.tar.gz and are using in the Portfile you submitted here.

 Why have you made it so confusing and convoluted? Why does macOS need a
 separate distribution file and build system? Why not simply let me
 download the source code from your repository and run `./configure && make
 && sudo make install` which so many other projects successfully use?

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