[MacPorts] #31778: hugin-app @2011.0.0 not compiling, clang error, then "QDGetPictureBounds" not declared error with llvm-gcc-4.2
MacPorts
noreply at macports.org
Fri Jul 20 03:40:31 PDT 2012
#31778: hugin-app @2011.0.0 not compiling, clang error, then "QDGetPictureBounds"
not declared error with llvm-gcc-4.2
----------------------------------------+-----------------------------------
Reporter: philippe.bernery@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.0.3
Keywords: | Port: hugin-app
----------------------------------------+-----------------------------------
Comment(by hvdwolf@…):
The next hugin 2012.0 is to be released soon. hugin is currently built
against Carbon using wxWidgets.
The conflicting macro between boost >=1.48 and Apple inside assertMacros.h
is a piece of carbon code that is necessary for wxwidgets 2.8 carbon. It's
a conflict I can't solve.
I already skipped the entire boost patch and wrote a few patches to
compile hugin against wxwidgets 2.9 for Cocoa. These patches are in a
hugin development branch and not ready for release yet. It has the
advantage that hugin can be compiled both for i386 and x86_64. 64bits
builds weren't posible against wxmac 2.8 as carbon isn't 64bits.
When I use the wxwidgets-devel 2.9 version and use the CPP/C/CXXFLAG "-D
__ASSERT_MACROS_DEFINE_VERSIONS_WITHOUT_UNDERSCORES=0" to overcome the
boost issue, I can compile hugin and I could build a portfile for that.
Hugin against Cocoa works but needs finetuning and is not ready for
release as drag&drop and a few more things are broken in wxwidgets 2.9.3
and 2.9.4. As it is not ready for release in 2012.0, it will not come to
Macports soon either. I like to have a hugin 2012.2 release somewhere in
autumn as well to implement all this, but at this moment I'm really in a
situation I can't go forward. Which means that hugin will remain broken
for a somewhat longer period or I should apply the hugin patches to 2012.0
as well and make a portfile that forces the use of wxwidgets-devel and
deactivate wxwidgets (when installed).
Please advise in case of other solutions which I don't know now due to
missing macports knowledge.
--
Ticket URL: <https://trac.macports.org/ticket/31778#comment:13>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list