This site requires JavaScript, please enable it in your browser!
Greenfoot back
dangjavageek
dangjavageek wrote ...

2012/6/9

Greenfoot Kinect / Mac OS X 10.7 Lion - libusb-devel

1
2
dangjavageek dangjavageek

2012/6/9

#
I thought I'd mention that Mac OS X 10.7 Lion and the latest mac ports generated a "please do not install this port" message as below, following the instructions on the Greenfoot / Kinect page for Mac OS X driver installation: % sudo /opt/local/bin/port install libusb-devel +universal ---> Fetching archive for libusb-devel ---> Attempting to fetch libusb-devel-1.0.8.20101017_3+universal.darwin_11.i386-x86_64.tbz2 from http://packages.macports.org/libusb-devel ---> Fetching distfiles for libusb-devel ---> Verifying checksum(s) for libusb-devel ---> Extracting libusb-devel ---> Configuring libusb-devel Error: Please do not install this port since it has been replaced by 'libusb'. Error: org.macports.configure for port libusb-devel returned: Please see the log file for port libusb-devel for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libusb-devel/libusb-devel/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port libusb-devel failed Best regards, -- DanG
vtn2@calvin.edu vtn2@calvin.edu

2012/8/30

#
Dan, I found the same thing happen to me. After getting past that, I had problems with configure: error: cannot find the flags to link with Boost thread Did you see this problem? Vic
dangjavageek dangjavageek

2012/8/31

#
Yes, I've made 3 runs at trying to get the Kinect configured with Greenfoot on Mac OS X 10.8 (i.e., have gone to Mountain LIon since the last post) and I've had no luck yet, Boost seems to be the culprit each time.
nccb nccb

2012/9/3

#
I'm aware of this problem, having recently hit the same on my Mac. It seems you now need libusb instead of libusb-devel, and for Boost I ended up having to hardcode my boost paths! As a quick solution, here's the configure.ac that I ended up using (I think the two changes involve commenting the BOOST_THREADS macro, and hardcoding the paths in LIBS and LDFLAGS at the bottom):
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
AC_INIT([kinectserver], [1.2])
AC_CANONICAL_TARGET
AM_INIT_AUTOMAKE
AC_PROG_CXX
AC_PROG_LIBTOOL
 
AC_CONFIG_SRCDIR(server.cpp)
 
AC_CHECK_HEADERS([sys/time.h],,AC_MSG_ERROR("Could not find sys/time.h"))
 
CPPFLAGS="$CPPFLAGS -I/usr/include/ni/"
AC_LANG(C++)
AC_CHECK_HEADERS([XnTypes.h XnOpenNI.h XnCppWrapper.h],,AC_MSG_ERROR("Could not find OpenNI headers"))
 
m4_include([m4/boost.m4])
 
BOOST_REQUIRE
BOOST_ASIO
BOOST_SMART_PTR
BOOST_PROGRAM_OPTIONS([mt-s])
BOOST_SYSTEM([mt-s])
#BOOST_THREADS([mt])
 
#TODO give an error if any of the boost libraries are missing
 
m4_include([m4/wxwin.m4])
AM_OPTIONS_WXCONFIG
AM_PATH_WXCONFIG([2.4.0], wxWin=1)
if test "$wxWin" != 1; then
  AC_MSG_ERROR([
        wxWidgets must be installed on your system.
  
        Please check that wx-config is in path, the directory
        where wxWidgets libraries are installed (returned by
        'wx-config --libs' or 'wx-config --static --libs' command)
        is in LD_LIBRARY_PATH or equivalent variable and
        wxWidgets version is $reqwx or above.
        ])
fi
CPPFLAGS="$CPPFLAGS $BOOST_CPPFLAGS $WX_CPPFLAGS"
CXXFLAGS="$CXXFLAGS $WX_CXXFLAGS_ONLY"
CFLAGS="$CFLAGS $WX_CFLAGS_ONLY"
BOOST_THREAD_LIBS=""
BOOST_THREAD_LDFLAGS=""
LIBS="$LIBS $WX_LIBS $BOOST_SYSTEM_LIBS /opt/local/lib/libboost_thread-mt.a $BOOST_PROGRAM_OPTIONS_LIBS"
LDFLAGS="$LDFLAGS $BOOST_SYSTEM_LDFLAGS -L/opt/local/lib $BOOST_PROGRAM_OPTIONS_LDFLAGS"
 
AC_CONFIG_FILES(Makefile)
AC_OUTPUT
What I need to do as soon as I get time is properly update the boost macros, if possible, and then do a new Kinect release with updated instructions. I've been wanting to do this for a while, but it's been a busy summer! Edit: once you've replaced this in the untarred source for kinectserver, you'll need to run "autoreconf -i" (which requires autoconf to be installed on your system: "sudo port install autoconf" and "sudo port install automake" should do it, from memory) followed by the usual "./configure" and "make".
dangjavageek dangjavageek

2012/9/7

#
awesome, thanks, nccb!
dristea dristea

2012/9/19

