[MacPorts] #25162: qt4-mac-devel fails to build, error in storage/StorageEvent.h:38
MacPorts
noreply at macports.org
Mon Jun 7 04:16:06 PDT 2010
#25162: qt4-mac-devel fails to build, error in storage/StorageEvent.h:38
---------------------------------------+------------------------------------
Reporter: macports@… | Owner: macports-tickets@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 1.9.99
Resolution: duplicate | Keywords:
Port: qt4-mac-devel |
---------------------------------------+------------------------------------
Changes (by ryandesign@…):
* status: new => closed
* resolution: => duplicate
Comment:
Replying to [comment:2 macports@…]:
> Thanks, deactivating libevent did the trick. Maybe qt4-mac should
conflict with those packages -- or at least display a helpful message
after a failed build?
qt4-mac is already marked as conflicting with libevent. The problem is
that the conflicts keyword was not designed to model build-time conflicts
like this. (It was designed to model activation-time conflicts.) MacPorts
base needs to be given a new keyword to model build-time conflicts.
So this ticket is a duplicate of #20199.
> Also, thanks for the tip about qt4-mac vs qt4-mac-devel. I though I
needed qt4-mac-devel to do QT development.
MacPorts does not follow that naming convention. In other package
managers, -dev or -devel packages contain the headers, while the regular
port contains the libraries. In MacPorts, the -devel port (if any)
contains the development version of the full software (headers and
libraries), and the regular port contains the stable version of the full
software (headers and libraries). See #14540.
--
Ticket URL: <http://trac.macports.org/ticket/25162#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list