[MacPorts] #70585: py310-pyqt5-webengine upgrade broken on port version 2.10.1 on Ventura 13.6.7
MacPorts
noreply at macports.org
Fri Aug 23 00:12:25 UTC 2024
#70585: py310-pyqt5-webengine upgrade broken on port version 2.10.1 on Ventura
13.6.7
------------------------------------+------------------------
Reporter: Alex11N | Owner: reneeotten
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.10.1
Resolution: | Keywords:
Port: py310-pyqt5-webengine |
------------------------------------+------------------------
Comment (by Alex11N):
Replying to [comment:9 jmroot]:
> Could be that
`DEVELOPER_DIR='/Applications/Xcode.app/Contents/Developer'`, which is set
as a result of `use_xcode yes` in the Portfile, makes xcrun unable to
find SDKs provided by the CLTs. As I'm sure has been noted before, it
would be a lot easier if Qt just let us tell it which SDK path to use.
Is there a licencing (i.e., legal) requirement that we stick strictly to
the portfile? Who actually creates it? I would have thought that it would
have been up to the maintainer's discretion as to what went into the
portfile.
As a slightly related query, is there a useful book on the 'autotool'
complex? Most of my problems are dealing with vagaries of
configure/autoconf/make/m4, etc. I know that 'make' and relatives and m4
aren't 'autotools' as such, but given my currently lack of understanding
about how the build machinery works they almost might just as well be.
Actual pogram code is one thing - the build process is another bucket of
snakes entirely. It appears to me that the suite changes relatively
frequently so what is one year's flavour is different the next, so maybe a
book isn'tthe right thing to be asking about.
--
Ticket URL: <https://trac.macports.org/ticket/70585#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list