#
Hi. I'm using 10.7.4 on a Mac, and I'm getting the same error as above: checking for the Boost thread library... no configure: error: cannot find the flags to link with Boost thread I did change the content of configure.ac to reflect the above changes, as stated by nccb on 2012/9/3 Any ideas on what is going wrong? Thanks, D.
psybersonic psybersonic

2013/2/6

#
Hi I'm on Mountain Lion and I've followed this thread only to get an error on autoreconfig -i My year studying under David Barnes et al did not prepare me for this. Any pointers? Thanks $ autoreconf -i glibtoolize: putting auxiliary files in `.'. glibtoolize: copying file `./ltmain.sh' glibtoolize: Consider adding `AC_CONFIG_MACRO_DIR()' to configure.ac and glibtoolize: rerunning glibtoolize, to keep the correct libtool macros in-tree. glibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. configure.ac:43: error: possibly undefined macro: BOOST_THREAD_LIBS If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:44: error: possibly undefined macro: BOOST_THREAD_LDFLAGS autoreconf: /opt/local/bin/autoconf failed with exit status: 1
einf_nksa einf_nksa

2013/2/13

#
Hey nccb Thank you very much for all the work you've done for the kinect workaround! We've had a project in our class and had a lot of fun with it! We were able to develop four fun games. Unfortunately, the mac users had to fight the same problems as described in this post (with boost). We weren't able to solve these problems. We wanted to ask you, if you could bring out the new release, as you announced it. This would be great, because with this, the younger students could work on their personal computers, when we repeat this project. thanks einf_nksa
RoseTom RoseTom

2014/5/1

#
Hello nccb, I'm working on Mountain Lion OSx to integrate the kinect with my greenfoot game for a demo purpose. But I am facing the same issue as mentioned by psybersonic, when trying to run autoreconf -i. I followed the steps listed http://www.greenfoot.org/doc/kinect/macos.html. until the command ./configure --with-boost=/opt/local/include --with-wx-config=/opt/local/bin/wx-config --with-wx-prefix=/opt/local. Since I got the error with boost flags, I changed the configure.ac files as you specified. The error is: autoreconf -i glibtoolize: putting auxiliary files in `.'. glibtoolize: copying file `./ltmain.sh' glibtoolize: Consider adding `AC_CONFIG_MACRO_DIR()' to configure.ac and glibtoolize: rerunning glibtoolize, to keep the correct libtool macros in-tree. glibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. configure.ac:43: error: possibly undefined macro: BOOST_THREAD_LIBS If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:44: error: possibly undefined macro: BOOST_THREAD_LDFLAGS autoreconf: /opt/local/bin/autoconf failed with exit status: 1 Any thoughts? Thanks.
dangjavageek dangjavageek

2014/5/20

#
I tried this on mac os x 10.9.2 and same results - I will look into other places documenting how to get around the boost thread library issue
nccb nccb

2014/5/23

#
Hi, Could anyone with this problem try: http://www.cs.kent.ac.uk/people/staff/nccb/kinectserver-1.2m2.tar.gz and see if it works better for them on Mac? If it does I'll replace the download on the site with it.
jskipper jskipper

2014/6/5

#
So i tried your new server and certainly got farther... but alas I have ende here: ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** Error 1 thoughts?
nccb nccb

2014/6/6

#
jskipper -- I would need to see the lines above that one, to know what symbols the "ld" tool has failed to find.
jskipper jskipper

2014/6/8

#
here is the full output of the make command: https://drive.google.com/file/d/0B3Tzauf-Y3HNNG1VdE1GbE40UXM/edit?usp=sharing thank you :)
dangjavageek dangjavageek

2014/12/3

#
Thanks for the updated kinectserver build, nccb! Tried this on Mac OS X 10.10... at this point it's probably worth updating my path here: Mac OS X 10.10.1 XCode 6.1.1 macports 2.3.3 sudo /opt/local/bin/port -v selfupdate RESULT: MacPorts base version 2.3.3 installed ---> MacPorts base is already the latest version sudo /opt/local/bin/port install libtool RESULT: clean install sudo /opt/local/bin/port install libusb +universal RESULT: clean install sudo /opt/local/bin/port install boost RESULT: clean install sudo /opt/local/bin/port install wxWidgets-2.8 RESULT: Error: wxWidgets-2.8 cannot be built on Moc OS X >= 10.7 with Xcode >= 4.4, please use port wxWidgets-3.0 or wxgtk-2.8 instead sudo /opt/local/bin/port install wxWidgets-3.0 RESULT: clean install OpenNI from greenfoot kinect download page RESULT: clean install Kinect Driver from greenfoot kinect download page RESULT: clean install NITE from greenfoot kinect download page RESULT: clean install test OpenNI SimpleViewer RESULT: works with -Djava.library.path=/usr/lib kinectserver-1.2m2 -> ./configure --with-boost=/opt/local/include --with-wx-config=/opt/local/bin/wx-config --with-wx-prefix=/opt/local RESULT: checking for /opt/local/bin/wx-config... no configure: error: wxWidgets must be installed on your system. Please check that wx-config is in path, the directory where wxWidgets libraries are installed (returned by 'wx-config --libs' or 'wx-config --static --libs' command) is in LD_LIBRARY_PATH or equivalent variable and wxWidgets version is or above.
There are more replies on the next page.
1
2