Philippe BERNERY a écrit :
I then have a link error in libwebcam because of boost... I
recompiled boost from source, but it does not change anything. Does
anyone know about it?
Undefined symbols:
"boost::signals::detail::named_slot_map_iterator::equal(boost::signals::detail::named_slot_map_iterator
const&) const", referenced from:
bool
boost::iterator_core_access::equal<boost::signals::detail::named_slot_map_iterator,
boost::signals::detail::named_slot_map_iterator>(boost::signals::detail::named_slot_map_iterator
const&, boost::signals::detail::named_slot_map_iterator const&,
mpl_::bool_<true>)in WebcamDriver.o
Sorry, I have no idea about this one for now.
I still have no idea too. I continue to look for the solution...
I successfully installed Boost from MacPorts, with some little trickery
(port clean --all boost ; port install boost). The issue with MacPorts
seemed to be caused by bjam not being installed at the time MacPorts
would build Boost.
Using this version of Boost, I have been able to build WengoPhone on
Leopard, but I had to build FFMpeg with MacPorts: it would not link with
the libabutil binary from libs/3rdparty. Error message was:
ld: absolute addressing (perhaps -mdynamic-no-pic) used in _av_d2q from
/Users/agateau/src/wengophone-2.2/libs/3rdparty/ffmpeg/binary-lib/macosx/libavutil.a(rational.o)
not allowed in slidable image
I am now happy to report WengoPhone builds and run on Leopard. Latest
nightly build (PPC only for now) has been built using Leopard and Qt 4.3.2.
About the FFMpeg problem: I think the simplest solution is just to get
rid of the MacOS binaries and requires the users to build FFMpeg
themselves. What do you think about this?
Aurélien
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
