search

Ashwinning / libmv

Automatically exported from code.google.com/p/libmv
MIT License
0 stars 0 forks source link

Build fails running OSX 10.6 #15

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. make

What is the expected output? What do you see instead?

- Expected: cmake calling libraries and dependencies. 
- Actual:   I receive QT and gflag errors (see attached file).

What version of the product are you using? On what operating system?

- Revision 756. MacOSX 10.6 Snow Leopard.

Please provide any additional information below.

Build fails on snow leopard. I searched online. The error is QT related but
I am not sure how to resolve this issue. 

CMAKE_MODULE_PATH = /repos/libmv-read-only/src/CMakeModules
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - not found.
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found.
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found.
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - not found.
-- Found Qt-Version 4.5.3
-- Found OpenSSL: /usr/lib/libssl.dylib
-- Configuring done
-- Generating done
-- Build files have been written to: /repos/libmv-read-only/bin-dbg

Any suggestions would be appreciated. I am running OSX 10.6 and just
installed the latest QT SDK disk image "qt-sdk-mac-opensource-2009.04.dmg".
I also build and installed gflags from source and posted an issue on their
site. My make log file is attached for reference.

Thanks! 

P.S I am interested in contributing to the project and am working out the
details of a geometric min-hash algorithm to evaluate its application on
mobile phones.

Original issue reported on code.google.com by bid...@gmail.com on 21 Oct 2009 at 1:23

Attachments:

GoogleCodeExporter commented 9 years ago 
Hey, sorry about the build failure. Pau is the local mac expert; pau, do you 
have any 
suggestions?

We actually have a local copy of gflags in third_party; the other one should 
not be 
used.

Original comment by mie...@gmail.com on 24 Oct 2009 at 2:24

GoogleCodeExporter commented 9 years ago 
I was able to build it on Mac OS X 10.6 by hacking up the following...

Warnings are treated as errors so in an effort to get something to compile I 
had to
disable that by removing "-Wfatal-errors -Werror" and adding "-fpermissive"
So that the cmake file has this in it instead...

IF(CMAKE_COMPILER_IS_GNUCXX)
  SET(CMAKE_CXX_FLAGS "-Wall -W -Wno-sign-compare -Wno-strict-aliasing -fpermissive")
  ADD_DEFINITIONS(-D_GNU_SOURCE)
ENDIF(CMAKE_COMPILER_IS_GNUCXX)

in the cmake interface you need to specify arch
i386 for arch

And to avoid certain issues with functions in 10.6 you can tell it to compile
with 10.5's sdk. (for now that will get you somewhere)
So cmake settings have to have 10.5 and 
use the MacOSX10.5.sdk

Original comment by sirhcsen...@gmail.com on 21 Mar 2010 at 7:08

GoogleCodeExporter commented 9 years ago 
Hello,
Thanks for the comments.

Could you please send us the log of warning that as interpreted as errors ?

And if you can also the issues you have meet with 10.6...

Thanks a lot.

Original comment by pmou...@gmail.com on 22 Mar 2010 at 8:38

GoogleCodeExporter commented 9 years ago 
[  3%] Building CXX object 
third_party/glog/src/CMakeFiles/glog.dir/signalhandler.o
In file included from
/Users/admin/Documents/libmvWork/libmv-read-only/src/third_party/glog/src/signal
handler.cc:42:
/Developer/SDKs/MacOSX10.6.sdk/usr/include/ucontext.h:42:2: error: #error 
ucontext
routines are deprecated, and require _XOPEN_SOURCE to be defined
make[2]: *** [third_party/glog/src/CMakeFiles/glog.dir/signalhandler.o] Error 1
make[1]: *** [third_party/glog/src/CMakeFiles/glog.dir/all] Error 2
make: *** [all] Error 2

In 10.6 this file has deprecated functions and in 10.6 
#include <ucontext.h>

Original comment by sirhcsen...@gmail.com on 27 Mar 2010 at 9:40

GoogleCodeExporter commented 9 years ago 
Could you try to change #include <ucontext.h> to #include <sys/ucontext.h> and 
tell 
us if it changes something ?

Original comment by pmou...@gmail.com on 29 Mar 2010 at 12:48

GoogleCodeExporter commented 9 years ago 
Why does that work? the # include <sys/ucontext.h> worked. Now I get past it to 
an
error that looks like. 

In file included from
/Users/admin/Documents/libmvWork/libmv-read-only/src/third_party/daisy/include/d
aisy/daisy.h:46,
                 from
/Users/admin/Documents/libmvWork/libmv-read-only/src/third_party/daisy/src/daisy
.cpp:42:
/Users/admin/Documents/libmvWork/libmv-read-only/src/third_party/daisy/include/k
utility/general.h:
In function ‘void kutility::map_memory_file(std::string, long int, T*&)’:
/Users/admin/Documents/libmvWork/libmv-read-only/src/third_party/daisy/include/k
utility/general.h:752:
error: there are no arguments to ‘open64’ that depend on a template 
parameter, so a
declaration of ‘open64’ must be available
compilation terminated due to -Wfatal-errors.
make[2]: *** [third_party/daisy/CMakeFiles/daisy.dir/src/daisy.o] Error 1
make[1]: *** [third_party/daisy/CMakeFiles/daisy.dir/all] Error 2
make: *** [all] Error 2

Original comment by sirhcsen...@gmail.com on 29 Mar 2010 at 7:38

GoogleCodeExporter commented 9 years ago 
need acknowledge: is this bug still here?

Original comment by julien.michot.fr@gmail.com on 27 Apr 2011 at 5:53

GoogleCodeExporter commented 9 years ago 
I haven't gotten to recompile libmv in a long while. If no one has done son on 
OS X since then I'd imagine it's still there.  I don't know though.

Original comment by sirhcsen...@gmail.com on 27 Apr 2011 at 6:26

GoogleCodeExporter commented 9 years ago 
Actually, we have made some bugfix for this issue,
but I need to be sure that it compiles on Mac OSX before closing it.

Original comment by julien.michot.fr@gmail.com on 27 Apr 2011 at 7:24

GoogleCodeExporter commented 9 years ago 
hello every one,

i am a new here.. i saw the source code for blender and processing file .. the 
idea is soo near to what am working on ,, i wanna communicate the blender with 
the peocessing via osc .. this is the only application i found to formalize my 
idea well.. 

so please if any one send to me a full documentation about the scenario that 
must be result when applying the project ??

another question , 

i would ask if there is a specific hardware to use it as a sender to 
processing??

in my work , i wanna use the sensor gloves as a signal sender to processing 
then send these information to blender to make the action suitable to the 
recieved information via osc ? is it applicable ?

thank you?

Original comment by shaimaa....@gmail.com on 16 May 2011 at 9:28