[MacPorts] #52862: qt4-mac +debug: non-debug QtWebkit links to debug frameworks, and QtWebkit_debug does not exist

MacPorts noreply at macports.org
Sat Nov 12 17:32:05 CET 2016


#52862: qt4-mac +debug: non-debug QtWebkit links to debug frameworks, and
QtWebkit_debug does not exist
-----------------------+--------------------------------
  Reporter:  devernay  |      Owner:  macports-tickets@…
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:
      Port:  qt4-mac   |
-----------------------+--------------------------------

Comment (by RJVB):

 If I may suggest, Qt's release + debug framework approach is nice and
 would be great if it worked reliably, but it never did in my testing. It's
 also mostly interesting for people working on Qt4, of which there are
 probably preciously few these days.

 I find that most of the time I only need usable backtraces into Qt code
 because whatever bug I'm hunting comes from dependent ("client") code 95+%
 of the time.

 That's why in my own Qt5 port I have refactored the debug variant so that
 it adds and changes a number of compiler options so that I get a true
 debug build, while my personal regular build already contains some form of
 debug information.

 This approach is more than good enough with MacPorts where you can switch
 between regular/release and +debug builds with the port de/activate
 feature. As a bonus you cut the build time in half: you install the
 regular/release build from a binary package, and only build the debug
 version (actually, >2x faster because a -O0 build is a lot faster than a
 -O2 or -O3 build).

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



More information about the macports-tickets mailing list