PCL on Mac OS X Mountain Lion

classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|

PCL on Mac OS X Mountain Lion

Kustaa Nyholm
Hi,

having had a frustrating two days trying to install PCL on my
own I decided to seek for help...

I tried the binaries from here:

http://www.pointclouds.org/downloads/

but they did not work, I've already forgotten what's the issue,
might have been that I was unable to install VTK...
IIRC I could get it to compile by installing a bunch of
stuff via MacPorts but then a simple
C program with just main() with out calling anything
in PCL fails to load because it cannot find VTK...
which is kind...ermh annoying as I have no need for
VTK...to me it seems that strictly 'point cloud only'
library without dependencies on libusb, OpenNI
and VTK would make sense, I could do without boost too,
though eigen seem like a good idea...but I digress.

Anyway, I'm a homebrew user so eventually I just
delete everything related to macports and PCL
and started from scratch with these instructions:

http://www.pointclouds.org/documentation/tutorials/installing_homebrew.php

This went rather well once I discovered the
'brew tap homebrew/science' to get the dependencies
to install as per instructions, which might be a
handy tip for people like me who
are not so up to speed with all things homebrew.

However at the end this failed because the tar file
the brew expects for PCL has move. Little bit of googling
enabled me to find the 1.6.0 tar file and hacking
the pcl.rb file allowed the download to succeed and
compile begun. BTW is there an up to date .rb file
somewhere?

In the end that compilation failed at 8% mark with
mysterious error

make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
make: *** [all] Error 2


Manually compiling PCL revealed that this related to
some or other 'at' symbol not being found which after
a little googling seems to be a problem with Apple clang.

I was not prepared to go back to gcc (supposing it
was available for Mountain Lion and latest X-code)
and after googling that the issue was supposed to
be fixed about a year ago I tried to compile from
the trunk with:

brew install pcl --HEAD

this goes quite a long way but eventually fails
with the mysterious Error 2:

dyld: DYLD_ environment variables being ignored because main executable
(/usr/bin/sudo) is setuid or setgid
==> Checking out http://svn.pointclouds.org/pcl/trunk
==> mkdir build
==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
==> make install
[ 98%] Built target test_registration
Linking CXX shared library ../lib/libpcl_recognition.dylib
brew: superenv removed: -Wno-invalid-offsetof
[ 98%] Built target pcl_recognition
make: *** [all] Error 2



At this point I decided to seek some help, especially
as I saw a couple notes that claimed that this
install from source without a hitch on Mountain Lion.

So is there an up to date instruction for doing this somewhere
or can someone please give me hand to make this happen?

br Kusti




This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

Radu B. Rusu
Administrator
http://www.pcl-users.org/Successful-PCL-Build-from-Source-on-Mac-OS-X-including-Kinfu-td4022018.html


Cheers,
Radu.
--
http://openperception.org

On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:

> Hi,
>
> having had a frustrating two days trying to install PCL on my
> own I decided to seek for help...
>
> I tried the binaries from here:
>
> http://www.pointclouds.org/downloads/
>
> but they did not work, I've already forgotten what's the issue,
> might have been that I was unable to install VTK...
> IIRC I could get it to compile by installing a bunch of
> stuff via MacPorts but then a simple
> C program with just main() with out calling anything
> in PCL fails to load because it cannot find VTK...
> which is kind...ermh annoying as I have no need for
> VTK...to me it seems that strictly 'point cloud only'
> library without dependencies on libusb, OpenNI
> and VTK would make sense, I could do without boost too,
> though eigen seem like a good idea...but I digress.
>
> Anyway, I'm a homebrew user so eventually I just
> delete everything related to macports and PCL
> and started from scratch with these instructions:
>
> http://www.pointclouds.org/documentation/tutorials/installing_homebrew.php
>
> This went rather well once I discovered the
> 'brew tap homebrew/science' to get the dependencies
> to install as per instructions, which might be a
> handy tip for people like me who
> are not so up to speed with all things homebrew.
>
> However at the end this failed because the tar file
> the brew expects for PCL has move. Little bit of googling
> enabled me to find the 1.6.0 tar file and hacking
> the pcl.rb file allowed the download to succeed and
> compile begun. BTW is there an up to date .rb file
> somewhere?
>
> In the end that compilation failed at 8% mark with
> mysterious error
>
> make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
> make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
> make: *** [all] Error 2
>
>
> Manually compiling PCL revealed that this related to
> some or other 'at' symbol not being found which after
> a little googling seems to be a problem with Apple clang.
>
> I was not prepared to go back to gcc (supposing it
> was available for Mountain Lion and latest X-code)
> and after googling that the issue was supposed to
> be fixed about a year ago I tried to compile from
> the trunk with:
>
> brew install pcl --HEAD
>
> this goes quite a long way but eventually fails
> with the mysterious Error 2:
>
> dyld: DYLD_ environment variables being ignored because main executable
> (/usr/bin/sudo) is setuid or setgid
> ==> Checking out http://svn.pointclouds.org/pcl/trunk
> ==> mkdir build
> ==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
> -DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
> ==> make install
> [ 98%] Built target test_registration
> Linking CXX shared library ../lib/libpcl_recognition.dylib
> brew: superenv removed: -Wno-invalid-offsetof
> [ 98%] Built target pcl_recognition
> make: *** [all] Error 2
>
>
>
> At this point I decided to seek some help, especially
> as I saw a couple notes that claimed that this
> install from source without a hitch on Mountain Lion.
>
> So is there an up to date instruction for doing this somewhere
> or can someone please give me hand to make this happen?
>
> br Kusti
>
>
>
>
> This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
> _______________________________________________
> [hidden email] / http://pointclouds.org
> http://pointclouds.org/mailman/listinfo/pcl-users
>
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

Kustaa Nyholm
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

>http://www.pcl-users.org/Successful-PCL-Build-from-Source-on-Mac-OS-X-incl
>uding-Kinfu-td4022018.html
>
>
>Cheers,
>Radu.
>--
>http://openperception.org
>
>On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
>>Hi,
>>
>>having had a frustrating two days trying to install PCL on my
>>own I decided to seek for help...
>>
>>I tried the binaries from here:
>>
>>http://www.pointclouds.org/downloads/
>>
>>but they did not work, I've already forgotten what's the issue,
>>might have been that I was unable to install VTK...
>>IIRC I could get it to compile by installing a bunch of
>>stuff via MacPorts but then a simple
>>C program with just main() with out calling anything
>>in PCL fails to load because it cannot find VTK...
>>which is kind...ermh annoying as I have no need for
>>VTK...to me it seems that strictly 'point cloud only'
>>library without dependencies on libusb, OpenNI
>>and VTK would make sense, I could do without boost too,
>>though eigen seem like a good idea...but I digress.
>>
>>Anyway, I'm a homebrew user so eventually I just
>>delete everything related to macports and PCL
>>and started from scratch with these instructions:
>>
>>http://www.pointclouds.org/documentation/tutorials/installing_homebrew.ph
>>p
>>
>>This went rather well once I discovered the
>>'brew tap homebrew/science' to get the dependencies
>>to install as per instructions, which might be a
>>handy tip for people like me who
>>are not so up to speed with all things homebrew.
>>
>>However at the end this failed because the tar file
>>the brew expects for PCL has move. Little bit of googling
>>enabled me to find the 1.6.0 tar file and hacking
>>the pcl.rb file allowed the download to succeed and
>>compile begun. BTW is there an up to date .rb file
>>somewhere?
>>
>>In the end that compilation failed at 8% mark with
>>mysterious error
>>
>>make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
>>make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
>>make: *** [all] Error 2
>>
>>
>>Manually compiling PCL revealed that this related to
>>some or other 'at' symbol not being found which after
>>a little googling seems to be a problem with Apple clang.
>>
>>I was not prepared to go back to gcc (supposing it
>>was available for Mountain Lion and latest X-code)
>>and after googling that the issue was supposed to
>>be fixed about a year ago I tried to compile from
>>the trunk with:
>>
>>brew install pcl --HEAD
>>
>>this goes quite a long way but eventually fails
>>with the mysterious Error 2:
>>
>>dyld: DYLD_ environment variables being ignored because main executable
>>(/usr/bin/sudo) is setuid or setgid
>>==> Checking out http://svn.pointclouds.org/pcl/trunk
>>==> mkdir build
>>==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
>>-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
>>==> make install
>>[ 98%] Built target test_registration
>>Linking CXX shared library ../lib/libpcl_recognition.dylib
>>brew: superenv removed: -Wno-invalid-offsetof
>>[ 98%] Built target pcl_recognition
>>make: *** [all] Error 2
>>
>>
>>
>>At this point I decided to seek some help, especially
>>as I saw a couple notes that claimed that this
>>install from source without a hitch on Mountain Lion.
>>
>>So is there an up to date instruction for doing this somewhere
>>or can someone please give me hand to make this happen?
>>
>>br Kusti
>>
>>
>>
>>
>>This e-mail may contain confidential or privileged information. If you
>>are not the intended recipient (or have received this e-mail in error)
>>please notify the sender immediately and destroy this e-mail. Any
>>unauthorized copying, disclosure or distribution of the material in this
>>e-mail is strictly forbidden. We will not be liable for direct,
>>indirect, special or consequential damages arising from alteration of
>>the contents of this message by a third party or as a result of any
>>virus being passed on or as of transmission of this e-mail in general.
>>_______________________________________________
>>[hidden email] / http://pointclouds.org
>>http://pointclouds.org/mailman/listinfo/pcl-users
>>
>


--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 (direct)
Fax: +358 20 7795 676
GSM: +358 40 580 5193
e-mail: [hidden email]







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

aichim
Administrator
Hi Kustaa,

I am sad to hear about your bad experiences with PCL on MacOS. I personally use MacPorts and never had problems getting PCL to run quickly on fresh Macs.
Also, if you don't give us the exact errors you encountered, but just long rants (I guarantee that nobody spent time to read your long emails entirely :) ) - there is no way for us to fix the problems and provide the users with better support.

Cheers and good luck with your project!
Alex




On Thu, Jun 13, 2013 at 11:37 AM, Kustaa Nyholm <[hidden email]> wrote:
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

>http://www.pcl-users.org/Successful-PCL-Build-from-Source-on-Mac-OS-X-incl
>uding-Kinfu-td4022018.html
>
>
>Cheers,
>Radu.
>--
>http://openperception.org
>
>On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
>>Hi,
>>
>>having had a frustrating two days trying to install PCL on my
>>own I decided to seek for help...
>>
>>I tried the binaries from here:
>>
>>http://www.pointclouds.org/downloads/
>>
>>but they did not work, I've already forgotten what's the issue,
>>might have been that I was unable to install VTK...
>>IIRC I could get it to compile by installing a bunch of
>>stuff via MacPorts but then a simple
>>C program with just main() with out calling anything
>>in PCL fails to load because it cannot find VTK...
>>which is kind...ermh annoying as I have no need for
>>VTK...to me it seems that strictly 'point cloud only'
>>library without dependencies on libusb, OpenNI
>>and VTK would make sense, I could do without boost too,
>>though eigen seem like a good idea...but I digress.
>>
>>Anyway, I'm a homebrew user so eventually I just
>>delete everything related to macports and PCL
>>and started from scratch with these instructions:
>>
>>http://www.pointclouds.org/documentation/tutorials/installing_homebrew.ph
>>p
>>
>>This went rather well once I discovered the
>>'brew tap homebrew/science' to get the dependencies
>>to install as per instructions, which might be a
>>handy tip for people like me who
>>are not so up to speed with all things homebrew.
>>
>>However at the end this failed because the tar file
>>the brew expects for PCL has move. Little bit of googling
>>enabled me to find the 1.6.0 tar file and hacking
>>the pcl.rb file allowed the download to succeed and
>>compile begun. BTW is there an up to date .rb file
>>somewhere?
>>
>>In the end that compilation failed at 8% mark with
>>mysterious error
>>
>>make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
>>make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
>>make: *** [all] Error 2
>>
>>
>>Manually compiling PCL revealed that this related to
>>some or other 'at' symbol not being found which after
>>a little googling seems to be a problem with Apple clang.
>>
>>I was not prepared to go back to gcc (supposing it
>>was available for Mountain Lion and latest X-code)
>>and after googling that the issue was supposed to
>>be fixed about a year ago I tried to compile from
>>the trunk with:
>>
>>brew install pcl --HEAD
>>
>>this goes quite a long way but eventually fails
>>with the mysterious Error 2:
>>
>>dyld: DYLD_ environment variables being ignored because main executable
>>(/usr/bin/sudo) is setuid or setgid
>>==> Checking out http://svn.pointclouds.org/pcl/trunk
>>==> mkdir build
>>==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
>>-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
>>==> make install
>>[ 98%] Built target test_registration
>>Linking CXX shared library ../lib/libpcl_recognition.dylib
>>brew: superenv removed: -Wno-invalid-offsetof
>>[ 98%] Built target pcl_recognition
>>make: *** [all] Error 2
>>
>>
>>
>>At this point I decided to seek some help, especially
>>as I saw a couple notes that claimed that this
>>install from source without a hitch on Mountain Lion.
>>
>>So is there an up to date instruction for doing this somewhere
>>or can someone please give me hand to make this happen?
>>
>>br Kusti
>>
>>
>>
>>
>>This e-mail may contain confidential or privileged information. If you
>>are not the intended recipient (or have received this e-mail in error)
>>please notify the sender immediately and destroy this e-mail. Any
>>unauthorized copying, disclosure or distribution of the material in this
>>e-mail is strictly forbidden. We will not be liable for direct,
>>indirect, special or consequential damages arising from alteration of
>>the contents of this message by a third party or as a result of any
>>virus being passed on or as of transmission of this e-mail in general.
>>_______________________________________________
>>[hidden email] / http://pointclouds.org
>>http://pointclouds.org/mailman/listinfo/pcl-users
>>
>


--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: <a href="tel:%2B358%2020%207795%20572" value="+358207795572">+358 20 7795 572 (direct)
Fax: <a href="tel:%2B358%2020%207795%20676" value="+358207795676">+358 20 7795 676
GSM: <a href="tel:%2B358%2040%20580%205193" value="+358405805193">+358 40 580 5193
e-mail: [hidden email]







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

aichim
Administrator
Hi,


General feedback is not necessarily something we are missing here :-), contributions are much more welcome!

Did you try compiling the trunk code from GitHub? And manually installing the dependencies from Macports or Brew?

Alex.


On Thu, Jun 13, 2013 at 2:32 PM, Kustaa Nyholm <[hidden email]> wrote:
Hi Alex,

thanks for answering. Too bad if no-one read my email through.

Briefly then , my problem for which I needed help and for which I actually
gave the verbatim error was that installing with homebrew
every dependency installs except pcl itself.

Running:

brew -v install pcl -HEAD

Ends with:

Building CXX object io/tools/ply/CMakeFiles/pcl_ply2obj.dir/ply2obj.cpp.o
/tmp/pcl-1azZ/PCL-1.6.0-Source/io/tools/ply/ply2obj.cpp:308:17: error: no template named 'at' in namespace 'pcl::io::ply'; did you mean 'boost::mpl::at'?
/tmp/pcl-1azZ/PCL-1.6.0-Source/io/tools/ply/ply2ply.cpp:359:17: error: no template named 'at' in namespace 'pcl::io::ply'; did you mean 'boost::mpl::at'?
  pcl::io::ply::at<pcl::io::ply::int8>(scalar_property_definition_callbacks) =...  pcl::io::ply::at<pcl::io::ply::float32> (scalar_property_definition_callbacks) = boost::bind...
  ~~~~~~~~~~~~~~^~
                boost::mpl::at

  ~~~~~~~~~~~~~~^~
                boost::mpl::at
/usr/local/include/boost/mpl/at_fwd.hpp:20:50: note: 'boost::mpl::at' declared here
template< typename Sequence, typename N > struct at;
                                                 ^
/usr/local/include/boost/mpl/at_fwd.hpp:20:50: note: 'boost::mpl::at' declared here
template< typename Sequence, typename N > struct at;
                                                 ^
/tmp/pcl-1azZ/PCL-1.6.0-Source/io/tools/ply/ply2ply.cpp/tmp/pcl-1azZ/PCL-1.6.0-Source/io/tools/ply/ply2obj.cpp::359308::1717::  error: error: ttoooo  ffeeww  tteemmppllaattee  aarrgguummeennttss  ffoorr  ccllaassss  tteemmppllaattee  ''aatt''

  pcl::io::ply::at<pcl::io::ply::int8>(scalar_property_definition_callbacks) =...  pcl::io::ply::at<pcl::io::ply::float32> (scalar_property_definition_callbacks) = boost::bind...

                ^                ^
(Of course there is more but this is the first error)

So if you can help me with that, then that is great.

Here is some info from my system:

MacBook Pro Retina 10.8.3

XCode 4.6.2

cc -v
Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn)
Target: x86_64-apple-darwin12.3.0
Thread model: posix

gcc -v
Using built-in specs.
Target: i686-apple-darwin11
Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2336.11~182/src/configure --disable-checking --enable-werror --prefix=/Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2336.11~182/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)

brew list --versions
atk 2.8.0
binutils 2.23.2
boost 1.53.0
cairo 1.12.14
cgal 4.2
cloog 0.18.0
cmake 2.8.10.2 2.8.11.1
cminpack 1.3.0
dhex 0.68
eigen 3.1.3
flann 1.8.4
fontconfig 2.10.92
freetype 2.4.11
gcc48 4.8.0
gdk-pixbuf 2.28.1
gettext 0.18.2
gfortran 4.8.0
glew 1.9.0
glfw 2.7.8
glib 2.36.2
gmp 5.1.1
gsl 1.15
gtk+ 2.24.18
gts 0.7.6
harfbuzz 0.9.16
hdf5 1.8.11
icu4c 51.1
imagemagick 6.8.0-10
isl 0.11.1 0.11.2
jpeg 8d
libffi 3.0.13
libmpc 1.0.1
libpng 1.5.14
libtiff 4.0.3
libtool 2.4.2
libusb 1.0.9
mpfr 3.1.1-p2 3.1.2
node 0.10.7
pango 1.34.1
pixman 0.30.0
pkg-config 0.28
qhull 2012.1
szip 2.1
vtk 5.10.1
xz 5.0.4










As to the 'rant 'part I was trying to
give some general feedback in a friendly and narrative manner
as I thought it would more palatable and easier to digest that
way. 

I was wrong.

That was sort of general feedback I was hoping to give, not
expecting anyone to respond to it or act on it, just wanted
to share because most projects say they want feedback...

I thought that by given examples of my difficulties would
illustrate the issue better than just a brief statement 
that 'I think this is wrong/bad'.

Sorry I failed.

br Kusti






From: Alexandru-Eugen Ichim <[hidden email]>
Reply-To: "Point Cloud Library (PCL) users" <[hidden email]>
Date: Thu, 13 Jun 2013 15:02:19 +0300
To: "Point Cloud Library (PCL) users" <[hidden email]>
Subject: Re: [PCL-users] PCL on Mac OS X Mountain Lion

Hi Kustaa,

I am sad to hear about your bad experiences with PCL on MacOS. I personally use MacPorts and never had problems getting PCL to run quickly on fresh Macs.
Also, if you don't give us the exact errors you encountered, but just long rants (I guarantee that nobody spent time to read your long emails entirely :) ) - there is no way for us to fix the problems and provide the users with better support.

Cheers and good luck with your project!
Alex




On Thu, Jun 13, 2013 at 11:37 AM, Kustaa Nyholm <[hidden email]> wrote:
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

>http://www.pcl-users.org/Successful-PCL-Build-from-Source-on-Mac-OS-X-incl
>uding-Kinfu-td4022018.html
>
>
>Cheers,
>Radu.
>--
>http://openperception.org
>
>On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
>>Hi,
>>
>>having had a frustrating two days trying to install PCL on my
>>own I decided to seek for help...
>>
>>I tried the binaries from here:
>>
>>http://www.pointclouds.org/downloads/
>>
>>but they did not work, I've already forgotten what's the issue,
>>might have been that I was unable to install VTK...
>>IIRC I could get it to compile by installing a bunch of
>>stuff via MacPorts but then a simple
>>C program with just main() with out calling anything
>>in PCL fails to load because it cannot find VTK...
>>which is kind...ermh annoying as I have no need for
>>VTK...to me it seems that strictly 'point cloud only'
>>library without dependencies on libusb, OpenNI
>>and VTK would make sense, I could do without boost too,
>>though eigen seem like a good idea...but I digress.
>>
>>Anyway, I'm a homebrew user so eventually I just
>>delete everything related to macports and PCL
>>and started from scratch with these instructions:
>>
>>http://www.pointclouds.org/documentation/tutorials/installing_homebrew.ph
>>p
>>
>>This went rather well once I discovered the
>>'brew tap homebrew/science' to get the dependencies
>>to install as per instructions, which might be a
>>handy tip for people like me who
>>are not so up to speed with all things homebrew.
>>
>>However at the end this failed because the tar file
>>the brew expects for PCL has move. Little bit of googling
>>enabled me to find the 1.6.0 tar file and hacking
>>the pcl.rb file allowed the download to succeed and
>>compile begun. BTW is there an up to date .rb file
>>somewhere?
>>
>>In the end that compilation failed at 8% mark with
>>mysterious error
>>
>>make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
>>make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
>>make: *** [all] Error 2
>>
>>
>>Manually compiling PCL revealed that this related to
>>some or other 'at' symbol not being found which after
>>a little googling seems to be a problem with Apple clang.
>>
>>I was not prepared to go back to gcc (supposing it
>>was available for Mountain Lion and latest X-code)
>>and after googling that the issue was supposed to
>>be fixed about a year ago I tried to compile from
>>the trunk with:
>>
>>brew install pcl --HEAD
>>
>>this goes quite a long way but eventually fails
>>with the mysterious Error 2:
>>
>>dyld: DYLD_ environment variables being ignored because main executable
>>(/usr/bin/sudo) is setuid or setgid
>>==> Checking out http://svn.pointclouds.org/pcl/trunk
>>==> mkdir build
>>==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
>>-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
>>==> make install
>>[ 98%] Built target test_registration
>>Linking CXX shared library ../lib/libpcl_recognition.dylib
>>brew: superenv removed: -Wno-invalid-offsetof
>>[ 98%] Built target pcl_recognition
>>make: *** [all] Error 2
>>
>>
>>
>>At this point I decided to seek some help, especially
>>as I saw a couple notes that claimed that this
>>install from source without a hitch on Mountain Lion.
>>
>>So is there an up to date instruction for doing this somewhere
>>or can someone please give me hand to make this happen?
>>
>>br Kusti
>>
>>
>>
>>
>>This e-mail may contain confidential or privileged information. If you
>>are not the intended recipient (or have received this e-mail in error)
>>please notify the sender immediately and destroy this e-mail. Any
>>unauthorized copying, disclosure or distribution of the material in this
>>e-mail is strictly forbidden. We will not be liable for direct,
>>indirect, special or consequential damages arising from alteration of
>>the contents of this message by a third party or as a result of any
>>virus being passed on or as of transmission of this e-mail in general.
>>_______________________________________________
>>[hidden email] / http://pointclouds.org
>>http://pointclouds.org/mailman/listinfo/pcl-users
>>
>


--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: <a href="tel:%2B358%2020%207795%20572" value="+358207795572" target="_blank">+358 20 7795 572 (direct)
Fax: <a href="tel:%2B358%2020%207795%20676" value="+358207795676" target="_blank">+358 20 7795 676
GSM: <a href="tel:%2B358%2040%20580%205193" value="+358405805193" target="_blank">+358 40 580 5193
e-mail: [hidden email]







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users



_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

Kustaa Nyholm
Hi,

I still seem to write too long as I'm not getting through
and  I thought my mail answered these questions :)

Anyway:

I compiled with:

   brew -v install pcl -HEAD

and I thought that compiles the trunk, at least it downloads stuff like:

   Downloading http://sourceforge.net/projects/pointclouds/files/1.6.0/PCL-1.6.0-Source.tar.bz2

is that stale since that is from sourceforge but you talk about github?

Is there a fresh brew formula for github somewhere?

And yes, like I said, every dependency install nicely from brew
(only flan formula needed some patching IIRC).

br Kusti




Hi,


General feedback is not necessarily something we are missing here :-), contributions are much more welcome!

Did you try compiling the trunk code from GitHub? And manually installing the dependencies from Macports or Brew?

Alex.


On Thu, Jun 13, 2013 at 2:32 PM, Kustaa Nyholm <[hidden email]> wrote:
Hi Alex,

thanks for answering. Too bad if no-one read my email through.

Briefly then , my problem for which I needed help and for which I actually
gave the verbatim error was that installing with homebrew
every dependency installs except pcl itself.

Running:

brew -v install pcl -HEAD

Ends with:

Building CXX object io/tools/ply/CMakeFiles/pcl_ply2obj.dir/ply2obj.cpp.o
/tmp/pcl-1azZ/PCL-1.6.0-Source/io/tools/ply/ply2obj.cpp:308:17: error: no template named 'at' in namespace 'pcl::io::ply'; did you mean 'boost::mpl::at'?
/tmp/pcl-1azZ/PCL-1.6.0-Source/io/tools/ply/ply2ply.cpp:359:17: error: no template named 'at' in namespace 'pcl::io::ply'; did you mean 'boost::mpl::at'?
  pcl::io::ply::at<pcl::io::ply::int8>(scalar_property_definition_callbacks) =...  pcl::io::ply::at<pcl::io::ply::float32> (scalar_property_definition_callbacks) = boost::bind...
  ~~~~~~~~~~~~~~^~
                boost::mpl::at

  ~~~~~~~~~~~~~~^~
                boost::mpl::at
/usr/local/include/boost/mpl/at_fwd.hpp:20:50: note: 'boost::mpl::at' declared here
template< typename Sequence, typename N > struct at;
                                                 ^
/usr/local/include/boost/mpl/at_fwd.hpp:20:50: note: 'boost::mpl::at' declared here
template< typename Sequence, typename N > struct at;
                                                 ^
/tmp/pcl-1azZ/PCL-1.6.0-Source/io/tools/ply/ply2ply.cpp/tmp/pcl-1azZ/PCL-1.6.0-Source/io/tools/ply/ply2obj.cpp::359308::1717::  error: error: ttoooo  ffeeww  tteemmppllaattee  aarrgguummeennttss  ffoorr  ccllaassss  tteemmppllaattee  ''aatt''

  pcl::io::ply::at<pcl::io::ply::int8>(scalar_property_definition_callbacks) =...  pcl::io::ply::at<pcl::io::ply::float32> (scalar_property_definition_callbacks) = boost::bind...

                ^                ^
(Of course there is more but this is the first error)

So if you can help me with that, then that is great.

Here is some info from my system:

MacBook Pro Retina 10.8.3

XCode 4.6.2

cc -v
Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn)
Target: x86_64-apple-darwin12.3.0
Thread model: posix

gcc -v
Using built-in specs.
Target: i686-apple-darwin11
Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2336.11~182/src/configure --disable-checking --enable-werror --prefix=/Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2336.11~182/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)

brew list --versions
atk 2.8.0
binutils 2.23.2
boost 1.53.0
cairo 1.12.14
cgal 4.2
cloog 0.18.0
cmake 2.8.10.2 2.8.11.1
cminpack 1.3.0
dhex 0.68
eigen 3.1.3
flann 1.8.4
fontconfig 2.10.92
freetype 2.4.11
gcc48 4.8.0
gdk-pixbuf 2.28.1
gettext 0.18.2
gfortran 4.8.0
glew 1.9.0
glfw 2.7.8
glib 2.36.2
gmp 5.1.1
gsl 1.15
gtk+ 2.24.18
gts 0.7.6
harfbuzz 0.9.16
hdf5 1.8.11
icu4c 51.1
imagemagick 6.8.0-10
isl 0.11.1 0.11.2
jpeg 8d
libffi 3.0.13
libmpc 1.0.1
libpng 1.5.14
libtiff 4.0.3
libtool 2.4.2
libusb 1.0.9
mpfr 3.1.1-p2 3.1.2
node 0.10.7
pango 1.34.1
pixman 0.30.0
pkg-config 0.28
qhull 2012.1
szip 2.1
vtk 5.10.1
xz 5.0.4










As to the 'rant 'part I was trying to
give some general feedback in a friendly and narrative manner
as I thought it would more palatable and easier to digest that
way. 

I was wrong.

That was sort of general feedback I was hoping to give, not
expecting anyone to respond to it or act on it, just wanted
to share because most projects say they want feedback...

I thought that by given examples of my difficulties would
illustrate the issue better than just a brief statement 
that 'I think this is wrong/bad'.

Sorry I failed.

br Kusti






From: Alexandru-Eugen Ichim <[hidden email]>
Reply-To: "Point Cloud Library (PCL) users" <[hidden email]>
Date: Thu, 13 Jun 2013 15:02:19 +0300
To: "Point Cloud Library (PCL) users" <[hidden email]>
Subject: Re: [PCL-users] PCL on Mac OS X Mountain Lion

Hi Kustaa,

I am sad to hear about your bad experiences with PCL on MacOS. I personally use MacPorts and never had problems getting PCL to run quickly on fresh Macs.
Also, if you don't give us the exact errors you encountered, but just long rants (I guarantee that nobody spent time to read your long emails entirely :) ) - there is no way for us to fix the problems and provide the users with better support.

Cheers and good luck with your project!
Alex




On Thu, Jun 13, 2013 at 11:37 AM, Kustaa Nyholm <[hidden email]> wrote:
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

>http://www.pcl-users.org/Successful-PCL-Build-from-Source-on-Mac-OS-X-incl
>uding-Kinfu-td4022018.html
>
>
>Cheers,
>Radu.
>--
>http://openperception.org
>
>On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
>>Hi,
>>
>>having had a frustrating two days trying to install PCL on my
>>own I decided to seek for help...
>>
>>I tried the binaries from here:
>>
>>http://www.pointclouds.org/downloads/
>>
>>but they did not work, I've already forgotten what's the issue,
>>might have been that I was unable to install VTK...
>>IIRC I could get it to compile by installing a bunch of
>>stuff via MacPorts but then a simple
>>C program with just main() with out calling anything
>>in PCL fails to load because it cannot find VTK...
>>which is kind...ermh annoying as I have no need for
>>VTK...to me it seems that strictly 'point cloud only'
>>library without dependencies on libusb, OpenNI
>>and VTK would make sense, I could do without boost too,
>>though eigen seem like a good idea...but I digress.
>>
>>Anyway, I'm a homebrew user so eventually I just
>>delete everything related to macports and PCL
>>and started from scratch with these instructions:
>>
>>http://www.pointclouds.org/documentation/tutorials/installing_homebrew.ph
>>p
>>
>>This went rather well once I discovered the
>>'brew tap homebrew/science' to get the dependencies
>>to install as per instructions, which might be a
>>handy tip for people like me who
>>are not so up to speed with all things homebrew.
>>
>>However at the end this failed because the tar file
>>the brew expects for PCL has move. Little bit of googling
>>enabled me to find the 1.6.0 tar file and hacking
>>the pcl.rb file allowed the download to succeed and
>>compile begun. BTW is there an up to date .rb file
>>somewhere?
>>
>>In the end that compilation failed at 8% mark with
>>mysterious error
>>
>>make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
>>make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
>>make: *** [all] Error 2
>>
>>
>>Manually compiling PCL revealed that this related to
>>some or other 'at' symbol not being found which after
>>a little googling seems to be a problem with Apple clang.
>>
>>I was not prepared to go back to gcc (supposing it
>>was available for Mountain Lion and latest X-code)
>>and after googling that the issue was supposed to
>>be fixed about a year ago I tried to compile from
>>the trunk with:
>>
>>brew install pcl --HEAD
>>
>>this goes quite a long way but eventually fails
>>with the mysterious Error 2:
>>
>>dyld: DYLD_ environment variables being ignored because main executable
>>(/usr/bin/sudo) is setuid or setgid
>>==> Checking out http://svn.pointclouds.org/pcl/trunk
>>==> mkdir build
>>==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
>>-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
>>==> make install
>>[ 98%] Built target test_registration
>>Linking CXX shared library ../lib/libpcl_recognition.dylib
>>brew: superenv removed: -Wno-invalid-offsetof
>>[ 98%] Built target pcl_recognition
>>make: *** [all] Error 2
>>
>>
>>
>>At this point I decided to seek some help, especially
>>as I saw a couple notes that claimed that this
>>install from source without a hitch on Mountain Lion.
>>
>>So is there an up to date instruction for doing this somewhere
>>or can someone please give me hand to make this happen?
>>
>>br Kusti
>>
>>
>>
>>
>>This e-mail may contain confidential or privileged information. If you
>>are not the intended recipient (or have received this e-mail in error)
>>please notify the sender immediately and destroy this e-mail. Any
>>unauthorized copying, disclosure or distribution of the material in this
>>e-mail is strictly forbidden. We will not be liable for direct,
>>indirect, special or consequential damages arising from alteration of
>>the contents of this message by a third party or as a result of any
>>virus being passed on or as of transmission of this e-mail in general.
>>_______________________________________________
>>[hidden email] / http://pointclouds.org
>>http://pointclouds.org/mailman/listinfo/pcl-users
>>
>


--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: <a href="tel:%2B358%2020%207795%20572" value="+358207795572" target="_blank">+358 20 7795 572 (direct)
Fax: <a href="tel:%2B358%2020%207795%20676" value="+358207795676" target="_blank">+358 20 7795 676
GSM: <a href="tel:%2B358%2040%20580%205193" value="+358405805193" target="_blank">+358 40 580 5193
e-mail: [hidden email]







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users



_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

Radu B. Rusu
Administrator
In reply to this post by Kustaa Nyholm
Kustaa,

Your comments about VTK are definitely not appreciated. I can see where you're coming from, perhaps you had bad
experiences in the past with VTK, but still. Our colleagues from Kitware worked hard to give us a comprehensive set of
_open source_ visualization libraries. If you don't like it, please don't use it. Would you rather they wouldn't have
open sourced it? I sure as hell wouldn't.

If you look around carefully, you'll notice the following problems in your reasoning:

  *  PCL (and VTK, and Boost, and others) are generic multi-library projects, that can be compiled conditionally, based
on what library or module you would want to use from them. If you don't want to use VTK, simply tell PCL that you'd like
to compile its modules without VTK. You'll drop the pcl_visualization library as well as some converter modules in
pcl_io, but that's about it.

  * the errors that you posted regarding the GitHub master branch of PCL are easily fixable and pertain to the
pcl_people library/module. Simply disable it for now, and contact the respective developers to fix it, or submit a fix
yourself. It's an open community, open platform, open access, and the code that you're compiling is bleeding edge
master/trunk.

When it comes to open source 3rd party libraries and Mac OS, we will always have issues, as Apple is not built around
open source communities, and you'll always find more Linux developers for a project like ours than anything else. It's
all a matter of how we deal with this as a community and work together to solve these problems that matters. Rants are
great, but they should be followed with "oh, and here's the patch that fixes this...". Otherwise they're just long
e-mails that most people, as Alex mentioned it, tend to ignore.

Good luck reimplementing from scratch the algorithms that you need. Sounds like a great way to spend your time :)
(http://www.openperception.org/wp-content/uploads/2012/06/development_timeline.png). I'm still hoping that you'll
reconsider -- at least you've gotten awesome support on PCL mailing lists - so we must be doing something right.

Cheers,
Radu.
--
http://openperception.org

On 06/13/2013 02:37 AM, Kustaa Nyholm wrote:

> Hi Radu,
>
> thanks for the link I had not stumbled up on it earlier.
>
> Reading through Ken's nice writeup it looks daunting and
> fragile in that I'm as likely to fail with those instructions
> than on my own.
>
> I tried the superbuild but that fails to build flan which
> brew builds without a hitch.
>
> At the moment I think I'm going to give PCL a rest and
> concentrate on re-implementing from scratch the few bits
> and algorithms I was hoping to use from PCL. I think my
> time is better utilised in writing code than trying to
> resolve build issues and dependencies with huge C-libraries.
>
> PCL looked so promising and interesting that I gave it
> a chance and  let my stead fast rule never to use any
> large C-code base that does not compile out-of-the-box.
>
> Sad, but there it is, the C-toolchain and the tendency
> to re-use code by depending on other complex libraries
> seems to me to be the biggest stumbling block for code (re)use.
>
> I hope to come back to PCL in the future when the build
> process on Mac is mature enough so that I don't have
> to struggle with it.
>
> Meanwhile I hope the project/build structure could
> be so re-structured that users could just use the
> parts they need without needing to whole rigmarole build.
>
> I can live with boost and eigen and it is difficult
> to see that it would make sense to attempt something
> like PCL without them but VTK ... oh please...without
> that monster I've had been in business long time ago.
>
> Just MO.
>
> br Kusti
>
>
>
>
>
> On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:
>
>> http://www.pcl-users.org/Successful-PCL-Build-from-Source-on-Mac-OS-X-incl
>> uding-Kinfu-td4022018.html
>>
>>
>> Cheers,
>> Radu.
>> --
>> http://openperception.org
>>
>> On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
>>> Hi,
>>>
>>> having had a frustrating two days trying to install PCL on my
>>> own I decided to seek for help...
>>>
>>> I tried the binaries from here:
>>>
>>> http://www.pointclouds.org/downloads/
>>>
>>> but they did not work, I've already forgotten what's the issue,
>>> might have been that I was unable to install VTK...
>>> IIRC I could get it to compile by installing a bunch of
>>> stuff via MacPorts but then a simple
>>> C program with just main() with out calling anything
>>> in PCL fails to load because it cannot find VTK...
>>> which is kind...ermh annoying as I have no need for
>>> VTK...to me it seems that strictly 'point cloud only'
>>> library without dependencies on libusb, OpenNI
>>> and VTK would make sense, I could do without boost too,
>>> though eigen seem like a good idea...but I digress.
>>>
>>> Anyway, I'm a homebrew user so eventually I just
>>> delete everything related to macports and PCL
>>> and started from scratch with these instructions:
>>>
>>> http://www.pointclouds.org/documentation/tutorials/installing_homebrew.ph
>>> p
>>>
>>> This went rather well once I discovered the
>>> 'brew tap homebrew/science' to get the dependencies
>>> to install as per instructions, which might be a
>>> handy tip for people like me who
>>> are not so up to speed with all things homebrew.
>>>
>>> However at the end this failed because the tar file
>>> the brew expects for PCL has move. Little bit of googling
>>> enabled me to find the 1.6.0 tar file and hacking
>>> the pcl.rb file allowed the download to succeed and
>>> compile begun. BTW is there an up to date .rb file
>>> somewhere?
>>>
>>> In the end that compilation failed at 8% mark with
>>> mysterious error
>>>
>>> make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
>>> make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
>>> make: *** [all] Error 2
>>>
>>>
>>> Manually compiling PCL revealed that this related to
>>> some or other 'at' symbol not being found which after
>>> a little googling seems to be a problem with Apple clang.
>>>
>>> I was not prepared to go back to gcc (supposing it
>>> was available for Mountain Lion and latest X-code)
>>> and after googling that the issue was supposed to
>>> be fixed about a year ago I tried to compile from
>>> the trunk with:
>>>
>>> brew install pcl --HEAD
>>>
>>> this goes quite a long way but eventually fails
>>> with the mysterious Error 2:
>>>
>>> dyld: DYLD_ environment variables being ignored because main executable
>>> (/usr/bin/sudo) is setuid or setgid
>>> ==> Checking out http://svn.pointclouds.org/pcl/trunk
>>> ==> mkdir build
>>> ==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
>>> -DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
>>> ==> make install
>>> [ 98%] Built target test_registration
>>> Linking CXX shared library ../lib/libpcl_recognition.dylib
>>> brew: superenv removed: -Wno-invalid-offsetof
>>> [ 98%] Built target pcl_recognition
>>> make: *** [all] Error 2
>>>
>>>
>>>
>>> At this point I decided to seek some help, especially
>>> as I saw a couple notes that claimed that this
>>> install from source without a hitch on Mountain Lion.
>>>
>>> So is there an up to date instruction for doing this somewhere
>>> or can someone please give me hand to make this happen?
>>>
>>> br Kusti
>>>
>>>
>>>
>>>
>>> This e-mail may contain confidential or privileged information. If you
>>> are not the intended recipient (or have received this e-mail in error)
>>> please notify the sender immediately and destroy this e-mail. Any
>>> unauthorized copying, disclosure or distribution of the material in this
>>> e-mail is strictly forbidden. We will not be liable for direct,
>>> indirect, special or consequential damages arising from alteration of
>>> the contents of this message by a third party or as a result of any
>>> virus being passed on or as of transmission of this e-mail in general.
>>> _______________________________________________
>>> [hidden email] / http://pointclouds.org
>>> http://pointclouds.org/mailman/listinfo/pcl-users
>>>
>>
>
>
> --
> Kustaa Nyholm
> Research Manager, Software
> Research and Technology Division
> PLANMECA OY
> Asentajankatu 6
> 00880 HELSINKI
> FINLAND
>
> Please note our new telephone and fax numbers!
> Tel: +358 20 7795 572 (direct)
> Fax: +358 20 7795 676
> GSM: +358 40 580 5193
> e-mail: [hidden email]
>
>
>
>
>
>
>
> This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
> _______________________________________________
> [hidden email] / http://pointclouds.org
> http://pointclouds.org/mailman/listinfo/pcl-users
>
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

Kustaa Nyholm
Hi Radu,

I'm sorry I offended you, that was not my intention.

I'm glad to hear that the pcl_people_library/module can be easily
disabled, I'm going to try that next. Thanks for helping
and pointing out the solution. And thanks for Alex
too for his help.

I may even contact the authors of that module or
supply a patch, if I can come up with one.

BTW it was not my intention to use the bleeding edge,
this was an attempt because of an other compile problem
with the stable version, which I pressumed would at
least compile without a problem.

----


Everyone not really interested in this should now touch
that dial and tune out as this is likely to run to
some number of lines as I'm going to discuss some
some of Radu's other points.

I was not (trying to be) derogatory about VTK, my point
was simply that it is not what everyone needs or can use,
it is not a panacea. I sure appreciate their efforts
and applaud that it was open sourced. And for some
tasks it works admirably I'm sure, for the tasks we
tried it some years ago it did not and we coded from
scratch to get the speed and features we needed.
Having said that I truly appreciate the years of
hard word, craftsmanship and resource that has gone in
to it.

But making it mandatory dependency on a general purpose
triangulation library does seem to go against the grain.

You say that "don't want to use VTK, simply tell PCL
to compile its modules without VTK", well I can't
get PCL to compile in the first place, which was my
main problem. The binaries I found for Mac OS X
did not work because they insisted on VTK even though
my code (empty main()) did not use them. My code
compiled and linked but failed to load. The PCL
webpage says that VTK is mandatory. When I checked
the CMake script I did not spot how to disable
VTK dependency, but then I'm new to CMake.

So excuse me when I was mistaken.

But apparently I've somehow now managed to get
VTK to compile (via brew) cause when I try to
brew install it, brew tells me it is already installed,
so that won't bother me anymore.

As to Open source, Mac, Linux I agree with you but
without wanting to expand the discussion I just want
point out that some projects work better than others
(not refering to or trying to  sneak in a derogatory
comment for PCL) and some languages / build system
are better that other in that respect.

I appreciate your comment about implementing from scratch,
well the thing I'm after is not really implemented in
PCL so I would be doing some scratch building anyway
and the thing is so small that I'm pretty sure it would
be half done by now if I had not decided to use PCL
as a reference.

But I've not totally given up on PCL yet. And I hope
you have not given up an me, I appreciate all the
help and even backfire like Rafu's mail.

Once again I'm sorry if I offended anyone and I thank
you all for the help I've received. And like I said
PCL looks awesome and promising, I wouldn't be here
writing long emails that no-one will read and
everyone ignores if I thought otherwise.

One More Thing (tm): Rafu you wrote: "a matter of how
we deal with this as a community and work together
to solve these problems that matters" I of course
agree with that but I don't think either of scored
big time in this discussion, a simple attempt to point
out that my opinion that PCL would be better off
without mandatory VTK dependency turned into the
beginnings of a flame exchange.

cheers Kusti



On 13/06/2013 18:17, "Radu B. Rusu" <[hidden email]> wrote:

>Kustaa,
>
>Your comments about VTK are definitely not appreciated. I can see where
>you're coming from, perhaps you had bad
>experiences in the past with VTK, but still. Our colleagues from Kitware
>worked hard to give us a comprehensive set of
>_open source_ visualization libraries. If you don't like it, please don't
>use it. Would you rather they wouldn't have
>open sourced it? I sure as hell wouldn't.
>
>If you look around carefully, you'll notice the following problems in
>your reasoning:
>
>  *  PCL (and VTK, and Boost, and others) are generic multi-library
>projects, that can be compiled conditionally, based
>on what library or module you would want to use from them. If you don't
>want to use VTK, simply tell PCL that you'd like
>to compile its modules without VTK. You'll drop the pcl_visualization
>library as well as some converter modules in
>pcl_io, but that's about it.
>
>  * the errors that you posted regarding the GitHub master branch of PCL
>are easily fixable and pertain to the
>pcl_people library/module. Simply disable it for now, and contact the
>respective developers to fix it, or submit a fix
>yourself. It's an open community, open platform, open access, and the
>code that you're compiling is bleeding edge
>master/trunk.
>
>When it comes to open source 3rd party libraries and Mac OS, we will
>always have issues, as Apple is not built around
>open source communities, and you'll always find more Linux developers for
>a project like ours than anything else. It's
>all a matter of how we deal with this as a community and work together to
>solve these problems that matters. Rants are
>great, but they should be followed with "oh, and here's the patch that
>fixes this...". Otherwise they're just long
>e-mails that most people, as Alex mentioned it, tend to ignore.
>
>Good luck reimplementing from scratch the algorithms that you need.
>Sounds like a great way to spend your time :)
>(http://www.openperception.org/wp-content/uploads/2012/06/development_time
>line.png). I'm still hoping that you'll
>reconsider -- at least you've gotten awesome support on PCL mailing lists
>- so we must be doing something right.
>
>Cheers,
>Radu.
>--
>http://openperception.org
>
>On 06/13/2013 02:37 AM, Kustaa Nyholm wrote:
>>Hi Radu,
>>
>>thanks for the link I had not stumbled up on it earlier.
>>
>>Reading through Ken's nice writeup it looks daunting and
>>fragile in that I'm as likely to fail with those instructions
>>than on my own.
>>
>>I tried the superbuild but that fails to build flan which
>>brew builds without a hitch.
>>
>>At the moment I think I'm going to give PCL a rest and
>>concentrate on re-implementing from scratch the few bits
>>and algorithms I was hoping to use from PCL. I think my
>>time is better utilised in writing code than trying to
>>resolve build issues and dependencies with huge C-libraries.
>>
>>PCL looked so promising and interesting that I gave it
>>a chance and  let my stead fast rule never to use any
>>large C-code base that does not compile out-of-the-box.
>>
>>Sad, but there it is, the C-toolchain and the tendency
>>to re-use code by depending on other complex libraries
>>seems to me to be the biggest stumbling block for code (re)use.
>>
>>I hope to come back to PCL in the future when the build
>>process on Mac is mature enough so that I don't have
>>to struggle with it.
>>
>>Meanwhile I hope the project/build structure could
>>be so re-structured that users could just use the
>>parts they need without needing to whole rigmarole build.
>>
>>I can live with boost and eigen and it is difficult
>>to see that it would make sense to attempt something
>>like PCL without them but VTK ... oh please...without
>>that monster I've had been in business long time ago.
>>
>>Just MO.
>>
>>br Kusti
>>
>>
>>
>>
>>
>>On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:
>>
>>>http://www.pcl-users.org/Successful-PCL-Build-from-Source-on-Mac-OS-X-in
>>>cl
>>>uding-Kinfu-td4022018.html
>>>
>>>
>>>Cheers,
>>>Radu.
>>>--
>>>http://openperception.org
>>>
>>>On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
>>>>Hi,
>>>>
>>>>having had a frustrating two days trying to install PCL on my
>>>>own I decided to seek for help...
>>>>
>>>>I tried the binaries from here:
>>>>
>>>>http://www.pointclouds.org/downloads/
>>>>
>>>>but they did not work, I've already forgotten what's the issue,
>>>>might have been that I was unable to install VTK...
>>>>IIRC I could get it to compile by installing a bunch of
>>>>stuff via MacPorts but then a simple
>>>>C program with just main() with out calling anything
>>>>in PCL fails to load because it cannot find VTK...
>>>>which is kind...ermh annoying as I have no need for
>>>>VTK...to me it seems that strictly 'point cloud only'
>>>>library without dependencies on libusb, OpenNI
>>>>and VTK would make sense, I could do without boost too,
>>>>though eigen seem like a good idea...but I digress.
>>>>
>>>>Anyway, I'm a homebrew user so eventually I just
>>>>delete everything related to macports and PCL
>>>>and started from scratch with these instructions:
>>>>
>>>>http://www.pointclouds.org/documentation/tutorials/installing_homebrew.
>>>>ph
>>>>p
>>>>
>>>>This went rather well once I discovered the
>>>>'brew tap homebrew/science' to get the dependencies
>>>>to install as per instructions, which might be a
>>>>handy tip for people like me who
>>>>are not so up to speed with all things homebrew.
>>>>
>>>>However at the end this failed because the tar file
>>>>the brew expects for PCL has move. Little bit of googling
>>>>enabled me to find the 1.6.0 tar file and hacking
>>>>the pcl.rb file allowed the download to succeed and
>>>>compile begun. BTW is there an up to date .rb file
>>>>somewhere?
>>>>
>>>>In the end that compilation failed at 8% mark with
>>>>mysterious error
>>>>
>>>>make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
>>>>make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
>>>>make: *** [all] Error 2
>>>>
>>>>
>>>>Manually compiling PCL revealed that this related to
>>>>some or other 'at' symbol not being found which after
>>>>a little googling seems to be a problem with Apple clang.
>>>>
>>>>I was not prepared to go back to gcc (supposing it
>>>>was available for Mountain Lion and latest X-code)
>>>>and after googling that the issue was supposed to
>>>>be fixed about a year ago I tried to compile from
>>>>the trunk with:
>>>>
>>>>brew install pcl --HEAD
>>>>
>>>>this goes quite a long way but eventually fails
>>>>with the mysterious Error 2:
>>>>
>>>>dyld: DYLD_ environment variables being ignored because main executable
>>>>(/usr/bin/sudo) is setuid or setgid
>>>>==> Checking out http://svn.pointclouds.org/pcl/trunk
>>>>==> mkdir build
>>>>==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
>>>>-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
>>>>==> make install
>>>>[ 98%] Built target test_registration
>>>>Linking CXX shared library ../lib/libpcl_recognition.dylib
>>>>brew: superenv removed: -Wno-invalid-offsetof
>>>>[ 98%] Built target pcl_recognition
>>>>make: *** [all] Error 2
>>>>
>>>>
>>>>
>>>>At this point I decided to seek some help, especially
>>>>as I saw a couple notes that claimed that this
>>>>install from source without a hitch on Mountain Lion.
>>>>
>>>>So is there an up to date instruction for doing this somewhere
>>>>or can someone please give me hand to make this happen?
>>>>
>>>>br Kusti
>>>>
>>>>
>>>>
>>>>
>>>>This e-mail may contain confidential or privileged information. If you
>>>>are not the intended recipient (or have received this e-mail in error)
>>>>please notify the sender immediately and destroy this e-mail. Any
>>>>unauthorized copying, disclosure or distribution of the material in
>>>>this
>>>>e-mail is strictly forbidden. We will not be liable for direct,
>>>>indirect, special or consequential damages arising from alteration of
>>>>the contents of this message by a third party or as a result of any
>>>>virus being passed on or as of transmission of this e-mail in general.
>>>>_______________________________________________
>>>>[hidden email] / http://pointclouds.org
>>>>http://pointclouds.org/mailman/listinfo/pcl-users
>>>>
>>>
>>
>>
>>--
>>Kustaa Nyholm
>>Research Manager, Software
>>Research and Technology Division
>>PLANMECA OY
>>Asentajankatu 6
>>00880 HELSINKI
>>FINLAND
>>
>>Please note our new telephone and fax numbers!
>>Tel: +358 20 7795 572 (direct)
>>Fax: +358 20 7795 676
>>GSM: +358 40 580 5193
>>e-mail: [hidden email]
>>
>>
>>
>>
>>
>>
>>
>>This e-mail may contain confidential or privileged information. If you
>>are not the intended recipient (or have received this e-mail in error)
>>please notify the sender immediately and destroy this e-mail. Any
>>unauthorized copying, disclosure or distribution of the material in this
>>e-mail is strictly forbidden. We will not be liable for direct,
>>indirect, special or consequential damages arising from alteration of
>>the contents of this message by a third party or as a result of any
>>virus being passed on or as of transmission of this e-mail in general.
>>_______________________________________________
>>[hidden email] / http://pointclouds.org
>>http://pointclouds.org/mailman/listinfo/pcl-users
>>
>


--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 (direct)
Fax: +358 20 7795 676
GSM: +358 40 580 5193
e-mail: [hidden email]







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

fran6co
In reply to this post by Kustaa Nyholm
Hi Kusta,
   not sure if you fixed your Mac OSX problems already but you could try a my PCL homebrew formula by tapping it:

     brew tap fran6co/cv

you can install it by:

     brew install --HEAD pcl

if you want to build just the barebones PCL library without any GUI dependency you can install like this:

     brew install --HEAD pcl --without-apps --without-tools --without-vtk

Any feedback is much appreciated (you can add issues at https://github.com/fran6co/homebrew-cv).
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

Kustaa Nyholm


On 13/06/2013 20:35, "fran6co" <[hidden email]> wrote:

>Hi Kusta,
>   not sure if you fixed your Mac OSX problems already but you could try a
>my PCL homebrew formula by tapping it:
>
>     brew tap fran6co/cv
>
>you can install it by:
>
>     brew install --HEAD pcl
>
>if you want to build just the barebones PCL library without any GUI
>dependency you can install like this:
>
>     brew install --HEAD pcl --without-apps --without-tools --without-vtk
>
>Any feedback is much appreciated (you can add issues at
>https://github.com/fran6co/homebrew-cv).
>

Hi fran6co,

brilliant, just what I was looking for!

An instant brew, very fitting as I'm mainly Java!

After tapping for some reason brew did not found pcl
but I did

brew install fran6co/cv/pcl

and that worked (or atleast it compiled and finished
successfully, I need to test that yet).

Thanks a billion,

br Kusti

>


This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

Radu B. Rusu
Administrator
In reply to this post by Kustaa Nyholm
Kustaa,

Thanks for your e-mail. I did not take your comments about VTK to be derogatory, just simply stating that ranting with
respect to "open source software" should have a slightly different tone than our daily, more usual, rants. Although as
an user one is still "investing" time in figuring out an open source library, I get a bit more edgy at times about these
issues, and hence I tend to remind that person that there are people behind that library, working hard at times to give
back and provide open systems so that others can enjoy. Can they do better in certain areas? Of course! That's where
they need help...

You won't find too many flame exchanges on our mailing lists, other than the usual SVN vs GIT, which we solved (Jochen
won the argument through persistence :D), and this wouldn't have turned into one either. VTK is a great library with its
set of faults. Kitware has now been generously granted a large contract/grant to revitalize VTK and build the next
generation of scientific visualization libraries as part of VTK6. I've had my share of suggestions for how that should
look like, and I'm sure they would appreciate to hear even more.

You are right about PCL 1.6 not being MacOS friendly, when it comes to visualization. We tried our best to provide
binary DMGs, but due to a much smaller Mac OS PCL user community, we have not received enough feedback in order to fix
all issues in time. We need your help (and others' too) about making that clear on our web pages. We're also hoping to
kick out PCL 1.7 soon with better Mac OS support -- most if not all things have been fixed since 1.6 came out. We'll
need to patch pcl_people now as well.

PS. I'm happy that fran6co managed to help. That's where the power of an open source community resides.

Cheers,
Radu.
--
http://openperception.org

On 06/13/2013 09:42 AM, Kustaa Nyholm wrote:

> Hi Radu,
>
> I'm sorry I offended you, that was not my intention.
>
> I'm glad to hear that the pcl_people_library/module can be easily
> disabled, I'm going to try that next. Thanks for helping
> and pointing out the solution. And thanks for Alex
> too for his help.
>
> I may even contact the authors of that module or
> supply a patch, if I can come up with one.
>
> BTW it was not my intention to use the bleeding edge,
> this was an attempt because of an other compile problem
> with the stable version, which I pressumed would at
> least compile without a problem.
>
> ----
>
>
> Everyone not really interested in this should now touch
> that dial and tune out as this is likely to run to
> some number of lines as I'm going to discuss some
> some of Radu's other points.
>
> I was not (trying to be) derogatory about VTK, my point
> was simply that it is not what everyone needs or can use,
> it is not a panacea. I sure appreciate their efforts
> and applaud that it was open sourced. And for some
> tasks it works admirably I'm sure, for the tasks we
> tried it some years ago it did not and we coded from
> scratch to get the speed and features we needed.
> Having said that I truly appreciate the years of
> hard word, craftsmanship and resource that has gone in
> to it.
>
> But making it mandatory dependency on a general purpose
> triangulation library does seem to go against the grain.
>
> You say that "don't want to use VTK, simply tell PCL
> to compile its modules without VTK", well I can't
> get PCL to compile in the first place, which was my
> main problem. The binaries I found for Mac OS X
> did not work because they insisted on VTK even though
> my code (empty main()) did not use them. My code
> compiled and linked but failed to load. The PCL
> webpage says that VTK is mandatory. When I checked
> the CMake script I did not spot how to disable
> VTK dependency, but then I'm new to CMake.
>
> So excuse me when I was mistaken.
>
> But apparently I've somehow now managed to get
> VTK to compile (via brew) cause when I try to
> brew install it, brew tells me it is already installed,
> so that won't bother me anymore.
>
> As to Open source, Mac, Linux I agree with you but
> without wanting to expand the discussion I just want
> point out that some projects work better than others
> (not refering to or trying to  sneak in a derogatory
> comment for PCL) and some languages / build system
> are better that other in that respect.
>
> I appreciate your comment about implementing from scratch,
> well the thing I'm after is not really implemented in
> PCL so I would be doing some scratch building anyway
> and the thing is so small that I'm pretty sure it would
> be half done by now if I had not decided to use PCL
> as a reference.
>
> But I've not totally given up on PCL yet. And I hope
> you have not given up an me, I appreciate all the
> help and even backfire like Rafu's mail.
>
> Once again I'm sorry if I offended anyone and I thank
> you all for the help I've received. And like I said
> PCL looks awesome and promising, I wouldn't be here
> writing long emails that no-one will read and
> everyone ignores if I thought otherwise.
>
> One More Thing (tm): Rafu you wrote: "a matter of how
> we deal with this as a community and work together
> to solve these problems that matters" I of course
> agree with that but I don't think either of scored
> big time in this discussion, a simple attempt to point
> out that my opinion that PCL would be better off
> without mandatory VTK dependency turned into the
> beginnings of a flame exchange.
>
> cheers Kusti
>
>
>
> On 13/06/2013 18:17, "Radu B. Rusu" <[hidden email]> wrote:
>
>> Kustaa,
>>
>> Your comments about VTK are definitely not appreciated. I can see where
>> you're coming from, perhaps you had bad
>> experiences in the past with VTK, but still. Our colleagues from Kitware
>> worked hard to give us a comprehensive set of
>> _open source_ visualization libraries. If you don't like it, please don't
>> use it. Would you rather they wouldn't have
>> open sourced it? I sure as hell wouldn't.
>>
>> If you look around carefully, you'll notice the following problems in
>> your reasoning:
>>
>>   *  PCL (and VTK, and Boost, and others) are generic multi-library
>> projects, that can be compiled conditionally, based
>> on what library or module you would want to use from them. If you don't
>> want to use VTK, simply tell PCL that you'd like
>> to compile its modules without VTK. You'll drop the pcl_visualization
>> library as well as some converter modules in
>> pcl_io, but that's about it.
>>
>>   * the errors that you posted regarding the GitHub master branch of PCL
>> are easily fixable and pertain to the
>> pcl_people library/module. Simply disable it for now, and contact the
>> respective developers to fix it, or submit a fix
>> yourself. It's an open community, open platform, open access, and the
>> code that you're compiling is bleeding edge
>> master/trunk.
>>
>> When it comes to open source 3rd party libraries and Mac OS, we will
>> always have issues, as Apple is not built around
>> open source communities, and you'll always find more Linux developers for
>> a project like ours than anything else. It's
>> all a matter of how we deal with this as a community and work together to
>> solve these problems that matters. Rants are
>> great, but they should be followed with "oh, and here's the patch that
>> fixes this...". Otherwise they're just long
>> e-mails that most people, as Alex mentioned it, tend to ignore.
>>
>> Good luck reimplementing from scratch the algorithms that you need.
>> Sounds like a great way to spend your time :)
>> (http://www.openperception.org/wp-content/uploads/2012/06/development_time
>> line.png). I'm still hoping that you'll
>> reconsider -- at least you've gotten awesome support on PCL mailing lists
>> - so we must be doing something right.
>>
>> Cheers,
>> Radu.
>> --
>> http://openperception.org
>>
>> On 06/13/2013 02:37 AM, Kustaa Nyholm wrote:
>>> Hi Radu,
>>>
>>> thanks for the link I had not stumbled up on it earlier.
>>>
>>> Reading through Ken's nice writeup it looks daunting and
>>> fragile in that I'm as likely to fail with those instructions
>>> than on my own.
>>>
>>> I tried the superbuild but that fails to build flan which
>>> brew builds without a hitch.
>>>
>>> At the moment I think I'm going to give PCL a rest and
>>> concentrate on re-implementing from scratch the few bits
>>> and algorithms I was hoping to use from PCL. I think my
>>> time is better utilised in writing code than trying to
>>> resolve build issues and dependencies with huge C-libraries.
>>>
>>> PCL looked so promising and interesting that I gave it
>>> a chance and  let my stead fast rule never to use any
>>> large C-code base that does not compile out-of-the-box.
>>>
>>> Sad, but there it is, the C-toolchain and the tendency
>>> to re-use code by depending on other complex libraries
>>> seems to me to be the biggest stumbling block for code (re)use.
>>>
>>> I hope to come back to PCL in the future when the build
>>> process on Mac is mature enough so that I don't have
>>> to struggle with it.
>>>
>>> Meanwhile I hope the project/build structure could
>>> be so re-structured that users could just use the
>>> parts they need without needing to whole rigmarole build.
>>>
>>> I can live with boost and eigen and it is difficult
>>> to see that it would make sense to attempt something
>>> like PCL without them but VTK ... oh please...without
>>> that monster I've had been in business long time ago.
>>>
>>> Just MO.
>>>
>>> br Kusti
>>>
>>>
>>>
>>>
>>>
>>> On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:
>>>
>>>> http://www.pcl-users.org/Successful-PCL-Build-from-Source-on-Mac-OS-X-in
>>>> cl
>>>> uding-Kinfu-td4022018.html
>>>>
>>>>
>>>> Cheers,
>>>> Radu.
>>>> --
>>>> http://openperception.org
>>>>
>>>> On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
>>>>> Hi,
>>>>>
>>>>> having had a frustrating two days trying to install PCL on my
>>>>> own I decided to seek for help...
>>>>>
>>>>> I tried the binaries from here:
>>>>>
>>>>> http://www.pointclouds.org/downloads/
>>>>>
>>>>> but they did not work, I've already forgotten what's the issue,
>>>>> might have been that I was unable to install VTK...
>>>>> IIRC I could get it to compile by installing a bunch of
>>>>> stuff via MacPorts but then a simple
>>>>> C program with just main() with out calling anything
>>>>> in PCL fails to load because it cannot find VTK...
>>>>> which is kind...ermh annoying as I have no need for
>>>>> VTK...to me it seems that strictly 'point cloud only'
>>>>> library without dependencies on libusb, OpenNI
>>>>> and VTK would make sense, I could do without boost too,
>>>>> though eigen seem like a good idea...but I digress.
>>>>>
>>>>> Anyway, I'm a homebrew user so eventually I just
>>>>> delete everything related to macports and PCL
>>>>> and started from scratch with these instructions:
>>>>>
>>>>> http://www.pointclouds.org/documentation/tutorials/installing_homebrew.
>>>>> ph
>>>>> p
>>>>>
>>>>> This went rather well once I discovered the
>>>>> 'brew tap homebrew/science' to get the dependencies
>>>>> to install as per instructions, which might be a
>>>>> handy tip for people like me who
>>>>> are not so up to speed with all things homebrew.
>>>>>
>>>>> However at the end this failed because the tar file
>>>>> the brew expects for PCL has move. Little bit of googling
>>>>> enabled me to find the 1.6.0 tar file and hacking
>>>>> the pcl.rb file allowed the download to succeed and
>>>>> compile begun. BTW is there an up to date .rb file
>>>>> somewhere?
>>>>>
>>>>> In the end that compilation failed at 8% mark with
>>>>> mysterious error
>>>>>
>>>>> make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
>>>>> make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
>>>>> make: *** [all] Error 2
>>>>>
>>>>>
>>>>> Manually compiling PCL revealed that this related to
>>>>> some or other 'at' symbol not being found which after
>>>>> a little googling seems to be a problem with Apple clang.
>>>>>
>>>>> I was not prepared to go back to gcc (supposing it
>>>>> was available for Mountain Lion and latest X-code)
>>>>> and after googling that the issue was supposed to
>>>>> be fixed about a year ago I tried to compile from
>>>>> the trunk with:
>>>>>
>>>>> brew install pcl --HEAD
>>>>>
>>>>> this goes quite a long way but eventually fails
>>>>> with the mysterious Error 2:
>>>>>
>>>>> dyld: DYLD_ environment variables being ignored because main executable
>>>>> (/usr/bin/sudo) is setuid or setgid
>>>>> ==> Checking out http://svn.pointclouds.org/pcl/trunk
>>>>> ==> mkdir build
>>>>> ==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
>>>>> -DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
>>>>> ==> make install
>>>>> [ 98%] Built target test_registration
>>>>> Linking CXX shared library ../lib/libpcl_recognition.dylib
>>>>> brew: superenv removed: -Wno-invalid-offsetof
>>>>> [ 98%] Built target pcl_recognition
>>>>> make: *** [all] Error 2
>>>>>
>>>>>
>>>>>
>>>>> At this point I decided to seek some help, especially
>>>>> as I saw a couple notes that claimed that this
>>>>> install from source without a hitch on Mountain Lion.
>>>>>
>>>>> So is there an up to date instruction for doing this somewhere
>>>>> or can someone please give me hand to make this happen?
>>>>>
>>>>> br Kusti
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> This e-mail may contain confidential or privileged information. If you
>>>>> are not the intended recipient (or have received this e-mail in error)
>>>>> please notify the sender immediately and destroy this e-mail. Any
>>>>> unauthorized copying, disclosure or distribution of the material in
>>>>> this
>>>>> e-mail is strictly forbidden. We will not be liable for direct,
>>>>> indirect, special or consequential damages arising from alteration of
>>>>> the contents of this message by a third party or as a result of any
>>>>> virus being passed on or as of transmission of this e-mail in general.
>>>>> _______________________________________________
>>>>> [hidden email] / http://pointclouds.org
>>>>> http://pointclouds.org/mailman/listinfo/pcl-users
>>>>>
>>>>
>>>
>>>
>>> --
>>> Kustaa Nyholm
>>> Research Manager, Software
>>> Research and Technology Division
>>> PLANMECA OY
>>> Asentajankatu 6
>>> 00880 HELSINKI
>>> FINLAND
>>>
>>> Please note our new telephone and fax numbers!
>>> Tel: +358 20 7795 572 (direct)
>>> Fax: +358 20 7795 676
>>> GSM: +358 40 580 5193
>>> e-mail: [hidden email]
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> This e-mail may contain confidential or privileged information. If you
>>> are not the intended recipient (or have received this e-mail in error)
>>> please notify the sender immediately and destroy this e-mail. Any
>>> unauthorized copying, disclosure or distribution of the material in this
>>> e-mail is strictly forbidden. We will not be liable for direct,
>>> indirect, special or consequential damages arising from alteration of
>>> the contents of this message by a third party or as a result of any
>>> virus being passed on or as of transmission of this e-mail in general.
>>> _______________________________________________
>>> [hidden email] / http://pointclouds.org
>>> http://pointclouds.org/mailman/listinfo/pcl-users
>>>
>>
>
>
> --
> Kustaa Nyholm
> Research Manager, Software
> Research and Technology Division
> PLANMECA OY
> Asentajankatu 6
> 00880 HELSINKI
> FINLAND
>
> Please note our new telephone and fax numbers!
> Tel: +358 20 7795 572 (direct)
> Fax: +358 20 7795 676
> GSM: +358 40 580 5193
> e-mail: [hidden email]
>
>
>
>
>
>
>
> This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
> _______________________________________________
> [hidden email] / http://pointclouds.org
> http://pointclouds.org/mailman/listinfo/pcl-users
>
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

Lv Zhaoyang
Hi Radu,

I'm also a Mac user, and getting PCL just in the last week. I also had a terrible experience with the Mac PCL version, and now I just turned to Ubuntu on my virtual machine. On ubuntu everything works fine now. Here are some problems I confronted: 

1. After I track the problems and google all the solutions. One problem is with the boost library. You can see it here. http://stackoverflow.com/questions/17054800/errors-in-boost-installed-from-both-macport-and-brew
No one respond me yet. So I turned to Linux finally. But the performance is affected on virtual machine. I am still glad to solve it on my mac. 

2. Vtk on my mac also has problem. I tried the visualisation tutorial, but no interface appears. 

3. I also disable two parts in PCL (I think it's the people_detection and outofcore). The PCL version I use it from github. In Linux, I don't need to disable anything.  

That's all the problem I finally got. If I solved these, there might be some new problems.  In general, it's not as easy as the Linux one. I spent 4 days configuring PCL on Mac. Then I turned to Linux, I solved everything in one day. The installation tutorial in Mac seems very old and not consistent. I tried at least all the three, macport, brew and the dmg file. That might be the reason I get conflicts in libs. Hope you can update it. 

I'm not a experienced programmer, still a student, a rookie in C++. We hope everything can get working quite easily and program, no need learn compiler and system. Of course, you are getting better and better. Hope this feedback can be useful. And I'm still waiting for my solutions.

Best,
Lv Zhaoyang

On 13 Jun 2013, at 22:26, "Radu B. Rusu" <[hidden email]> wrote:

Kustaa,

Thanks for your e-mail. I did not take your comments about VTK to be derogatory, just simply stating that ranting with respect to "open source software" should have a slightly different tone than our daily, more usual, rants. Although as an user one is still "investing" time in figuring out an open source library, I get a bit more edgy at times about these issues, and hence I tend to remind that person that there are people behind that library, working hard at times to give back and provide open systems so that others can enjoy. Can they do better in certain areas? Of course! That's where they need help...

You won't find too many flame exchanges on our mailing lists, other than the usual SVN vs GIT, which we solved (Jochen won the argument through persistence :D), and this wouldn't have turned into one either. VTK is a great library with its set of faults. Kitware has now been generously granted a large contract/grant to revitalize VTK and build the next generation of scientific visualization libraries as part of VTK6. I've had my share of suggestions for how that should look like, and I'm sure they would appreciate to hear even more.

You are right about PCL 1.6 not being MacOS friendly, when it comes to visualization. We tried our best to provide binary DMGs, but due to a much smaller Mac OS PCL user community, we have not received enough feedback in order to fix all issues in time. We need your help (and others' too) about making that clear on our web pages. We're also hoping to kick out PCL 1.7 soon with better Mac OS support -- most if not all things have been fixed since 1.6 came out. We'll need to patch pcl_people now as well.

PS. I'm happy that fran6co managed to help. That's where the power of an open source community resides.

Cheers,
Radu.
--
http://openperception.org

On 06/13/2013 09:42 AM, Kustaa Nyholm wrote:
Hi Radu,

I'm sorry I offended you, that was not my intention.

I'm glad to hear that the pcl_people_library/module can be easily
disabled, I'm going to try that next. Thanks for helping
and pointing out the solution. And thanks for Alex
too for his help.

I may even contact the authors of that module or
supply a patch, if I can come up with one.

BTW it was not my intention to use the bleeding edge,
this was an attempt because of an other compile problem
with the stable version, which I pressumed would at
least compile without a problem.

----


Everyone not really interested in this should now touch
that dial and tune out as this is likely to run to
some number of lines as I'm going to discuss some
some of Radu's other points.

I was not (trying to be) derogatory about VTK, my point
was simply that it is not what everyone needs or can use,
it is not a panacea. I sure appreciate their efforts
and applaud that it was open sourced. And for some
tasks it works admirably I'm sure, for the tasks we
tried it some years ago it did not and we coded from
scratch to get the speed and features we needed.
Having said that I truly appreciate the years of
hard word, craftsmanship and resource that has gone in
to it.

But making it mandatory dependency on a general purpose
triangulation library does seem to go against the grain.

You say that "don't want to use VTK, simply tell PCL
to compile its modules without VTK", well I can't
get PCL to compile in the first place, which was my
main problem. The binaries I found for Mac OS X
did not work because they insisted on VTK even though
my code (empty main()) did not use them. My code
compiled and linked but failed to load. The PCL
webpage says that VTK is mandatory. When I checked
the CMake script I did not spot how to disable
VTK dependency, but then I'm new to CMake.

So excuse me when I was mistaken.

But apparently I've somehow now managed to get
VTK to compile (via brew) cause when I try to
brew install it, brew tells me it is already installed,
so that won't bother me anymore.

As to Open source, Mac, Linux I agree with you but
without wanting to expand the discussion I just want
point out that some projects work better than others
(not refering to or trying to  sneak in a derogatory
comment for PCL) and some languages / build system
are better that other in that respect.

I appreciate your comment about implementing from scratch,
well the thing I'm after is not really implemented in
PCL so I would be doing some scratch building anyway
and the thing is so small that I'm pretty sure it would
be half done by now if I had not decided to use PCL
as a reference.

But I've not totally given up on PCL yet. And I hope
you have not given up an me, I appreciate all the
help and even backfire like Rafu's mail.

Once again I'm sorry if I offended anyone and I thank
you all for the help I've received. And like I said
PCL looks awesome and promising, I wouldn't be here
writing long emails that no-one will read and
everyone ignores if I thought otherwise.

One More Thing (tm): Rafu you wrote: "a matter of how
we deal with this as a community and work together
to solve these problems that matters" I of course
agree with that but I don't think either of scored
big time in this discussion, a simple attempt to point
out that my opinion that PCL would be better off
without mandatory VTK dependency turned into the
beginnings of a flame exchange.

cheers Kusti



On 13/06/2013 18:17, "Radu B. Rusu" <[hidden email]> wrote:

Kustaa,

Your comments about VTK are definitely not appreciated. I can see where
you're coming from, perhaps you had bad
experiences in the past with VTK, but still. Our colleagues from Kitware
worked hard to give us a comprehensive set of
_open source_ visualization libraries. If you don't like it, please don't
use it. Would you rather they wouldn't have
open sourced it? I sure as hell wouldn't.

If you look around carefully, you'll notice the following problems in
your reasoning:

 *  PCL (and VTK, and Boost, and others) are generic multi-library
projects, that can be compiled conditionally, based
on what library or module you would want to use from them. If you don't
want to use VTK, simply tell PCL that you'd like
to compile its modules without VTK. You'll drop the pcl_visualization
library as well as some converter modules in
pcl_io, but that's about it.

 * the errors that you posted regarding the GitHub master branch of PCL
are easily fixable and pertain to the
pcl_people library/module. Simply disable it for now, and contact the
respective developers to fix it, or submit a fix
yourself. It's an open community, open platform, open access, and the
code that you're compiling is bleeding edge
master/trunk.

When it comes to open source 3rd party libraries and Mac OS, we will
always have issues, as Apple is not built around
open source communities, and you'll always find more Linux developers for
a project like ours than anything else. It's
all a matter of how we deal with this as a community and work together to
solve these problems that matters. Rants are
great, but they should be followed with "oh, and here's the patch that
fixes this...". Otherwise they're just long
e-mails that most people, as Alex mentioned it, tend to ignore.

Good luck reimplementing from scratch the algorithms that you need.
Sounds like a great way to spend your time :)
(http://www.openperception.org/wp-content/uploads/2012/06/development_time
line.png). I'm still hoping that you'll
reconsider -- at least you've gotten awesome support on PCL mailing lists
- so we must be doing something right.

Cheers,
Radu.
--
http://openperception.org

On 06/13/2013 02:37 AM, Kustaa Nyholm wrote:
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

http://www.pcl-users.org/Successful-PCL-Build-from-Source-on-Mac-OS-X-in
cl
uding-Kinfu-td4022018.html


Cheers,
Radu.
--
http://openperception.org

On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
Hi,

having had a frustrating two days trying to install PCL on my
own I decided to seek for help...

I tried the binaries from here:

http://www.pointclouds.org/downloads/

but they did not work, I've already forgotten what's the issue,
might have been that I was unable to install VTK...
IIRC I could get it to compile by installing a bunch of
stuff via MacPorts but then a simple
C program with just main() with out calling anything
in PCL fails to load because it cannot find VTK...
which is kind...ermh annoying as I have no need for
VTK...to me it seems that strictly 'point cloud only'
library without dependencies on libusb, OpenNI
and VTK would make sense, I could do without boost too,
though eigen seem like a good idea...but I digress.

Anyway, I'm a homebrew user so eventually I just
delete everything related to macports and PCL
and started from scratch with these instructions:

http://www.pointclouds.org/documentation/tutorials/installing_homebrew.
ph
p

This went rather well once I discovered the
'brew tap homebrew/science' to get the dependencies
to install as per instructions, which might be a
handy tip for people like me who
are not so up to speed with all things homebrew.

However at the end this failed because the tar file
the brew expects for PCL has move. Little bit of googling
enabled me to find the 1.6.0 tar file and hacking
the pcl.rb file allowed the download to succeed and
compile begun. BTW is there an up to date .rb file
somewhere?

In the end that compilation failed at 8% mark with
mysterious error

make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
make: *** [all] Error 2


Manually compiling PCL revealed that this related to
some or other 'at' symbol not being found which after
a little googling seems to be a problem with Apple clang.

I was not prepared to go back to gcc (supposing it
was available for Mountain Lion and latest X-code)
and after googling that the issue was supposed to
be fixed about a year ago I tried to compile from
the trunk with:

brew install pcl --HEAD

this goes quite a long way but eventually fails
with the mysterious Error 2:

dyld: DYLD_ environment variables being ignored because main executable
(/usr/bin/sudo) is setuid or setgid
==> Checking out http://svn.pointclouds.org/pcl/trunk
==> mkdir build
==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
==> make install
[ 98%] Built target test_registration
Linking CXX shared library ../lib/libpcl_recognition.dylib
brew: superenv removed: -Wno-invalid-offsetof
[ 98%] Built target pcl_recognition
make: *** [all] Error 2



At this point I decided to seek some help, especially
as I saw a couple notes that claimed that this
install from source without a hitch on Mountain Lion.

So is there an up to date instruction for doing this somewhere
or can someone please give me hand to make this happen?

br Kusti




This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in
this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 (direct)
Fax: +358 20 7795 676
GSM: +358 40 580 5193
e-mail: [hidden email]







This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 (direct)
Fax: +358 20 7795 676
GSM: +358 40 580 5193
e-mail: [hidden email]







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users

_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

aichim
Administrator
Hi Lv,

1. That is not related to PCL. Especially that you are not a C++ expert, you should not try to combine libraries and package managers on MacOS. They are not made to collaborate with each other and you will run into trouble. I only use MacPorts, but HomeBrew gives very good results too.

2. You should make sure that you create .app bundles from CMake. There are discussions on how to do this on our mailing lists: simply do ADD_EXECUTABLE (my_exec MACOSX_BUNDLE file.cpp) or PCL_ADD_EXECUTABLE_OPT_BUNDLE (...).

3. Why do you need to do that? Open up a ticket on Github presenting your situation and the errors you get, and someone will take care of it.

Cheers,
Alex


On Fri, Jun 14, 2013 at 1:16 AM, Lv Zhaoyang <[hidden email]> wrote:
Hi Radu,

I'm also a Mac user, and getting PCL just in the last week. I also had a terrible experience with the Mac PCL version, and now I just turned to Ubuntu on my virtual machine. On ubuntu everything works fine now. Here are some problems I confronted: 

1. After I track the problems and google all the solutions. One problem is with the boost library. You can see it here. http://stackoverflow.com/questions/17054800/errors-in-boost-installed-from-both-macport-and-brew
No one respond me yet. So I turned to Linux finally. But the performance is affected on virtual machine. I am still glad to solve it on my mac. 

2. Vtk on my mac also has problem. I tried the visualisation tutorial, but no interface appears. 

3. I also disable two parts in PCL (I think it's the people_detection and outofcore). The PCL version I use it from github. In Linux, I don't need to disable anything.  

That's all the problem I finally got. If I solved these, there might be some new problems.  In general, it's not as easy as the Linux one. I spent 4 days configuring PCL on Mac. Then I turned to Linux, I solved everything in one day. The installation tutorial in Mac seems very old and not consistent. I tried at least all the three, macport, brew and the dmg file. That might be the reason I get conflicts in libs. Hope you can update it. 

I'm not a experienced programmer, still a student, a rookie in C++. We hope everything can get working quite easily and program, no need learn compiler and system. Of course, you are getting better and better. Hope this feedback can be useful. And I'm still waiting for my solutions.

Best,
Lv Zhaoyang

On 13 Jun 2013, at 22:26, "Radu B. Rusu" <[hidden email]> wrote:

Kustaa,

Thanks for your e-mail. I did not take your comments about VTK to be derogatory, just simply stating that ranting with respect to "open source software" should have a slightly different tone than our daily, more usual, rants. Although as an user one is still "investing" time in figuring out an open source library, I get a bit more edgy at times about these issues, and hence I tend to remind that person that there are people behind that library, working hard at times to give back and provide open systems so that others can enjoy. Can they do better in certain areas? Of course! That's where they need help...

You won't find too many flame exchanges on our mailing lists, other than the usual SVN vs GIT, which we solved (Jochen won the argument through persistence :D), and this wouldn't have turned into one either. VTK is a great library with its set of faults. Kitware has now been generously granted a large contract/grant to revitalize VTK and build the next generation of scientific visualization libraries as part of VTK6. I've had my share of suggestions for how that should look like, and I'm sure they would appreciate to hear even more.

You are right about PCL 1.6 not being MacOS friendly, when it comes to visualization. We tried our best to provide binary DMGs, but due to a much smaller Mac OS PCL user community, we have not received enough feedback in order to fix all issues in time. We need your help (and others' too) about making that clear on our web pages. We're also hoping to kick out PCL 1.7 soon with better Mac OS support -- most if not all things have been fixed since 1.6 came out. We'll need to patch pcl_people now as well.

PS. I'm happy that fran6co managed to help. That's where the power of an open source community resides.

Cheers,
Radu.
--
http://openperception.org

On 06/13/2013 09:42 AM, Kustaa Nyholm wrote:
Hi Radu,

I'm sorry I offended you, that was not my intention.

I'm glad to hear that the pcl_people_library/module can be easily
disabled, I'm going to try that next. Thanks for helping
and pointing out the solution. And thanks for Alex
too for his help.

I may even contact the authors of that module or
supply a patch, if I can come up with one.

BTW it was not my intention to use the bleeding edge,
this was an attempt because of an other compile problem
with the stable version, which I pressumed would at
least compile without a problem.

----


Everyone not really interested in this should now touch
that dial and tune out as this is likely to run to
some number of lines as I'm going to discuss some
some of Radu's other points.

I was not (trying to be) derogatory about VTK, my point
was simply that it is not what everyone needs or can use,
it is not a panacea. I sure appreciate their efforts
and applaud that it was open sourced. And for some
tasks it works admirably I'm sure, for the tasks we
tried it some years ago it did not and we coded from
scratch to get the speed and features we needed.
Having said that I truly appreciate the years of
hard word, craftsmanship and resource that has gone in
to it.

But making it mandatory dependency on a general purpose
triangulation library does seem to go against the grain.

You say that "don't want to use VTK, simply tell PCL
to compile its modules without VTK", well I can't
get PCL to compile in the first place, which was my
main problem. The binaries I found for Mac OS X
did not work because they insisted on VTK even though
my code (empty main()) did not use them. My code
compiled and linked but failed to load. The PCL
webpage says that VTK is mandatory. When I checked
the CMake script I did not spot how to disable
VTK dependency, but then I'm new to CMake.

So excuse me when I was mistaken.

But apparently I've somehow now managed to get
VTK to compile (via brew) cause when I try to
brew install it, brew tells me it is already installed,
so that won't bother me anymore.

As to Open source, Mac, Linux I agree with you but
without wanting to expand the discussion I just want
point out that some projects work better than others
(not refering to or trying to  sneak in a derogatory
comment for PCL) and some languages / build system
are better that other in that respect.

I appreciate your comment about implementing from scratch,
well the thing I'm after is not really implemented in
PCL so I would be doing some scratch building anyway
and the thing is so small that I'm pretty sure it would
be half done by now if I had not decided to use PCL
as a reference.

But I've not totally given up on PCL yet. And I hope
you have not given up an me, I appreciate all the
help and even backfire like Rafu's mail.

Once again I'm sorry if I offended anyone and I thank
you all for the help I've received. And like I said
PCL looks awesome and promising, I wouldn't be here
writing long emails that no-one will read and
everyone ignores if I thought otherwise.

One More Thing (tm): Rafu you wrote: "a matter of how
we deal with this as a community and work together
to solve these problems that matters" I of course
agree with that but I don't think either of scored
big time in this discussion, a simple attempt to point
out that my opinion that PCL would be better off
without mandatory VTK dependency turned into the
beginnings of a flame exchange.

cheers Kusti



On 13/06/2013 18:17, "Radu B. Rusu" <[hidden email]> wrote:

Kustaa,

Your comments about VTK are definitely not appreciated. I can see where
you're coming from, perhaps you had bad
experiences in the past with VTK, but still. Our colleagues from Kitware
worked hard to give us a comprehensive set of
_open source_ visualization libraries. If you don't like it, please don't
use it. Would you rather they wouldn't have
open sourced it? I sure as hell wouldn't.

If you look around carefully, you'll notice the following problems in
your reasoning:

 *  PCL (and VTK, and Boost, and others) are generic multi-library
projects, that can be compiled conditionally, based
on what library or module you would want to use from them. If you don't
want to use VTK, simply tell PCL that you'd like
to compile its modules without VTK. You'll drop the pcl_visualization
library as well as some converter modules in
pcl_io, but that's about it.

 * the errors that you posted regarding the GitHub master branch of PCL
are easily fixable and pertain to the
pcl_people library/module. Simply disable it for now, and contact the
respective developers to fix it, or submit a fix
yourself. It's an open community, open platform, open access, and the
code that you're compiling is bleeding edge
master/trunk.

When it comes to open source 3rd party libraries and Mac OS, we will
always have issues, as Apple is not built around
open source communities, and you'll always find more Linux developers for
a project like ours than anything else. It's
all a matter of how we deal with this as a community and work together to
solve these problems that matters. Rants are
great, but they should be followed with "oh, and here's the patch that
fixes this...". Otherwise they're just long
e-mails that most people, as Alex mentioned it, tend to ignore.

Good luck reimplementing from scratch the algorithms that you need.
Sounds like a great way to spend your time :)
(http://www.openperception.org/wp-content/uploads/2012/06/development_time
line.png). I'm still hoping that you'll
reconsider -- at least you've gotten awesome support on PCL mailing lists
- so we must be doing something right.

Cheers,
Radu.
--
http://openperception.org

On 06/13/2013 02:37 AM, Kustaa Nyholm wrote:
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

http://www.pcl-users.org/Successful-PCL-Build-from-Source-on-Mac-OS-X-in
cl
uding-Kinfu-td4022018.html


Cheers,
Radu.
--
http://openperception.org

On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
Hi,

having had a frustrating two days trying to install PCL on my
own I decided to seek for help...

I tried the binaries from here:

http://www.pointclouds.org/downloads/

but they did not work, I've already forgotten what's the issue,
might have been that I was unable to install VTK...
IIRC I could get it to compile by installing a bunch of
stuff via MacPorts but then a simple
C program with just main() with out calling anything
in PCL fails to load because it cannot find VTK...
which is kind...ermh annoying as I have no need for
VTK...to me it seems that strictly 'point cloud only'
library without dependencies on libusb, OpenNI
and VTK would make sense, I could do without boost too,
though eigen seem like a good idea...but I digress.

Anyway, I'm a homebrew user so eventually I just
delete everything related to macports and PCL
and started from scratch with these instructions:

http://www.pointclouds.org/documentation/tutorials/installing_homebrew.
ph
p

This went rather well once I discovered the
'brew tap homebrew/science' to get the dependencies
to install as per instructions, which might be a
handy tip for people like me who
are not so up to speed with all things homebrew.

However at the end this failed because the tar file
the brew expects for PCL has move. Little bit of googling
enabled me to find the 1.6.0 tar file and hacking
the pcl.rb file allowed the download to succeed and
compile begun. BTW is there an up to date .rb file
somewhere?

In the end that compilation failed at 8% mark with
mysterious error

make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
make: *** [all] Error 2


Manually compiling PCL revealed that this related to
some or other 'at' symbol not being found which after
a little googling seems to be a problem with Apple clang.

I was not prepared to go back to gcc (supposing it
was available for Mountain Lion and latest X-code)
and after googling that the issue was supposed to
be fixed about a year ago I tried to compile from
the trunk with:

brew install pcl --HEAD

this goes quite a long way but eventually fails
with the mysterious Error 2:

dyld: DYLD_ environment variables being ignored because main executable
(/usr/bin/sudo) is setuid or setgid
==> Checking out http://svn.pointclouds.org/pcl/trunk
==> mkdir build
==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
==> make install
[ 98%] Built target test_registration
Linking CXX shared library ../lib/libpcl_recognition.dylib
brew: superenv removed: -Wno-invalid-offsetof
[ 98%] Built target pcl_recognition
make: *** [all] Error 2



At this point I decided to seek some help, especially
as I saw a couple notes that claimed that this
install from source without a hitch on Mountain Lion.

So is there an up to date instruction for doing this somewhere
or can someone please give me hand to make this happen?

br Kusti




This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in
this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: <a href="tel:%2B358%2020%207795%20572" value="+358207795572" target="_blank">+358 20 7795 572 (direct)
Fax: <a href="tel:%2B358%2020%207795%20676" value="+358207795676" target="_blank">+358 20 7795 676
GSM: <a href="tel:%2B358%2040%20580%205193" value="+358405805193" target="_blank">+358 40 580 5193
e-mail: [hidden email]







This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: <a href="tel:%2B358%2020%207795%20572" value="+358207795572" target="_blank">+358 20 7795 572 (direct)
Fax: <a href="tel:%2B358%2020%207795%20676" value="+358207795676" target="_blank">+358 20 7795 676
GSM: <a href="tel:%2B358%2040%20580%205193" value="+358405805193" target="_blank">+358 40 580 5193
e-mail: [hidden email]







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users

_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users



_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

Lv Zhaoyang
Hi Alex, 

Thank you very much for your suggestion. I'll make a summary of my problems occurred. But before that, I want to uninstall the libs and try them from beginning. Do you have ideas to do that? 

Now my libs have been massed up. I need some suggestions how to fix it.

Cheers,
Lv Zhaoyang


On 14 Jun 2013, at 11:26, Alexandru-Eugen Ichim <[hidden email]> wrote:

Hi Lv,

1. That is not related to PCL. Especially that you are not a C++ expert, you should not try to combine libraries and package managers on MacOS. They are not made to collaborate with each other and you will run into trouble. I only use MacPorts, but HomeBrew gives very good results too.

2. You should make sure that you create .app bundles from CMake. There are discussions on how to do this on our mailing lists: simply do ADD_EXECUTABLE (my_exec MACOSX_BUNDLE file.cpp) or PCL_ADD_EXECUTABLE_OPT_BUNDLE (...).

3. Why do you need to do that? Open up a ticket on Github presenting your situation and the errors you get, and someone will take care of it.

Cheers,
Alex


On Fri, Jun 14, 2013 at 1:16 AM, Lv Zhaoyang <[hidden email]> wrote:
Hi Radu,

I'm also a Mac user, and getting PCL just in the last week. I also had a terrible experience with the Mac PCL version, and now I just turned to Ubuntu on my virtual machine. On ubuntu everything works fine now. Here are some problems I confronted: 

1. After I track the problems and google all the solutions. One problem is with the boost library. You can see it here. http://stackoverflow.com/questions/17054800/errors-in-boost-installed-from-both-macport-and-brew
No one respond me yet. So I turned to Linux finally. But the performance is affected on virtual machine. I am still glad to solve it on my mac. 

2. Vtk on my mac also has problem. I tried the visualisation tutorial, but no interface appears. 

3. I also disable two parts in PCL (I think it's the people_detection and outofcore). The PCL version I use it from github. In Linux, I don't need to disable anything.  

That's all the problem I finally got. If I solved these, there might be some new problems.  In general, it's not as easy as the Linux one. I spent 4 days configuring PCL on Mac. Then I turned to Linux, I solved everything in one day. The installation tutorial in Mac seems very old and not consistent. I tried at least all the three, macport, brew and the dmg file. That might be the reason I get conflicts in libs. Hope you can update it. 

I'm not a experienced programmer, still a student, a rookie in C++. We hope everything can get working quite easily and program, no need learn compiler and system. Of course, you are getting better and better. Hope this feedback can be useful. And I'm still waiting for my solutions.

Best,
Lv Zhaoyang

On 13 Jun 2013, at 22:26, "Radu B. Rusu" <[hidden email]> wrote:

Kustaa,

Thanks for your e-mail. I did not take your comments about VTK to be derogatory, just simply stating that ranting with respect to "open source software" should have a slightly different tone than our daily, more usual, rants. Although as an user one is still "investing" time in figuring out an open source library, I get a bit more edgy at times about these issues, and hence I tend to remind that person that there are people behind that library, working hard at times to give back and provide open systems so that others can enjoy. Can they do better in certain areas? Of course! That's where they need help...

You won't find too many flame exchanges on our mailing lists, other than the usual SVN vs GIT, which we solved (Jochen won the argument through persistence :D), and this wouldn't have turned into one either. VTK is a great library with its set of faults. Kitware has now been generously granted a large contract/grant to revitalize VTK and build the next generation of scientific visualization libraries as part of VTK6. I've had my share of suggestions for how that should look like, and I'm sure they would appreciate to hear even more.

You are right about PCL 1.6 not being MacOS friendly, when it comes to visualization. We tried our best to provide binary DMGs, but due to a much smaller Mac OS PCL user community, we have not received enough feedback in order to fix all issues in time. We need your help (and others' too) about making that clear on our web pages. We're also hoping to kick out PCL 1.7 soon with better Mac OS support -- most if not all things have been fixed since 1.6 came out. We'll need to patch pcl_people now as well.

PS. I'm happy that fran6co managed to help. That's where the power of an open source community resides.

Cheers,
Radu.
--
http://openperception.org

On 06/13/2013 09:42 AM, Kustaa Nyholm wrote:
Hi Radu,

I'm sorry I offended you, that was not my intention.

I'm glad to hear that the pcl_people_library/module can be easily
disabled, I'm going to try that next. Thanks for helping
and pointing out the solution. And thanks for Alex
too for his help.

I may even contact the authors of that module or
supply a patch, if I can come up with one.

BTW it was not my intention to use the bleeding edge,
this was an attempt because of an other compile problem
with the stable version, which I pressumed would at
least compile without a problem.

----


Everyone not really interested in this should now touch
that dial and tune out as this is likely to run to
some number of lines as I'm going to discuss some
some of Radu's other points.

I was not (trying to be) derogatory about VTK, my point
was simply that it is not what everyone needs or can use,
it is not a panacea. I sure appreciate their efforts
and applaud that it was open sourced. And for some
tasks it works admirably I'm sure, for the tasks we
tried it some years ago it did not and we coded from
scratch to get the speed and features we needed.
Having said that I truly appreciate the years of
hard word, craftsmanship and resource that has gone in
to it.

But making it mandatory dependency on a general purpose
triangulation library does seem to go against the grain.

You say that "don't want to use VTK, simply tell PCL
to compile its modules without VTK", well I can't
get PCL to compile in the first place, which was my
main problem. The binaries I found for Mac OS X
did not work because they insisted on VTK even though
my code (empty main()) did not use them. My code
compiled and linked but failed to load. The PCL
webpage says that VTK is mandatory. When I checked
the CMake script I did not spot how to disable
VTK dependency, but then I'm new to CMake.

So excuse me when I was mistaken.

But apparently I've somehow now managed to get
VTK to compile (via brew) cause when I try to
brew install it, brew tells me it is already installed,
so that won't bother me anymore.

As to Open source, Mac, Linux I agree with you but
without wanting to expand the discussion I just want
point out that some projects work better than others
(not refering to or trying to  sneak in a derogatory
comment for PCL) and some languages / build system
are better that other in that respect.

I appreciate your comment about implementing from scratch,
well the thing I'm after is not really implemented in
PCL so I would be doing some scratch building anyway
and the thing is so small that I'm pretty sure it would
be half done by now if I had not decided to use PCL
as a reference.

But I've not totally given up on PCL yet. And I hope
you have not given up an me, I appreciate all the
help and even backfire like Rafu's mail.

Once again I'm sorry if I offended anyone and I thank
you all for the help I've received. And like I said
PCL looks awesome and promising, I wouldn't be here
writing long emails that no-one will read and
everyone ignores if I thought otherwise.

One More Thing (tm): Rafu you wrote: "a matter of how
we deal with this as a community and work together
to solve these problems that matters" I of course
agree with that but I don't think either of scored
big time in this discussion, a simple attempt to point
out that my opinion that PCL would be better off
without mandatory VTK dependency turned into the
beginnings of a flame exchange.

cheers Kusti



On 13/06/2013 18:17, "Radu B. Rusu" <[hidden email]> wrote:

Kustaa,

Your comments about VTK are definitely not appreciated. I can see where
you're coming from, perhaps you had bad
experiences in the past with VTK, but still. Our colleagues from Kitware
worked hard to give us a comprehensive set of
_open source_ visualization libraries. If you don't like it, please don't
use it. Would you rather they wouldn't have
open sourced it? I sure as hell wouldn't.

If you look around carefully, you'll notice the following problems in
your reasoning:

 *  PCL (and VTK, and Boost, and others) are generic multi-library
projects, that can be compiled conditionally, based
on what library or module you would want to use from them. If you don't
want to use VTK, simply tell PCL that you'd like
to compile its modules without VTK. You'll drop the pcl_visualization
library as well as some converter modules in
pcl_io, but that's about it.

 * the errors that you posted regarding the GitHub master branch of PCL
are easily fixable and pertain to the
pcl_people library/module. Simply disable it for now, and contact the
respective developers to fix it, or submit a fix
yourself. It's an open community, open platform, open access, and the
code that you're compiling is bleeding edge
master/trunk.

When it comes to open source 3rd party libraries and Mac OS, we will
always have issues, as Apple is not built around
open source communities, and you'll always find more Linux developers for
a project like ours than anything else. It's
all a matter of how we deal with this as a community and work together to
solve these problems that matters. Rants are
great, but they should be followed with "oh, and here's the patch that
fixes this...". Otherwise they're just long
e-mails that most people, as Alex mentioned it, tend to ignore.

Good luck reimplementing from scratch the algorithms that you need.
Sounds like a great way to spend your time :)
(http://www.openperception.org/wp-content/uploads/2012/06/development_time
line.png). I'm still hoping that you'll
reconsider -- at least you've gotten awesome support on PCL mailing lists
- so we must be doing something right.

Cheers,
Radu.
--
http://openperception.org

On 06/13/2013 02:37 AM, Kustaa Nyholm wrote:
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

http://www.pcl-users.org/Successful-PCL-Build-from-Source-on-Mac-OS-X-in
cl
uding-Kinfu-td4022018.html


Cheers,
Radu.
--
http://openperception.org

On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
Hi,

having had a frustrating two days trying to install PCL on my
own I decided to seek for help...

I tried the binaries from here:

http://www.pointclouds.org/downloads/

but they did not work, I've already forgotten what's the issue,
might have been that I was unable to install VTK...
IIRC I could get it to compile by installing a bunch of
stuff via MacPorts but then a simple
C program with just main() with out calling anything
in PCL fails to load because it cannot find VTK...
which is kind...ermh annoying as I have no need for
VTK...to me it seems that strictly 'point cloud only'
library without dependencies on libusb, OpenNI
and VTK would make sense, I could do without boost too,
though eigen seem like a good idea...but I digress.

Anyway, I'm a homebrew user so eventually I just
delete everything related to macports and PCL
and started from scratch with these instructions:

http://www.pointclouds.org/documentation/tutorials/installing_homebrew.
ph
p

This went rather well once I discovered the
'brew tap homebrew/science' to get the dependencies
to install as per instructions, which might be a
handy tip for people like me who
are not so up to speed with all things homebrew.

However at the end this failed because the tar file
the brew expects for PCL has move. Little bit of googling
enabled me to find the 1.6.0 tar file and hacking
the pcl.rb file allowed the download to succeed and
compile begun. BTW is there an up to date .rb file
somewhere?

In the end that compilation failed at 8% mark with
mysterious error

make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
make: *** [all] Error 2


Manually compiling PCL revealed that this related to
some or other 'at' symbol not being found which after
a little googling seems to be a problem with Apple clang.

I was not prepared to go back to gcc (supposing it
was available for Mountain Lion and latest X-code)
and after googling that the issue was supposed to
be fixed about a year ago I tried to compile from
the trunk with:

brew install pcl --HEAD

this goes quite a long way but eventually fails
with the mysterious Error 2:

dyld: DYLD_ environment variables being ignored because main executable
(/usr/bin/sudo) is setuid or setgid
==> Checking out http://svn.pointclouds.org/pcl/trunk
==> mkdir build
==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
==> make install
[ 98%] Built target test_registration
Linking CXX shared library ../lib/libpcl_recognition.dylib
brew: superenv removed: -Wno-invalid-offsetof
[ 98%] Built target pcl_recognition
make: *** [all] Error 2



At this point I decided to seek some help, especially
as I saw a couple notes that claimed that this
install from source without a hitch on Mountain Lion.

So is there an up to date instruction for doing this somewhere
or can someone please give me hand to make this happen?

br Kusti




This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in
this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: <a href="tel:%2B358%2020%207795%20572" value="+358207795572" target="_blank">+358 20 7795 572 (direct)
Fax: <a href="tel:%2B358%2020%207795%20676" value="+358207795676" target="_blank">+358 20 7795 676
GSM: <a href="tel:%2B358%2040%20580%205193" value="+358405805193" target="_blank">+358 40 580 5193
e-mail: [hidden email]







This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: <a href="tel:%2B358%2020%207795%20572" value="+358207795572" target="_blank">+358 20 7795 572 (direct)
Fax: <a href="tel:%2B358%2020%207795%20676" value="+358207795676" target="_blank">+358 20 7795 676
GSM: <a href="tel:%2B358%2040%20580%205193" value="+358405805193" target="_blank">+358 40 580 5193
e-mail: [hidden email]







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users

_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

Kustaa Nyholm
Hi Lv,



you did not mention which Mac OS version you are running.

Once the correct 'Formula' was pointed out to me installing
everything with 'homebrew' went easily according to the
plan. Of course YMMV, but I would just install homebrew
and try the formula provided by fran6co.

Install homebrew according to this page:


Then run the brew doctor to and obey the instructions it gives to you
until brew doctor says you are ready to brew:

brew doctor


Then 'tap' to fran6co github repo:

brew tap fran6co/cv


and then install with with

brew install --HEAD pcl



or if you have tapped  homebrew/science

brew install fran6co/cv/pcl


Make sure you obey brew doctor instructions and
if you have remnants of previous installation attempts you should
try to remove them.

At the end of an almost complete
installation phase it sometimes fails because brew will not
overwrite some files created by your previous attempts.

When that happens brew will name the files in questions
so you should be able to manually delete them and
try to install again.

This worked for me like a charm. Thanks for PCL and team.

br Kusti




From:  Lv Zhaoyang <[hidden email]>
Reply-To:  "Point Cloud Library (PCL) users" <[hidden email]>
Date:  Fri, 14 Jun 2013 13:34:43 +0300
To:  "Point Cloud Library (PCL) users" <[hidden email]>
Subject:  Re: [PCL-users] PCL on Mac OS X Mountain Lion


Hi Alex,
Thank you very much for your suggestion. I'll make a summary of my problems occurred. But before that, I want to uninstall the libs and try them from beginning. Do you have ideas to do that?

Now my libs have been massed up. I need some suggestions how to fix it.

Cheers,
Lv Zhaoyang


On 14 Jun 2013, at 11:26, Alexandru-Eugen Ichim <[hidden email]> wrote:


Hi Lv,
1. That is not related to PCL. Especially that you are not a C++ expert, you should not try to combine libraries and package managers on MacOS. They are not made to collaborate with each other and you will run into trouble. I only use MacPorts, but HomeBrew gives very good results too.

2. You should make sure that you create .app bundles from CMake. There are discussions on how to do this on our mailing lists: simply do ADD_EXECUTABLE (my_exec MACOSX_BUNDLE file.cpp) or PCL_ADD_EXECUTABLE_OPT_BUNDLE (...).

3. Why do you need to do that? Open up a ticket on Github presenting your situation and the errors you get, and someone will take care of it.

Cheers,
Alex



On Fri, Jun 14, 2013 at 1:16 AM, Lv Zhaoyang <[hidden email]> wrote:

Hi Radu,
I'm also a Mac user, and getting PCL just in the last week. I also had a terrible experience with the Mac PCL version, and now I just turned to Ubuntu on my virtual machine. On ubuntu everything works fine now. Here are some problems I confronted:

1. After I track the problems and google all the solutions. One problem is with the boost library. You can see it here. http://stackoverflow.com/questions/17054800/errors-in-boost-installed-from-both-macport-and-brew
No one respond me yet. So I turned to Linux finally. But the performance is affected on virtual machine. I am still glad to solve it on my mac.

2. Vtk on my mac also has problem. I tried the visualisation tutorial, but no interface appears.

3. I also disable two parts in PCL (I think it's the people_detection and outofcore). The PCL version I use it from github. In Linux, I don't need to disable anything.  

That's all the problem I finally got. If I solved these, there might be some new problems.  In general, it's not as easy as the Linux one. I spent 4 days configuring PCL on Mac. Then I turned to Linux, I solved everything in one day. The installation tutorial in Mac seems very old and not consistent. I tried at least all the three, macport, brew and the dmg file. That might be the reason I get conflicts in libs. Hope you can update it.

I'm not a experienced programmer, still a student, a rookie in C++. We hope everything can get working quite easily and program, no need learn compiler and system. Of course, you are getting better and better. Hope this feedback can be useful. And I'm still waiting for my solutions.

Best,
Lv Zhaoyang

On 13 Jun 2013, at 22:26, "Radu B. Rusu" <[hidden email]> wrote:


Kustaa,

Thanks for your e-mail. I did not take your comments about VTK to be derogatory, just simply stating that ranting with respect to "open source software" should have a slightly different tone than our daily, more usual, rants. Although as an user one is still "investing" time in figuring out an open source library, I get a bit more edgy at times about these issues, and hence I tend to remind that person that there are people behind that library, working hard at times to give back and provide open systems so that others can enjoy. Can they do better in certain areas? Of course! That's where they need help...

You won't find too many flame exchanges on our mailing lists, other than the usual SVN vs GIT, which we solved (Jochen won the argument through persistence :D), and this wouldn't have turned into one either. VTK is a great library with its set of faults. Kitware has now been generously granted a large contract/grant to revitalize VTK and build the next generation of scientific visualization libraries as part of VTK6. I've had my share of suggestions for how that should look like, and I'm sure they would appreciate to hear even more.

You are right about PCL 1.6 not being MacOS friendly, when it comes to visualization. We tried our best to provide binary DMGs, but due to a much smaller Mac OS PCL user community, we have not received enough feedback in order to fix all issues in time. We need your help (and others' too) about making that clear on our web pages. We're also hoping to kick out PCL 1.7 soon with better Mac OS support -- most if not all things have been fixed since 1.6 came out. We'll need to patch pcl_people now as well.

PS. I'm happy that fran6co managed to help. That's where the power of an open source community resides.

Cheers,
Radu.
--

On 06/13/2013 09:42 AM, Kustaa Nyholm wrote:
Hi Radu,

I'm sorry I offended you, that was not my intention.

I'm glad to hear that the pcl_people_library/module can be easily
disabled, I'm going to try that next. Thanks for helping
and pointing out the solution. And thanks for Alex
too for his help.

I may even contact the authors of that module or
supply a patch, if I can come up with one.

BTW it was not my intention to use the bleeding edge,
this was an attempt because of an other compile problem
with the stable version, which I pressumed would at
least compile without a problem.

----


Everyone not really interested in this should now touch
that dial and tune out as this is likely to run to
some number of lines as I'm going to discuss some
some of Radu's other points.

I was not (trying to be) derogatory about VTK, my point
was simply that it is not what everyone needs or can use,
it is not a panacea. I sure appreciate their efforts
and applaud that it was open sourced. And for some
tasks it works admirably I'm sure, for the tasks we
tried it some years ago it did not and we coded from
scratch to get the speed and features we needed.
Having said that I truly appreciate the years of
hard word, craftsmanship and resource that has gone in
to it.

But making it mandatory dependency on a general purpose
triangulation library does seem to go against the grain.

You say that "don't want to use VTK, simply tell PCL
to compile its modules without VTK", well I can't
get PCL to compile in the first place, which was my
main problem. The binaries I found for Mac OS X
did not work because they insisted on VTK even though
my code (empty main()) did not use them. My code
compiled and linked but failed to load. The PCL
webpage says that VTK is mandatory. When I checked
the CMake script I did not spot how to disable
VTK dependency, but then I'm new to CMake.

So excuse me when I was mistaken.

But apparently I've somehow now managed to get
VTK to compile (via brew) cause when I try to
brew install it, brew tells me it is already installed,
so that won't bother me anymore.

As to Open source, Mac, Linux I agree with you but
without wanting to expand the discussion I just want
point out that some projects work better than others
(not refering to or trying to  sneak in a derogatory
comment for PCL) and some languages / build system
are better that other in that respect.

I appreciate your comment about implementing from scratch,
well the thing I'm after is not really implemented in
PCL so I would be doing some scratch building anyway
and the thing is so small that I'm pretty sure it would
be half done by now if I had not decided to use PCL
as a reference.

But I've not totally given up on PCL yet. And I hope
you have not given up an me, I appreciate all the
help and even backfire like Rafu's mail.

Once again I'm sorry if I offended anyone and I thank
you all for the help I've received. And like I said
PCL looks awesome and promising, I wouldn't be here
writing long emails that no-one will read and
everyone ignores if I thought otherwise.

One More Thing (tm): Rafu you wrote: "a matter of how
we deal with this as a community and work together
to solve these problems that matters" I of course
agree with that but I don't think either of scored
big time in this discussion, a simple attempt to point
out that my opinion that PCL would be better off
without mandatory VTK dependency turned into the
beginnings of a flame exchange.

cheers Kusti



On 13/06/2013 18:17, "Radu B. Rusu" <[hidden email]> wrote:

Kustaa,

Your comments about VTK are definitely not appreciated. I can see where
you're coming from, perhaps you had bad
experiences in the past with VTK, but still. Our colleagues from Kitware
worked hard to give us a comprehensive set of
_open source_ visualization libraries. If you don't like it, please don't
use it. Would you rather they wouldn't have
open sourced it? I sure as hell wouldn't.

If you look around carefully, you'll notice the following problems in
your reasoning:

  *  PCL (and VTK, and Boost, and others) are generic multi-library
projects, that can be compiled conditionally, based
on what library or module you would want to use from them. If you don't
want to use VTK, simply tell PCL that you'd like
to compile its modules without VTK. You'll drop the pcl_visualization
library as well as some converter modules in
pcl_io, but that's about it.

  * the errors that you posted regarding the GitHub master branch of PCL
are easily fixable and pertain to the
pcl_people library/module. Simply disable it for now, and contact the
respective developers to fix it, or submit a fix
yourself. It's an open community, open platform, open access, and the
code that you're compiling is bleeding edge
master/trunk.

When it comes to open source 3rd party libraries and Mac OS, we will
always have issues, as Apple is not built around
open source communities, and you'll always find more Linux developers for
a project like ours than anything else. It's
all a matter of how we deal with this as a community and work together to
solve these problems that matters. Rants are
great, but they should be followed with "oh, and here's the patch that
fixes this...". Otherwise they're just long
e-mails that most people, as Alex mentioned it, tend to ignore.

Good luck reimplementing from scratch the algorithms that you need.
Sounds like a great way to spend your time :)
line.png). I'm still hoping that you'll
reconsider -- at least you've gotten awesome support on PCL mailing lists
- so we must be doing something right.

Cheers,
Radu.
--

On 06/13/2013 02:37 AM, Kustaa Nyholm wrote:
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

cl
uding-Kinfu-td4022018.html


Cheers,
Radu.
--

On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
Hi,

having had a frustrating two days trying to install PCL on my
own I decided to seek for help...

I tried the binaries from here:


but they did not work, I've already forgotten what's the issue,
might have been that I was unable to install VTK...
IIRC I could get it to compile by installing a bunch of
stuff via MacPorts but then a simple
C program with just main() with out calling anything
in PCL fails to load because it cannot find VTK...
which is kind...ermh annoying as I have no need for
VTK...to me it seems that strictly 'point cloud only'
library without dependencies on libusb, OpenNI
and VTK would make sense, I could do without boost too,
though eigen seem like a good idea...but I digress.

Anyway, I'm a homebrew user so eventually I just
delete everything related to macports and PCL
and started from scratch with these instructions:

ph
p

This went rather well once I discovered the
'brew tap homebrew/science' to get the dependencies
to install as per instructions, which might be a
handy tip for people like me who
are not so up to speed with all things homebrew.

However at the end this failed because the tar file
the brew expects for PCL has move. Little bit of googling
enabled me to find the 1.6.0 tar file and hacking
the pcl.rb file allowed the download to succeed and
compile begun. BTW is there an up to date .rb file
somewhere?

In the end that compilation failed at 8% mark with
mysterious error

make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
make: *** [all] Error 2


Manually compiling PCL revealed that this related to
some or other 'at' symbol not being found which after
a little googling seems to be a problem with Apple clang.

I was not prepared to go back to gcc (supposing it
was available for Mountain Lion and latest X-code)
and after googling that the issue was supposed to
be fixed about a year ago I tried to compile from
the trunk with:

brew install pcl --HEAD

this goes quite a long way but eventually fails
with the mysterious Error 2:

dyld: DYLD_ environment variables being ignored because main executable
(/usr/bin/sudo) is setuid or setgid
==> mkdir build
==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
==> make install
[ 98%] Built target test_registration
Linking CXX shared library ../lib/libpcl_recognition.dylib
brew: superenv removed: -Wno-invalid-offsetof
[ 98%] Built target pcl_recognition
make: *** [all] Error 2



At this point I decided to seek some help, especially
as I saw a couple notes that claimed that this
install from source without a hitch on Mountain Lion.

So is there an up to date instruction for doing this somewhere
or can someone please give me hand to make this happen?

br Kusti




This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in
this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________








--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 <tel:%2B358%2020%207795%20572> (direct)
Fax: +358 20 7795 676 <tel:%2B358%2020%207795%20676>
GSM: +358 40 580 5193 <tel:%2B358%2040%20580%205193>







This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________








--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 <tel:%2B358%2020%207795%20572> (direct)
Fax: +358 20 7795 676 <tel:%2B358%2020%207795%20676>
GSM: +358 40 580 5193 <tel:%2B358%2040%20580%205193>







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________



_______________________________________________








_______________________________________________






_______________________________________________






_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
tog
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

tog
Thanks
This worked like a charm. But it does not seem to build kinfu. What if I want to build it ?

Regards
Guillaume


On Fri, Jun 14, 2013 at 1:22 PM, Kustaa Nyholm <[hidden email]> wrote:
Hi Lv,



you did not mention which Mac OS version you are running.

Once the correct 'Formula' was pointed out to me installing
everything with 'homebrew' went easily according to the
plan. Of course YMMV, but I would just install homebrew
and try the formula provided by fran6co.

Install homebrew according to this page:


Then run the brew doctor to and obey the instructions it gives to you
until brew doctor says you are ready to brew:

brew doctor


Then 'tap' to fran6co github repo:

brew tap fran6co/cv


and then install with with

brew install --HEAD pcl



or if you have tapped  homebrew/science

brew install fran6co/cv/pcl


Make sure you obey brew doctor instructions and
if you have remnants of previous installation attempts you should
try to remove them.

At the end of an almost complete
installation phase it sometimes fails because brew will not
overwrite some files created by your previous attempts.

When that happens brew will name the files in questions
so you should be able to manually delete them and
try to install again.

This worked for me like a charm. Thanks for PCL and team.

br Kusti




From:  Lv Zhaoyang <[hidden email]>
Reply-To:  "Point Cloud Library (PCL) users" <[hidden email]>
Date:  Fri, 14 Jun 2013 13:34:43 +0300
To:  "Point Cloud Library (PCL) users" <[hidden email]>
Subject:  Re: [PCL-users] PCL on Mac OS X Mountain Lion


Hi Alex,
Thank you very much for your suggestion. I'll make a summary of my problems occurred. But before that, I want to uninstall the libs and try them from beginning. Do you have ideas to do that?

Now my libs have been massed up. I need some suggestions how to fix it.

Cheers,
Lv Zhaoyang


On 14 Jun 2013, at 11:26, Alexandru-Eugen Ichim <[hidden email]> wrote:


Hi Lv,
1. That is not related to PCL. Especially that you are not a C++ expert, you should not try to combine libraries and package managers on MacOS. They are not made to collaborate with each other and you will run into trouble. I only use MacPorts, but HomeBrew gives very good results too.

2. You should make sure that you create .app bundles from CMake. There are discussions on how to do this on our mailing lists: simply do ADD_EXECUTABLE (my_exec MACOSX_BUNDLE file.cpp) or PCL_ADD_EXECUTABLE_OPT_BUNDLE (...).

3. Why do you need to do that? Open up a ticket on Github presenting your situation and the errors you get, and someone will take care of it.

Cheers,
Alex



On Fri, Jun 14, 2013 at 1:16 AM, Lv Zhaoyang <[hidden email]> wrote:

Hi Radu,
I'm also a Mac user, and getting PCL just in the last week. I also had a terrible experience with the Mac PCL version, and now I just turned to Ubuntu on my virtual machine. On ubuntu everything works fine now. Here are some problems I confronted:

1. After I track the problems and google all the solutions. One problem is with the boost library. You can see it here. http://stackoverflow.com/questions/17054800/errors-in-boost-installed-from-both-macport-and-brew
No one respond me yet. So I turned to Linux finally. But the performance is affected on virtual machine. I am still glad to solve it on my mac.

2. Vtk on my mac also has problem. I tried the visualisation tutorial, but no interface appears.

3. I also disable two parts in PCL (I think it's the people_detection and outofcore). The PCL version I use it from github. In Linux, I don't need to disable anything.  

That's all the problem I finally got. If I solved these, there might be some new problems.  In general, it's not as easy as the Linux one. I spent 4 days configuring PCL on Mac. Then I turned to Linux, I solved everything in one day. The installation tutorial in Mac seems very old and not consistent. I tried at least all the three, macport, brew and the dmg file. That might be the reason I get conflicts in libs. Hope you can update it.

I'm not a experienced programmer, still a student, a rookie in C++. We hope everything can get working quite easily and program, no need learn compiler and system. Of course, you are getting better and better. Hope this feedback can be useful. And I'm still waiting for my solutions.

Best,
Lv Zhaoyang

On 13 Jun 2013, at 22:26, "Radu B. Rusu" <[hidden email]> wrote:


Kustaa,

Thanks for your e-mail. I did not take your comments about VTK to be derogatory, just simply stating that ranting with respect to "open source software" should have a slightly different tone than our daily, more usual, rants. Although as an user one is still "investing" time in figuring out an open source library, I get a bit more edgy at times about these issues, and hence I tend to remind that person that there are people behind that library, working hard at times to give back and provide open systems so that others can enjoy. Can they do better in certain areas? Of course! That's where they need help...

You won't find too many flame exchanges on our mailing lists, other than the usual SVN vs GIT, which we solved (Jochen won the argument through persistence :D), and this wouldn't have turned into one either. VTK is a great library with its set of faults. Kitware has now been generously granted a large contract/grant to revitalize VTK and build the next generation of scientific visualization libraries as part of VTK6. I've had my share of suggestions for how that should look like, and I'm sure they would appreciate to hear even more.

You are right about PCL 1.6 not being MacOS friendly, when it comes to visualization. We tried our best to provide binary DMGs, but due to a much smaller Mac OS PCL user community, we have not received enough feedback in order to fix all issues in time. We need your help (and others' too) about making that clear on our web pages. We're also hoping to kick out PCL 1.7 soon with better Mac OS support -- most if not all things have been fixed since 1.6 came out. We'll need to patch pcl_people now as well.

PS. I'm happy that fran6co managed to help. That's where the power of an open source community resides.

Cheers,
Radu.
--

On 06/13/2013 09:42 AM, Kustaa Nyholm wrote:
Hi Radu,

I'm sorry I offended you, that was not my intention.

I'm glad to hear that the pcl_people_library/module can be easily
disabled, I'm going to try that next. Thanks for helping
and pointing out the solution. And thanks for Alex
too for his help.

I may even contact the authors of that module or
supply a patch, if I can come up with one.

BTW it was not my intention to use the bleeding edge,
this was an attempt because of an other compile problem
with the stable version, which I pressumed would at
least compile without a problem.

----


Everyone not really interested in this should now touch
that dial and tune out as this is likely to run to
some number of lines as I'm going to discuss some
some of Radu's other points.

I was not (trying to be) derogatory about VTK, my point
was simply that it is not what everyone needs or can use,
it is not a panacea. I sure appreciate their efforts
and applaud that it was open sourced. And for some
tasks it works admirably I'm sure, for the tasks we
tried it some years ago it did not and we coded from
scratch to get the speed and features we needed.
Having said that I truly appreciate the years of
hard word, craftsmanship and resource that has gone in
to it.

But making it mandatory dependency on a general purpose
triangulation library does seem to go against the grain.

You say that "don't want to use VTK, simply tell PCL
to compile its modules without VTK", well I can't
get PCL to compile in the first place, which was my
main problem. The binaries I found for Mac OS X
did not work because they insisted on VTK even though
my code (empty main()) did not use them. My code
compiled and linked but failed to load. The PCL
webpage says that VTK is mandatory. When I checked
the CMake script I did not spot how to disable
VTK dependency, but then I'm new to CMake.

So excuse me when I was mistaken.

But apparently I've somehow now managed to get
VTK to compile (via brew) cause when I try to
brew install it, brew tells me it is already installed,
so that won't bother me anymore.

As to Open source, Mac, Linux I agree with you but
without wanting to expand the discussion I just want
point out that some projects work better than others
(not refering to or trying to  sneak in a derogatory
comment for PCL) and some languages / build system
are better that other in that respect.

I appreciate your comment about implementing from scratch,
well the thing I'm after is not really implemented in
PCL so I would be doing some scratch building anyway
and the thing is so small that I'm pretty sure it would
be half done by now if I had not decided to use PCL
as a reference.

But I've not totally given up on PCL yet. And I hope
you have not given up an me, I appreciate all the
help and even backfire like Rafu's mail.

Once again I'm sorry if I offended anyone and I thank
you all for the help I've received. And like I said
PCL looks awesome and promising, I wouldn't be here
writing long emails that no-one will read and
everyone ignores if I thought otherwise.

One More Thing (tm): Rafu you wrote: "a matter of how
we deal with this as a community and work together
to solve these problems that matters" I of course
agree with that but I don't think either of scored
big time in this discussion, a simple attempt to point
out that my opinion that PCL would be better off
without mandatory VTK dependency turned into the
beginnings of a flame exchange.

cheers Kusti



On 13/06/2013 18:17, "Radu B. Rusu" <[hidden email]> wrote:

Kustaa,

Your comments about VTK are definitely not appreciated. I can see where
you're coming from, perhaps you had bad
experiences in the past with VTK, but still. Our colleagues from Kitware
worked hard to give us a comprehensive set of
_open source_ visualization libraries. If you don't like it, please don't
use it. Would you rather they wouldn't have
open sourced it? I sure as hell wouldn't.

If you look around carefully, you'll notice the following problems in
your reasoning:

  *  PCL (and VTK, and Boost, and others) are generic multi-library
projects, that can be compiled conditionally, based
on what library or module you would want to use from them. If you don't
want to use VTK, simply tell PCL that you'd like
to compile its modules without VTK. You'll drop the pcl_visualization
library as well as some converter modules in
pcl_io, but that's about it.

  * the errors that you posted regarding the GitHub master branch of PCL
are easily fixable and pertain to the
pcl_people library/module. Simply disable it for now, and contact the
respective developers to fix it, or submit a fix
yourself. It's an open community, open platform, open access, and the
code that you're compiling is bleeding edge
master/trunk.

When it comes to open source 3rd party libraries and Mac OS, we will
always have issues, as Apple is not built around
open source communities, and you'll always find more Linux developers for
a project like ours than anything else. It's
all a matter of how we deal with this as a community and work together to
solve these problems that matters. Rants are
great, but they should be followed with "oh, and here's the patch that
fixes this...". Otherwise they're just long
e-mails that most people, as Alex mentioned it, tend to ignore.

Good luck reimplementing from scratch the algorithms that you need.
Sounds like a great way to spend your time :)
line.png). I'm still hoping that you'll
reconsider -- at least you've gotten awesome support on PCL mailing lists
- so we must be doing something right.

Cheers,
Radu.
--

On 06/13/2013 02:37 AM, Kustaa Nyholm wrote:
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

cl
uding-Kinfu-td4022018.html


Cheers,
Radu.
--

On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
Hi,

having had a frustrating two days trying to install PCL on my
own I decided to seek for help...

I tried the binaries from here:


but they did not work, I've already forgotten what's the issue,
might have been that I was unable to install VTK...
IIRC I could get it to compile by installing a bunch of
stuff via MacPorts but then a simple
C program with just main() with out calling anything
in PCL fails to load because it cannot find VTK...
which is kind...ermh annoying as I have no need for
VTK...to me it seems that strictly 'point cloud only'
library without dependencies on libusb, OpenNI
and VTK would make sense, I could do without boost too,
though eigen seem like a good idea...but I digress.

Anyway, I'm a homebrew user so eventually I just
delete everything related to macports and PCL
and started from scratch with these instructions:

ph
p

This went rather well once I discovered the
'brew tap homebrew/science' to get the dependencies
to install as per instructions, which might be a
handy tip for people like me who
are not so up to speed with all things homebrew.

However at the end this failed because the tar file
the brew expects for PCL has move. Little bit of googling
enabled me to find the 1.6.0 tar file and hacking
the pcl.rb file allowed the download to succeed and
compile begun. BTW is there an up to date .rb file
somewhere?

In the end that compilation failed at 8% mark with
mysterious error

make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
make: *** [all] Error 2


Manually compiling PCL revealed that this related to
some or other 'at' symbol not being found which after
a little googling seems to be a problem with Apple clang.

I was not prepared to go back to gcc (supposing it
was available for Mountain Lion and latest X-code)
and after googling that the issue was supposed to
be fixed about a year ago I tried to compile from
the trunk with:

brew install pcl --HEAD

this goes quite a long way but eventually fails
with the mysterious Error 2:

dyld: DYLD_ environment variables being ignored because main executable
(/usr/bin/sudo) is setuid or setgid
==> mkdir build
==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
==> make install
[ 98%] Built target test_registration
Linking CXX shared library ../lib/libpcl_recognition.dylib
brew: superenv removed: -Wno-invalid-offsetof
[ 98%] Built target pcl_recognition
make: *** [all] Error 2



At this point I decided to seek some help, especially
as I saw a couple notes that claimed that this
install from source without a hitch on Mountain Lion.

So is there an up to date instruction for doing this somewhere
or can someone please give me hand to make this happen?

br Kusti




This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in
this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________








--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 <tel:%2B358%2020%207795%20572> (direct)
Fax: +358 20 7795 676 <tel:%2B358%2020%207795%20676>
GSM: +358 40 580 5193 <tel:%2B358%2040%20580%205193>







This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________








--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 <tel:%2B358%2020%207795%20572> (direct)
Fax: +358 20 7795 676 <tel:%2B358%2020%207795%20676>
GSM: +358 40 580 5193 <tel:%2B358%2040%20580%205193>







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________

_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
PGP KeyID: 2048R/EA31CFC9  subkeys.pgp.net

_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

fran6co
You need to enable the openni depency. If you want to build the full package (couldn't get the app_cloud_composer to compile yet) you have to install it with:

brew install --HEAD pcl --with-openni --with-qt

You should get kinfu and everything else.

On Saturday, July 27, 2013 at 10:32 AM, tog wrote:

Thanks
This worked like a charm. But it does not seem to build kinfu. What if I want to build it ?

Regards
Guillaume


On Fri, Jun 14, 2013 at 1:22 PM, Kustaa Nyholm <[hidden email]> wrote:
Hi Lv,



you did not mention which Mac OS version you are running.

Once the correct 'Formula' was pointed out to me installing
everything with 'homebrew' went easily according to the
plan. Of course YMMV, but I would just install homebrew
and try the formula provided by fran6co.

Install homebrew according to this page:


Then run the brew doctor to and obey the instructions it gives to you
until brew doctor says you are ready to brew:

brew doctor


Then 'tap' to fran6co github repo:

brew tap fran6co/cv


and then install with with

brew install --HEAD pcl



or if you have tapped  homebrew/science

brew install fran6co/cv/pcl


Make sure you obey brew doctor instructions and
if you have remnants of previous installation attempts you should
try to remove them.

At the end of an almost complete
installation phase it sometimes fails because brew will not
overwrite some files created by your previous attempts.

When that happens brew will name the files in questions
so you should be able to manually delete them and
try to install again.

This worked for me like a charm. Thanks for PCL and team.

br Kusti




From:  Lv Zhaoyang <[hidden email]>
Reply-To:  "Point Cloud Library (PCL) users" <[hidden email]>
Date:  Fri, 14 Jun 2013 13:34:43 +0300
To:  "Point Cloud Library (PCL) users" <[hidden email]>
Subject:  Re: [PCL-users] PCL on Mac OS X Mountain Lion


Hi Alex,
Thank you very much for your suggestion. I'll make a summary of my problems occurred. But before that, I want to uninstall the libs and try them from beginning. Do you have ideas to do that?

Now my libs have been massed up. I need some suggestions how to fix it.

Cheers,
Lv Zhaoyang


On 14 Jun 2013, at 11:26, Alexandru-Eugen Ichim <[hidden email]> wrote:


Hi Lv,
1. That is not related to PCL. Especially that you are not a C++ expert, you should not try to combine libraries and package managers on MacOS. They are not made to collaborate with each other and you will run into trouble. I only use MacPorts, but HomeBrew gives very good results too.

2. You should make sure that you create .app bundles from CMake. There are discussions on how to do this on our mailing lists: simply do ADD_EXECUTABLE (my_exec MACOSX_BUNDLE file.cpp) or PCL_ADD_EXECUTABLE_OPT_BUNDLE (...).

3. Why do you need to do that? Open up a ticket on Github presenting your situation and the errors you get, and someone will take care of it.

Cheers,
Alex



On Fri, Jun 14, 2013 at 1:16 AM, Lv Zhaoyang <[hidden email]> wrote:

Hi Radu,
I'm also a Mac user, and getting PCL just in the last week. I also had a terrible experience with the Mac PCL version, and now I just turned to Ubuntu on my virtual machine. On ubuntu everything works fine now. Here are some problems I confronted:

1. After I track the problems and google all the solutions. One problem is with the boost library. You can see it here. http://stackoverflow.com/questions/17054800/errors-in-boost-installed-from-both-macport-and-brew
No one respond me yet. So I turned to Linux finally. But the performance is affected on virtual machine. I am still glad to solve it on my mac.

2. Vtk on my mac also has problem. I tried the visualisation tutorial, but no interface appears.

3. I also disable two parts in PCL (I think it's the people_detection and outofcore). The PCL version I use it from github. In Linux, I don't need to disable anything.  

That's all the problem I finally got. If I solved these, there might be some new problems.  In general, it's not as easy as the Linux one. I spent 4 days configuring PCL on Mac. Then I turned to Linux, I solved everything in one day. The installation tutorial in Mac seems very old and not consistent. I tried at least all the three, macport, brew and the dmg file. That might be the reason I get conflicts in libs. Hope you can update it.

I'm not a experienced programmer, still a student, a rookie in C++. We hope everything can get working quite easily and program, no need learn compiler and system. Of course, you are getting better and better. Hope this feedback can be useful. And I'm still waiting for my solutions.

Best,
Lv Zhaoyang

On 13 Jun 2013, at 22:26, "Radu B. Rusu" <[hidden email]> wrote:


Kustaa,

Thanks for your e-mail. I did not take your comments about VTK to be derogatory, just simply stating that ranting with respect to "open source software" should have a slightly different tone than our daily, more usual, rants. Although as an user one is still "investing" time in figuring out an open source library, I get a bit more edgy at times about these issues, and hence I tend to remind that person that there are people behind that library, working hard at times to give back and provide open systems so that others can enjoy. Can they do better in certain areas? Of course! That's where they need help...

You won't find too many flame exchanges on our mailing lists, other than the usual SVN vs GIT, which we solved (Jochen won the argument through persistence :D), and this wouldn't have turned into one either. VTK is a great library with its set of faults. Kitware has now been generously granted a large contract/grant to revitalize VTK and build the next generation of scientific visualization libraries as part of VTK6. I've had my share of suggestions for how that should look like, and I'm sure they would appreciate to hear even more.

You are right about PCL 1.6 not being MacOS friendly, when it comes to visualization. We tried our best to provide binary DMGs, but due to a much smaller Mac OS PCL user community, we have not received enough feedback in order to fix all issues in time. We need your help (and others' too) about making that clear on our web pages. We're also hoping to kick out PCL 1.7 soon with better Mac OS support -- most if not all things have been fixed since 1.6 came out. We'll need to patch pcl_people now as well.

PS. I'm happy that fran6co managed to help. That's where the power of an open source community resides.

Cheers,
Radu.
--

On 06/13/2013 09:42 AM, Kustaa Nyholm wrote:
Hi Radu,

I'm sorry I offended you, that was not my intention.

I'm glad to hear that the pcl_people_library/module can be easily
disabled, I'm going to try that next. Thanks for helping
and pointing out the solution. And thanks for Alex
too for his help.

I may even contact the authors of that module or
supply a patch, if I can come up with one.

BTW it was not my intention to use the bleeding edge,
this was an attempt because of an other compile problem
with the stable version, which I pressumed would at
least compile without a problem.

----


Everyone not really interested in this should now touch
that dial and tune out as this is likely to run to
some number of lines as I'm going to discuss some
some of Radu's other points.

I was not (trying to be) derogatory about VTK, my point
was simply that it is not what everyone needs or can use,
it is not a panacea. I sure appreciate their efforts
and applaud that it was open sourced. And for some
tasks it works admirably I'm sure, for the tasks we
tried it some years ago it did not and we coded from
scratch to get the speed and features we needed.
Having said that I truly appreciate the years of
hard word, craftsmanship and resource that has gone in
to it.

But making it mandatory dependency on a general purpose
triangulation library does seem to go against the grain.

You say that "don't want to use VTK, simply tell PCL
to compile its modules without VTK", well I can't
get PCL to compile in the first place, which was my
main problem. The binaries I found for Mac OS X
did not work because they insisted on VTK even though
my code (empty main()) did not use them. My code
compiled and linked but failed to load. The PCL
webpage says that VTK is mandatory. When I checked
the CMake script I did not spot how to disable
VTK dependency, but then I'm new to CMake.

So excuse me when I was mistaken.

But apparently I've somehow now managed to get
VTK to compile (via brew) cause when I try to
brew install it, brew tells me it is already installed,
so that won't bother me anymore.

As to Open source, Mac, Linux I agree with you but
without wanting to expand the discussion I just want
point out that some projects work better than others
(not refering to or trying to  sneak in a derogatory
comment for PCL) and some languages / build system
are better that other in that respect.

I appreciate your comment about implementing from scratch,
well the thing I'm after is not really implemented in
PCL so I would be doing some scratch building anyway
and the thing is so small that I'm pretty sure it would
be half done by now if I had not decided to use PCL
as a reference.

But I've not totally given up on PCL yet. And I hope
you have not given up an me, I appreciate all the
help and even backfire like Rafu's mail.

Once again I'm sorry if I offended anyone and I thank
you all for the help I've received. And like I said
PCL looks awesome and promising, I wouldn't be here
writing long emails that no-one will read and
everyone ignores if I thought otherwise.

One More Thing (tm): Rafu you wrote: "a matter of how
we deal with this as a community and work together
to solve these problems that matters" I of course
agree with that but I don't think either of scored
big time in this discussion, a simple attempt to point
out that my opinion that PCL would be better off
without mandatory VTK dependency turned into the
beginnings of a flame exchange.

cheers Kusti



On 13/06/2013 18:17, "Radu B. Rusu" <[hidden email]> wrote:

Kustaa,

Your comments about VTK are definitely not appreciated. I can see where
you're coming from, perhaps you had bad
experiences in the past with VTK, but still. Our colleagues from Kitware
worked hard to give us a comprehensive set of
_open source_ visualization libraries. If you don't like it, please don't
use it. Would you rather they wouldn't have
open sourced it? I sure as hell wouldn't.

If you look around carefully, you'll notice the following problems in
your reasoning:

  *  PCL (and VTK, and Boost, and others) are generic multi-library
projects, that can be compiled conditionally, based
on what library or module you would want to use from them. If you don't
want to use VTK, simply tell PCL that you'd like
to compile its modules without VTK. You'll drop the pcl_visualization
library as well as some converter modules in
pcl_io, but that's about it.

  * the errors that you posted regarding the GitHub master branch of PCL
are easily fixable and pertain to the
pcl_people library/module. Simply disable it for now, and contact the
respective developers to fix it, or submit a fix
yourself. It's an open community, open platform, open access, and the
code that you're compiling is bleeding edge
master/trunk.

When it comes to open source 3rd party libraries and Mac OS, we will
always have issues, as Apple is not built around
open source communities, and you'll always find more Linux developers for
a project like ours than anything else. It's
all a matter of how we deal with this as a community and work together to
solve these problems that matters. Rants are
great, but they should be followed with "oh, and here's the patch that
fixes this...". Otherwise they're just long
e-mails that most people, as Alex mentioned it, tend to ignore.

Good luck reimplementing from scratch the algorithms that you need.
Sounds like a great way to spend your time :)
line.png). I'm still hoping that you'll
reconsider -- at least you've gotten awesome support on PCL mailing lists
- so we must be doing something right.

Cheers,
Radu.
--

On 06/13/2013 02:37 AM, Kustaa Nyholm wrote:
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

cl
uding-Kinfu-td4022018.html


Cheers,
Radu.
--

On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
Hi,

having had a frustrating two days trying to install PCL on my
own I decided to seek for help...

I tried the binaries from here:


but they did not work, I've already forgotten what's the issue,
might have been that I was unable to install VTK...
IIRC I could get it to compile by installing a bunch of
stuff via MacPorts but then a simple
C program with just main() with out calling anything
in PCL fails to load because it cannot find VTK...
which is kind...ermh annoying as I have no need for
VTK...to me it seems that strictly 'point cloud only'
library without dependencies on libusb, OpenNI
and VTK would make sense, I could do without boost too,
though eigen seem like a good idea...but I digress.

Anyway, I'm a homebrew user so eventually I just
delete everything related to macports and PCL
and started from scratch with these instructions:

ph
p

This went rather well once I discovered the
'brew tap homebrew/science' to get the dependencies
to install as per instructions, which might be a
handy tip for people like me who
are not so up to speed with all things homebrew.

However at the end this failed because the tar file
the brew expects for PCL has move. Little bit of googling
enabled me to find the 1.6.0 tar file and hacking
the pcl.rb file allowed the download to succeed and
compile begun. BTW is there an up to date .rb file
somewhere?

In the end that compilation failed at 8% mark with
mysterious error

make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
make: *** [all] Error 2


Manually compiling PCL revealed that this related to
some or other 'at' symbol not being found which after
a little googling seems to be a problem with Apple clang.

I was not prepared to go back to gcc (supposing it
was available for Mountain Lion and latest X-code)
and after googling that the issue was supposed to
be fixed about a year ago I tried to compile from
the trunk with:

brew install pcl --HEAD

this goes quite a long way but eventually fails
with the mysterious Error 2:

dyld: DYLD_ environment variables being ignored because main executable
(/usr/bin/sudo) is setuid or setgid
==> mkdir build
==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
==> make install
[ 98%] Built target test_registration
Linking CXX shared library ../lib/libpcl_recognition.dylib
brew: superenv removed: -Wno-invalid-offsetof
[ 98%] Built target pcl_recognition
make: *** [all] Error 2



At this point I decided to seek some help, especially
as I saw a couple notes that claimed that this
install from source without a hitch on Mountain Lion.

So is there an up to date instruction for doing this somewhere
or can someone please give me hand to make this happen?

br Kusti




This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in
this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________








--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 <tel:%2B358%2020%207795%20572> (direct)
Fax: +358 20 7795 676 <tel:%2B358%2020%207795%20676>
GSM: +358 40 580 5193 <tel:%2B358%2040%20580%205193>







This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________








--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 <tel:%2B358%2020%207795%20572> (direct)
Fax: +358 20 7795 676 <tel:%2B358%2020%207795%20676>
GSM: +358 40 580 5193 <tel:%2B358%2040%20580%205193>







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________

_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
PGP KeyID: 2048R/EA31CFC9  subkeys.pgp.net


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
tog
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

tog
This is exactly what I did but although the installation went (apparently) well I had a strange feeling because for example I don't have vtk as an executable.
Nevertheless the process (brew install --verbose homebrew/science/vtk --with-qt --with-python) says
==> Summary
🍺  /usr/local/Cellar/vtk/5.10.1: 2619 files, 105M, built in 9.4 minutes


When looking for vtk binaries, I can only see:
tog$ vtk
vtkEncodeString    vtkWrapHierarchy   vtkWrapPython      vtkWrapPythonInit  vtkpython

After this:
brew install --verbose pcl --HEAD --with-openni --with-qt gives me the following error:

Error: pcl dependency vtk not installed with:
  --qt


I am a bit puzzled !

Any idea ?

Guillaume


On Mon, Jul 29, 2013 at 5:26 PM, Francisco Facioni <[hidden email]> wrote:
You need to enable the openni depency. If you want to build the full package (couldn't get the app_cloud_composer to compile yet) you have to install it with:

brew install --HEAD pcl --with-openni --with-qt

You should get kinfu and everything else.

On Saturday, July 27, 2013 at 10:32 AM, tog wrote:

Thanks
This worked like a charm. But it does not seem to build kinfu. What if I want to build it ?

Regards
Guillaume


On Fri, Jun 14, 2013 at 1:22 PM, Kustaa Nyholm <[hidden email]> wrote:
Hi Lv,



you did not mention which Mac OS version you are running.

Once the correct 'Formula' was pointed out to me installing
everything with 'homebrew' went easily according to the
plan. Of course YMMV, but I would just install homebrew
and try the formula provided by fran6co.

Install homebrew according to this page:


Then run the brew doctor to and obey the instructions it gives to you
until brew doctor says you are ready to brew:

brew doctor


Then 'tap' to fran6co github repo:

brew tap fran6co/cv


and then install with with

brew install --HEAD pcl



or if you have tapped  homebrew/science

brew install fran6co/cv/pcl


Make sure you obey brew doctor instructions and
if you have remnants of previous installation attempts you should
try to remove them.

At the end of an almost complete
installation phase it sometimes fails because brew will not
overwrite some files created by your previous attempts.

When that happens brew will name the files in questions
so you should be able to manually delete them and
try to install again.

This worked for me like a charm. Thanks for PCL and team.

br Kusti




From:  Lv Zhaoyang <[hidden email]>
Reply-To:  "Point Cloud Library (PCL) users" <[hidden email]>
Date:  Fri, 14 Jun 2013 13:34:43 +0300
To:  "Point Cloud Library (PCL) users" <[hidden email]>
Subject:  Re: [PCL-users] PCL on Mac OS X Mountain Lion


Hi Alex,
Thank you very much for your suggestion. I'll make a summary of my problems occurred. But before that, I want to uninstall the libs and try them from beginning. Do you have ideas to do that?

Now my libs have been massed up. I need some suggestions how to fix it.

Cheers,
Lv Zhaoyang


On 14 Jun 2013, at 11:26, Alexandru-Eugen Ichim <[hidden email]> wrote:


Hi Lv,
1. That is not related to PCL. Especially that you are not a C++ expert, you should not try to combine libraries and package managers on MacOS. They are not made to collaborate with each other and you will run into trouble. I only use MacPorts, but HomeBrew gives very good results too.

2. You should make sure that you create .app bundles from CMake. There are discussions on how to do this on our mailing lists: simply do ADD_EXECUTABLE (my_exec MACOSX_BUNDLE file.cpp) or PCL_ADD_EXECUTABLE_OPT_BUNDLE (...).

3. Why do you need to do that? Open up a ticket on Github presenting your situation and the errors you get, and someone will take care of it.

Cheers,
Alex



On Fri, Jun 14, 2013 at 1:16 AM, Lv Zhaoyang <[hidden email]> wrote:

Hi Radu,
I'm also a Mac user, and getting PCL just in the last week. I also had a terrible experience with the Mac PCL version, and now I just turned to Ubuntu on my virtual machine. On ubuntu everything works fine now. Here are some problems I confronted:

1. After I track the problems and google all the solutions. One problem is with the boost library. You can see it here. http://stackoverflow.com/questions/17054800/errors-in-boost-installed-from-both-macport-and-brew
No one respond me yet. So I turned to Linux finally. But the performance is affected on virtual machine. I am still glad to solve it on my mac.

2. Vtk on my mac also has problem. I tried the visualisation tutorial, but no interface appears.

3. I also disable two parts in PCL (I think it's the people_detection and outofcore). The PCL version I use it from github. In Linux, I don't need to disable anything.  

That's all the problem I finally got. If I solved these, there might be some new problems.  In general, it's not as easy as the Linux one. I spent 4 days configuring PCL on Mac. Then I turned to Linux, I solved everything in one day. The installation tutorial in Mac seems very old and not consistent. I tried at least all the three, macport, brew and the dmg file. That might be the reason I get conflicts in libs. Hope you can update it.

I'm not a experienced programmer, still a student, a rookie in C++. We hope everything can get working quite easily and program, no need learn compiler and system. Of course, you are getting better and better. Hope this feedback can be useful. And I'm still waiting for my solutions.

Best,
Lv Zhaoyang

On 13 Jun 2013, at 22:26, "Radu B. Rusu" <[hidden email]> wrote:


Kustaa,

Thanks for your e-mail. I did not take your comments about VTK to be derogatory, just simply stating that ranting with respect to "open source software" should have a slightly different tone than our daily, more usual, rants. Although as an user one is still "investing" time in figuring out an open source library, I get a bit more edgy at times about these issues, and hence I tend to remind that person that there are people behind that library, working hard at times to give back and provide open systems so that others can enjoy. Can they do better in certain areas? Of course! That's where they need help...

You won't find too many flame exchanges on our mailing lists, other than the usual SVN vs GIT, which we solved (Jochen won the argument through persistence :D), and this wouldn't have turned into one either. VTK is a great library with its set of faults. Kitware has now been generously granted a large contract/grant to revitalize VTK and build the next generation of scientific visualization libraries as part of VTK6. I've had my share of suggestions for how that should look like, and I'm sure they would appreciate to hear even more.

You are right about PCL 1.6 not being MacOS friendly, when it comes to visualization. We tried our best to provide binary DMGs, but due to a much smaller Mac OS PCL user community, we have not received enough feedback in order to fix all issues in time. We need your help (and others' too) about making that clear on our web pages. We're also hoping to kick out PCL 1.7 soon with better Mac OS support -- most if not all things have been fixed since 1.6 came out. We'll need to patch pcl_people now as well.

PS. I'm happy that fran6co managed to help. That's where the power of an open source community resides.

Cheers,
Radu.
--

On 06/13/2013 09:42 AM, Kustaa Nyholm wrote:
Hi Radu,

I'm sorry I offended you, that was not my intention.

I'm glad to hear that the pcl_people_library/module can be easily
disabled, I'm going to try that next. Thanks for helping
and pointing out the solution. And thanks for Alex
too for his help.

I may even contact the authors of that module or
supply a patch, if I can come up with one.

BTW it was not my intention to use the bleeding edge,
this was an attempt because of an other compile problem
with the stable version, which I pressumed would at
least compile without a problem.

----


Everyone not really interested in this should now touch
that dial and tune out as this is likely to run to
some number of lines as I'm going to discuss some
some of Radu's other points.

I was not (trying to be) derogatory about VTK, my point
was simply that it is not what everyone needs or can use,
it is not a panacea. I sure appreciate their efforts
and applaud that it was open sourced. And for some
tasks it works admirably I'm sure, for the tasks we
tried it some years ago it did not and we coded from
scratch to get the speed and features we needed.
Having said that I truly appreciate the years of
hard word, craftsmanship and resource that has gone in
to it.

But making it mandatory dependency on a general purpose
triangulation library does seem to go against the grain.

You say that "don't want to use VTK, simply tell PCL
to compile its modules without VTK", well I can't
get PCL to compile in the first place, which was my
main problem. The binaries I found for Mac OS X
did not work because they insisted on VTK even though
my code (empty main()) did not use them. My code
compiled and linked but failed to load. The PCL
webpage says that VTK is mandatory. When I checked
the CMake script I did not spot how to disable
VTK dependency, but then I'm new to CMake.

So excuse me when I was mistaken.

But apparently I've somehow now managed to get
VTK to compile (via brew) cause when I try to
brew install it, brew tells me it is already installed,
so that won't bother me anymore.

As to Open source, Mac, Linux I agree with you but
without wanting to expand the discussion I just want
point out that some projects work better than others
(not refering to or trying to  sneak in a derogatory
comment for PCL) and some languages / build system
are better that other in that respect.

I appreciate your comment about implementing from scratch,
well the thing I'm after is not really implemented in
PCL so I would be doing some scratch building anyway
and the thing is so small that I'm pretty sure it would
be half done by now if I had not decided to use PCL
as a reference.

But I've not totally given up on PCL yet. And I hope
you have not given up an me, I appreciate all the
help and even backfire like Rafu's mail.

Once again I'm sorry if I offended anyone and I thank
you all for the help I've received. And like I said
PCL looks awesome and promising, I wouldn't be here
writing long emails that no-one will read and
everyone ignores if I thought otherwise.

One More Thing (tm): Rafu you wrote: "a matter of how
we deal with this as a community and work together
to solve these problems that matters" I of course
agree with that but I don't think either of scored
big time in this discussion, a simple attempt to point
out that my opinion that PCL would be better off
without mandatory VTK dependency turned into the
beginnings of a flame exchange.

cheers Kusti



On 13/06/2013 18:17, "Radu B. Rusu" <[hidden email]> wrote:

Kustaa,

Your comments about VTK are definitely not appreciated. I can see where
you're coming from, perhaps you had bad
experiences in the past with VTK, but still. Our colleagues from Kitware
worked hard to give us a comprehensive set of
_open source_ visualization libraries. If you don't like it, please don't
use it. Would you rather they wouldn't have
open sourced it? I sure as hell wouldn't.

If you look around carefully, you'll notice the following problems in
your reasoning:

  *  PCL (and VTK, and Boost, and others) are generic multi-library
projects, that can be compiled conditionally, based
on what library or module you would want to use from them. If you don't
want to use VTK, simply tell PCL that you'd like
to compile its modules without VTK. You'll drop the pcl_visualization
library as well as some converter modules in
pcl_io, but that's about it.

  * the errors that you posted regarding the GitHub master branch of PCL
are easily fixable and pertain to the
pcl_people library/module. Simply disable it for now, and contact the
respective developers to fix it, or submit a fix
yourself. It's an open community, open platform, open access, and the
code that you're compiling is bleeding edge
master/trunk.

When it comes to open source 3rd party libraries and Mac OS, we will
always have issues, as Apple is not built around
open source communities, and you'll always find more Linux developers for
a project like ours than anything else. It's
all a matter of how we deal with this as a community and work together to
solve these problems that matters. Rants are
great, but they should be followed with "oh, and here's the patch that
fixes this...". Otherwise they're just long
e-mails that most people, as Alex mentioned it, tend to ignore.

Good luck reimplementing from scratch the algorithms that you need.
Sounds like a great way to spend your time :)
line.png). I'm still hoping that you'll
reconsider -- at least you've gotten awesome support on PCL mailing lists
- so we must be doing something right.

Cheers,
Radu.
--

On 06/13/2013 02:37 AM, Kustaa Nyholm wrote:
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

cl
uding-Kinfu-td4022018.html


Cheers,
Radu.
--

On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
Hi,

having had a frustrating two days trying to install PCL on my
own I decided to seek for help...

I tried the binaries from here:


but they did not work, I've already forgotten what's the issue,
might have been that I was unable to install VTK...
IIRC I could get it to compile by installing a bunch of
stuff via MacPorts but then a simple
C program with just main() with out calling anything
in PCL fails to load because it cannot find VTK...
which is kind...ermh annoying as I have no need for
VTK...to me it seems that strictly 'point cloud only'
library without dependencies on libusb, OpenNI
and VTK would make sense, I could do without boost too,
though eigen seem like a good idea...but I digress.

Anyway, I'm a homebrew user so eventually I just
delete everything related to macports and PCL
and started from scratch with these instructions:

ph
p

This went rather well once I discovered the
'brew tap homebrew/science' to get the dependencies
to install as per instructions, which might be a
handy tip for people like me who
are not so up to speed with all things homebrew.

However at the end this failed because the tar file
the brew expects for PCL has move. Little bit of googling
enabled me to find the 1.6.0 tar file and hacking
the pcl.rb file allowed the download to succeed and
compile begun. BTW is there an up to date .rb file
somewhere?

In the end that compilation failed at 8% mark with
mysterious error

make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
make: *** [all] Error 2


Manually compiling PCL revealed that this related to
some or other 'at' symbol not being found which after
a little googling seems to be a problem with Apple clang.

I was not prepared to go back to gcc (supposing it
was available for Mountain Lion and latest X-code)
and after googling that the issue was supposed to
be fixed about a year ago I tried to compile from
the trunk with:

brew install pcl --HEAD

this goes quite a long way but eventually fails
with the mysterious Error 2:

dyld: DYLD_ environment variables being ignored because main executable
(/usr/bin/sudo) is setuid or setgid
==> mkdir build
==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
==> make install
[ 98%] Built target test_registration
Linking CXX shared library ../lib/libpcl_recognition.dylib
brew: superenv removed: -Wno-invalid-offsetof
[ 98%] Built target pcl_recognition
make: *** [all] Error 2



At this point I decided to seek some help, especially
as I saw a couple notes that claimed that this
install from source without a hitch on Mountain Lion.

So is there an up to date instruction for doing this somewhere
or can someone please give me hand to make this happen?

br Kusti




This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in
this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________








--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 <tel:%2B358%2020%207795%20572> (direct)
Fax: +358 20 7795 676 <tel:%2B358%2020%207795%20676>
GSM: +358 40 580 5193 <tel:%2B358%2040%20580%205193>







This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________








--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 <tel:%2B358%2020%207795%20572> (direct)
Fax: +358 20 7795 676 <tel:%2B358%2020%207795%20676>
GSM: +358 40 580 5193 <tel:%2B358%2040%20580%205193>







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________

_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
PGP KeyID: 2048R/EA31CFC9  subkeys.pgp.net


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
PGP KeyID: 2048R/EA31CFC9  subkeys.pgp.net

_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

Radu B. Rusu
Administrator
Just as a note, using vtk from macports worked just fine for me.

Best,
Radu.

On Jul 31, 2013, at 8:38 AM, tog <[hidden email]> wrote:

This is exactly what I did but although the installation went (apparently) well I had a strange feeling because for example I don't have vtk as an executable.
Nevertheless the process (brew install --verbose homebrew/science/vtk --with-qt --with-python) says
==> Summary
🍺  /usr/local/Cellar/vtk/5.10.1: 2619 files, 105M, built in 9.4 minutes


When looking for vtk binaries, I can only see:
tog$ vtk
vtkEncodeString    vtkWrapHierarchy   vtkWrapPython      vtkWrapPythonInit  vtkpython

After this:
brew install --verbose pcl --HEAD --with-openni --with-qt gives me the following error:

Error: pcl dependency vtk not installed with:
  --qt


I am a bit puzzled !

Any idea ?

Guillaume


On Mon, Jul 29, 2013 at 5:26 PM, Francisco Facioni <[hidden email]> wrote:
You need to enable the openni depency. If you want to build the full package (couldn't get the app_cloud_composer to compile yet) you have to install it with:

brew install --HEAD pcl --with-openni --with-qt

You should get kinfu and everything else.

On Saturday, July 27, 2013 at 10:32 AM, tog wrote:

Thanks
This worked like a charm. But it does not seem to build kinfu. What if I want to build it ?

Regards
Guillaume


On Fri, Jun 14, 2013 at 1:22 PM, Kustaa Nyholm <[hidden email]> wrote:
Hi Lv,



you did not mention which Mac OS version you are running.

Once the correct 'Formula' was pointed out to me installing
everything with 'homebrew' went easily according to the
plan. Of course YMMV, but I would just install homebrew
and try the formula provided by fran6co.

Install homebrew according to this page:


Then run the brew doctor to and obey the instructions it gives to you
until brew doctor says you are ready to brew:

brew doctor


Then 'tap' to fran6co github repo:

brew tap fran6co/cv


and then install with with

brew install --HEAD pcl



or if you have tapped  homebrew/science

brew install fran6co/cv/pcl


Make sure you obey brew doctor instructions and
if you have remnants of previous installation attempts you should
try to remove them.

At the end of an almost complete
installation phase it sometimes fails because brew will not
overwrite some files created by your previous attempts.

When that happens brew will name the files in questions
so you should be able to manually delete them and
try to install again.

This worked for me like a charm. Thanks for PCL and team.

br Kusti




From:  Lv Zhaoyang <[hidden email]>
Reply-To:  "Point Cloud Library (PCL) users" <[hidden email]>
Date:  Fri, 14 Jun 2013 13:34:43 +0300
To:  "Point Cloud Library (PCL) users" <[hidden email]>
Subject:  Re: [PCL-users] PCL on Mac OS X Mountain Lion


Hi Alex,
Thank you very much for your suggestion. I'll make a summary of my problems occurred. But before that, I want to uninstall the libs and try them from beginning. Do you have ideas to do that?

Now my libs have been massed up. I need some suggestions how to fix it.

Cheers,
Lv Zhaoyang


On 14 Jun 2013, at 11:26, Alexandru-Eugen Ichim <[hidden email]> wrote:


Hi Lv,
1. That is not related to PCL. Especially that you are not a C++ expert, you should not try to combine libraries and package managers on MacOS. They are not made to collaborate with each other and you will run into trouble. I only use MacPorts, but HomeBrew gives very good results too.

2. You should make sure that you create .app bundles from CMake. There are discussions on how to do this on our mailing lists: simply do ADD_EXECUTABLE (my_exec MACOSX_BUNDLE file.cpp) or PCL_ADD_EXECUTABLE_OPT_BUNDLE (...).

3. Why do you need to do that? Open up a ticket on Github presenting your situation and the errors you get, and someone will take care of it.

Cheers,
Alex



On Fri, Jun 14, 2013 at 1:16 AM, Lv Zhaoyang <[hidden email]> wrote:

Hi Radu,
I'm also a Mac user, and getting PCL just in the last week. I also had a terrible experience with the Mac PCL version, and now I just turned to Ubuntu on my virtual machine. On ubuntu everything works fine now. Here are some problems I confronted:

1. After I track the problems and google all the solutions. One problem is with the boost library. You can see it here. http://stackoverflow.com/questions/17054800/errors-in-boost-installed-from-both-macport-and-brew
No one respond me yet. So I turned to Linux finally. But the performance is affected on virtual machine. I am still glad to solve it on my mac.

2. Vtk on my mac also has problem. I tried the visualisation tutorial, but no interface appears.

3. I also disable two parts in PCL (I think it's the people_detection and outofcore). The PCL version I use it from github. In Linux, I don't need to disable anything.  

That's all the problem I finally got. If I solved these, there might be some new problems.  In general, it's not as easy as the Linux one. I spent 4 days configuring PCL on Mac. Then I turned to Linux, I solved everything in one day. The installation tutorial in Mac seems very old and not consistent. I tried at least all the three, macport, brew and the dmg file. That might be the reason I get conflicts in libs. Hope you can update it.

I'm not a experienced programmer, still a student, a rookie in C++. We hope everything can get working quite easily and program, no need learn compiler and system. Of course, you are getting better and better. Hope this feedback can be useful. And I'm still waiting for my solutions.

Best,
Lv Zhaoyang

On 13 Jun 2013, at 22:26, "Radu B. Rusu" <[hidden email]> wrote:


Kustaa,

Thanks for your e-mail. I did not take your comments about VTK to be derogatory, just simply stating that ranting with respect to "open source software" should have a slightly different tone than our daily, more usual, rants. Although as an user one is still "investing" time in figuring out an open source library, I get a bit more edgy at times about these issues, and hence I tend to remind that person that there are people behind that library, working hard at times to give back and provide open systems so that others can enjoy. Can they do better in certain areas? Of course! That's where they need help...

You won't find too many flame exchanges on our mailing lists, other than the usual SVN vs GIT, which we solved (Jochen won the argument through persistence :D), and this wouldn't have turned into one either. VTK is a great library with its set of faults. Kitware has now been generously granted a large contract/grant to revitalize VTK and build the next generation of scientific visualization libraries as part of VTK6. I've had my share of suggestions for how that should look like, and I'm sure they would appreciate to hear even more.

You are right about PCL 1.6 not being MacOS friendly, when it comes to visualization. We tried our best to provide binary DMGs, but due to a much smaller Mac OS PCL user community, we have not received enough feedback in order to fix all issues in time. We need your help (and others' too) about making that clear on our web pages. We're also hoping to kick out PCL 1.7 soon with better Mac OS support -- most if not all things have been fixed since 1.6 came out. We'll need to patch pcl_people now as well.

PS. I'm happy that fran6co managed to help. That's where the power of an open source community resides.

Cheers,
Radu.
--

On 06/13/2013 09:42 AM, Kustaa Nyholm wrote:
Hi Radu,

I'm sorry I offended you, that was not my intention.

I'm glad to hear that the pcl_people_library/module can be easily
disabled, I'm going to try that next. Thanks for helping
and pointing out the solution. And thanks for Alex
too for his help.

I may even contact the authors of that module or
supply a patch, if I can come up with one.

BTW it was not my intention to use the bleeding edge,
this was an attempt because of an other compile problem
with the stable version, which I pressumed would at
least compile without a problem.

----


Everyone not really interested in this should now touch
that dial and tune out as this is likely to run to
some number of lines as I'm going to discuss some
some of Radu's other points.

I was not (trying to be) derogatory about VTK, my point
was simply that it is not what everyone needs or can use,
it is not a panacea. I sure appreciate their efforts
and applaud that it was open sourced. And for some
tasks it works admirably I'm sure, for the tasks we
tried it some years ago it did not and we coded from
scratch to get the speed and features we needed.
Having said that I truly appreciate the years of
hard word, craftsmanship and resource that has gone in
to it.

But making it mandatory dependency on a general purpose
triangulation library does seem to go against the grain.

You say that "don't want to use VTK, simply tell PCL
to compile its modules without VTK", well I can't
get PCL to compile in the first place, which was my
main problem. The binaries I found for Mac OS X
did not work because they insisted on VTK even though
my code (empty main()) did not use them. My code
compiled and linked but failed to load. The PCL
webpage says that VTK is mandatory. When I checked
the CMake script I did not spot how to disable
VTK dependency, but then I'm new to CMake.

So excuse me when I was mistaken.

But apparently I've somehow now managed to get
VTK to compile (via brew) cause when I try to
brew install it, brew tells me it is already installed,
so that won't bother me anymore.

As to Open source, Mac, Linux I agree with you but
without wanting to expand the discussion I just want
point out that some projects work better than others
(not refering to or trying to  sneak in a derogatory
comment for PCL) and some languages / build system
are better that other in that respect.

I appreciate your comment about implementing from scratch,
well the thing I'm after is not really implemented in
PCL so I would be doing some scratch building anyway
and the thing is so small that I'm pretty sure it would
be half done by now if I had not decided to use PCL
as a reference.

But I've not totally given up on PCL yet. And I hope
you have not given up an me, I appreciate all the
help and even backfire like Rafu's mail.

Once again I'm sorry if I offended anyone and I thank
you all for the help I've received. And like I said
PCL looks awesome and promising, I wouldn't be here
writing long emails that no-one will read and
everyone ignores if I thought otherwise.

One More Thing (tm): Rafu you wrote: "a matter of how
we deal with this as a community and work together
to solve these problems that matters" I of course
agree with that but I don't think either of scored
big time in this discussion, a simple attempt to point
out that my opinion that PCL would be better off
without mandatory VTK dependency turned into the
beginnings of a flame exchange.

cheers Kusti



On 13/06/2013 18:17, "Radu B. Rusu" <[hidden email]> wrote:

Kustaa,

Your comments about VTK are definitely not appreciated. I can see where
you're coming from, perhaps you had bad
experiences in the past with VTK, but still. Our colleagues from Kitware
worked hard to give us a comprehensive set of
_open source_ visualization libraries. If you don't like it, please don't
use it. Would you rather they wouldn't have
open sourced it? I sure as hell wouldn't.

If you look around carefully, you'll notice the following problems in
your reasoning:

  *  PCL (and VTK, and Boost, and others) are generic multi-library
projects, that can be compiled conditionally, based
on what library or module you would want to use from them. If you don't
want to use VTK, simply tell PCL that you'd like
to compile its modules without VTK. You'll drop the pcl_visualization
library as well as some converter modules in
pcl_io, but that's about it.

  * the errors that you posted regarding the GitHub master branch of PCL
are easily fixable and pertain to the
pcl_people library/module. Simply disable it for now, and contact the
respective developers to fix it, or submit a fix
yourself. It's an open community, open platform, open access, and the
code that you're compiling is bleeding edge
master/trunk.

When it comes to open source 3rd party libraries and Mac OS, we will
always have issues, as Apple is not built around
open source communities, and you'll always find more Linux developers for
a project like ours than anything else. It's
all a matter of how we deal with this as a community and work together to
solve these problems that matters. Rants are
great, but they should be followed with "oh, and here's the patch that
fixes this...". Otherwise they're just long
e-mails that most people, as Alex mentioned it, tend to ignore.

Good luck reimplementing from scratch the algorithms that you need.
Sounds like a great way to spend your time :)
line.png). I'm still hoping that you'll
reconsider -- at least you've gotten awesome support on PCL mailing lists
- so we must be doing something right.

Cheers,
Radu.
--

On 06/13/2013 02:37 AM, Kustaa Nyholm wrote:
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

cl
uding-Kinfu-td4022018.html


Cheers,
Radu.
--

On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
Hi,

having had a frustrating two days trying to install PCL on my
own I decided to seek for help...

I tried the binaries from here:


but they did not work, I've already forgotten what's the issue,
might have been that I was unable to install VTK...
IIRC I could get it to compile by installing a bunch of
stuff via MacPorts but then a simple
C program with just main() with out calling anything
in PCL fails to load because it cannot find VTK...
which is kind...ermh annoying as I have no need for
VTK...to me it seems that strictly 'point cloud only'
library without dependencies on libusb, OpenNI
and VTK would make sense, I could do without boost too,
though eigen seem like a good idea...but I digress.

Anyway, I'm a homebrew user so eventually I just
delete everything related to macports and PCL
and started from scratch with these instructions:

ph
p

This went rather well once I discovered the
'brew tap homebrew/science' to get the dependencies
to install as per instructions, which might be a
handy tip for people like me who
are not so up to speed with all things homebrew.

However at the end this failed because the tar file
the brew expects for PCL has move. Little bit of googling
enabled me to find the 1.6.0 tar file and hacking
the pcl.rb file allowed the download to succeed and
compile begun. BTW is there an up to date .rb file
somewhere?

In the end that compilation failed at 8% mark with
mysterious error

make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
make: *** [all] Error 2


Manually compiling PCL revealed that this related to
some or other 'at' symbol not being found which after
a little googling seems to be a problem with Apple clang.

I was not prepared to go back to gcc (supposing it
was available for Mountain Lion and latest X-code)
and after googling that the issue was supposed to
be fixed about a year ago I tried to compile from
the trunk with:

brew install pcl --HEAD

this goes quite a long way but eventually fails
with the mysterious Error 2:

dyld: DYLD_ environment variables being ignored because main executable
(/usr/bin/sudo) is setuid or setgid
==> mkdir build
==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
==> make install
[ 98%] Built target test_registration
Linking CXX shared library ../lib/libpcl_recognition.dylib
brew: superenv removed: -Wno-invalid-offsetof
[ 98%] Built target pcl_recognition
make: *** [all] Error 2



At this point I decided to seek some help, especially
as I saw a couple notes that claimed that this
install from source without a hitch on Mountain Lion.

So is there an up to date instruction for doing this somewhere
or can someone please give me hand to make this happen?

br Kusti




This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in
this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________








--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 <tel:%2B358%2020%207795%20572> (direct)
Fax: +358 20 7795 676 <tel:%2B358%2020%207795%20676>
GSM: +358 40 580 5193 <tel:%2B358%2040%20580%205193>







This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________








--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 <tel:%2B358%2020%207795%20572> (direct)
Fax: +358 20 7795 676 <tel:%2B358%2020%207795%20676>
GSM: +358 40 580 5193 <tel:%2B358%2040%20580%205193>







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________

_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
PGP KeyID: 2048R/EA31CFC9  subkeys.pgp.net


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
PGP KeyID: 2048R/EA31CFC9  subkeys.pgp.net
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCL on Mac OS X Mountain Lion

fran6co
In reply to this post by tog
You need to reinstall vtk with

brew remove vtk
brew install vtk --with-qt

and then reinstall pcl.

Somtimes homebrew doesn't pass along the flags to the dependencies.

On Wednesday, July 31, 2013 at 12:38 PM, tog wrote:

This is exactly what I did but although the installation went (apparently) well I had a strange feeling because for example I don't have vtk as an executable.
Nevertheless the process (brew install --verbose homebrew/science/vtk --with-qt --with-python) says
==> Summary
🍺  /usr/local/Cellar/vtk/5.10.1: 2619 files, 105M, built in 9.4 minutes


When looking for vtk binaries, I can only see:
tog$ vtk
vtkEncodeString    vtkWrapHierarchy   vtkWrapPython      vtkWrapPythonInit  vtkpython

After this:
brew install --verbose pcl --HEAD --with-openni --with-qt gives me the following error:

Error: pcl dependency vtk not installed with:
  --qt


I am a bit puzzled !

Any idea ?

Guillaume


On Mon, Jul 29, 2013 at 5:26 PM, Francisco Facioni <[hidden email]> wrote:
You need to enable the openni depency. If you want to build the full package (couldn't get the app_cloud_composer to compile yet) you have to install it with:

brew install --HEAD pcl --with-openni --with-qt

You should get kinfu and everything else.

On Saturday, July 27, 2013 at 10:32 AM, tog wrote:

Thanks
This worked like a charm. But it does not seem to build kinfu. What if I want to build it ?

Regards
Guillaume


On Fri, Jun 14, 2013 at 1:22 PM, Kustaa Nyholm <[hidden email]> wrote:
Hi Lv,



you did not mention which Mac OS version you are running.

Once the correct 'Formula' was pointed out to me installing
everything with 'homebrew' went easily according to the
plan. Of course YMMV, but I would just install homebrew
and try the formula provided by fran6co.

Install homebrew according to this page:


Then run the brew doctor to and obey the instructions it gives to you
until brew doctor says you are ready to brew:

brew doctor


Then 'tap' to fran6co github repo:

brew tap fran6co/cv


and then install with with

brew install --HEAD pcl



or if you have tapped  homebrew/science

brew install fran6co/cv/pcl


Make sure you obey brew doctor instructions and
if you have remnants of previous installation attempts you should
try to remove them.

At the end of an almost complete
installation phase it sometimes fails because brew will not
overwrite some files created by your previous attempts.

When that happens brew will name the files in questions
so you should be able to manually delete them and
try to install again.

This worked for me like a charm. Thanks for PCL and team.

br Kusti




From:  Lv Zhaoyang <[hidden email]>
Reply-To:  "Point Cloud Library (PCL) users" <[hidden email]>
Date:  Fri, 14 Jun 2013 13:34:43 +0300
To:  "Point Cloud Library (PCL) users" <[hidden email]>
Subject:  Re: [PCL-users] PCL on Mac OS X Mountain Lion


Hi Alex,
Thank you very much for your suggestion. I'll make a summary of my problems occurred. But before that, I want to uninstall the libs and try them from beginning. Do you have ideas to do that?

Now my libs have been massed up. I need some suggestions how to fix it.

Cheers,
Lv Zhaoyang


On 14 Jun 2013, at 11:26, Alexandru-Eugen Ichim <[hidden email]> wrote:


Hi Lv,
1. That is not related to PCL. Especially that you are not a C++ expert, you should not try to combine libraries and package managers on MacOS. They are not made to collaborate with each other and you will run into trouble. I only use MacPorts, but HomeBrew gives very good results too.

2. You should make sure that you create .app bundles from CMake. There are discussions on how to do this on our mailing lists: simply do ADD_EXECUTABLE (my_exec MACOSX_BUNDLE file.cpp) or PCL_ADD_EXECUTABLE_OPT_BUNDLE (...).

3. Why do you need to do that? Open up a ticket on Github presenting your situation and the errors you get, and someone will take care of it.

Cheers,
Alex



On Fri, Jun 14, 2013 at 1:16 AM, Lv Zhaoyang <[hidden email]> wrote:

Hi Radu,
I'm also a Mac user, and getting PCL just in the last week. I also had a terrible experience with the Mac PCL version, and now I just turned to Ubuntu on my virtual machine. On ubuntu everything works fine now. Here are some problems I confronted:

1. After I track the problems and google all the solutions. One problem is with the boost library. You can see it here. http://stackoverflow.com/questions/17054800/errors-in-boost-installed-from-both-macport-and-brew
No one respond me yet. So I turned to Linux finally. But the performance is affected on virtual machine. I am still glad to solve it on my mac.

2. Vtk on my mac also has problem. I tried the visualisation tutorial, but no interface appears.

3. I also disable two parts in PCL (I think it's the people_detection and outofcore). The PCL version I use it from github. In Linux, I don't need to disable anything.  

That's all the problem I finally got. If I solved these, there might be some new problems.  In general, it's not as easy as the Linux one. I spent 4 days configuring PCL on Mac. Then I turned to Linux, I solved everything in one day. The installation tutorial in Mac seems very old and not consistent. I tried at least all the three, macport, brew and the dmg file. That might be the reason I get conflicts in libs. Hope you can update it.

I'm not a experienced programmer, still a student, a rookie in C++. We hope everything can get working quite easily and program, no need learn compiler and system. Of course, you are getting better and better. Hope this feedback can be useful. And I'm still waiting for my solutions.

Best,
Lv Zhaoyang

On 13 Jun 2013, at 22:26, "Radu B. Rusu" <[hidden email]> wrote:


Kustaa,

Thanks for your e-mail. I did not take your comments about VTK to be derogatory, just simply stating that ranting with respect to "open source software" should have a slightly different tone than our daily, more usual, rants. Although as an user one is still "investing" time in figuring out an open source library, I get a bit more edgy at times about these issues, and hence I tend to remind that person that there are people behind that library, working hard at times to give back and provide open systems so that others can enjoy. Can they do better in certain areas? Of course! That's where they need help...

You won't find too many flame exchanges on our mailing lists, other than the usual SVN vs GIT, which we solved (Jochen won the argument through persistence :D), and this wouldn't have turned into one either. VTK is a great library with its set of faults. Kitware has now been generously granted a large contract/grant to revitalize VTK and build the next generation of scientific visualization libraries as part of VTK6. I've had my share of suggestions for how that should look like, and I'm sure they would appreciate to hear even more.

You are right about PCL 1.6 not being MacOS friendly, when it comes to visualization. We tried our best to provide binary DMGs, but due to a much smaller Mac OS PCL user community, we have not received enough feedback in order to fix all issues in time. We need your help (and others' too) about making that clear on our web pages. We're also hoping to kick out PCL 1.7 soon with better Mac OS support -- most if not all things have been fixed since 1.6 came out. We'll need to patch pcl_people now as well.

PS. I'm happy that fran6co managed to help. That's where the power of an open source community resides.

Cheers,
Radu.
--

On 06/13/2013 09:42 AM, Kustaa Nyholm wrote:
Hi Radu,

I'm sorry I offended you, that was not my intention.

I'm glad to hear that the pcl_people_library/module can be easily
disabled, I'm going to try that next. Thanks for helping
and pointing out the solution. And thanks for Alex
too for his help.

I may even contact the authors of that module or
supply a patch, if I can come up with one.

BTW it was not my intention to use the bleeding edge,
this was an attempt because of an other compile problem
with the stable version, which I pressumed would at
least compile without a problem.

----


Everyone not really interested in this should now touch
that dial and tune out as this is likely to run to
some number of lines as I'm going to discuss some
some of Radu's other points.

I was not (trying to be) derogatory about VTK, my point
was simply that it is not what everyone needs or can use,
it is not a panacea. I sure appreciate their efforts
and applaud that it was open sourced. And for some
tasks it works admirably I'm sure, for the tasks we
tried it some years ago it did not and we coded from
scratch to get the speed and features we needed.
Having said that I truly appreciate the years of
hard word, craftsmanship and resource that has gone in
to it.

But making it mandatory dependency on a general purpose
triangulation library does seem to go against the grain.

You say that "don't want to use VTK, simply tell PCL
to compile its modules without VTK", well I can't
get PCL to compile in the first place, which was my
main problem. The binaries I found for Mac OS X
did not work because they insisted on VTK even though
my code (empty main()) did not use them. My code
compiled and linked but failed to load. The PCL
webpage says that VTK is mandatory. When I checked
the CMake script I did not spot how to disable
VTK dependency, but then I'm new to CMake.

So excuse me when I was mistaken.

But apparently I've somehow now managed to get
VTK to compile (via brew) cause when I try to
brew install it, brew tells me it is already installed,
so that won't bother me anymore.

As to Open source, Mac, Linux I agree with you but
without wanting to expand the discussion I just want
point out that some projects work better than others
(not refering to or trying to  sneak in a derogatory
comment for PCL) and some languages / build system
are better that other in that respect.

I appreciate your comment about implementing from scratch,
well the thing I'm after is not really implemented in
PCL so I would be doing some scratch building anyway
and the thing is so small that I'm pretty sure it would
be half done by now if I had not decided to use PCL
as a reference.

But I've not totally given up on PCL yet. And I hope
you have not given up an me, I appreciate all the
help and even backfire like Rafu's mail.

Once again I'm sorry if I offended anyone and I thank
you all for the help I've received. And like I said
PCL looks awesome and promising, I wouldn't be here
writing long emails that no-one will read and
everyone ignores if I thought otherwise.

One More Thing (tm): Rafu you wrote: "a matter of how
we deal with this as a community and work together
to solve these problems that matters" I of course
agree with that but I don't think either of scored
big time in this discussion, a simple attempt to point
out that my opinion that PCL would be better off
without mandatory VTK dependency turned into the
beginnings of a flame exchange.

cheers Kusti



On 13/06/2013 18:17, "Radu B. Rusu" <[hidden email]> wrote:

Kustaa,

Your comments about VTK are definitely not appreciated. I can see where
you're coming from, perhaps you had bad
experiences in the past with VTK, but still. Our colleagues from Kitware
worked hard to give us a comprehensive set of
_open source_ visualization libraries. If you don't like it, please don't
use it. Would you rather they wouldn't have
open sourced it? I sure as hell wouldn't.

If you look around carefully, you'll notice the following problems in
your reasoning:

  *  PCL (and VTK, and Boost, and others) are generic multi-library
projects, that can be compiled conditionally, based
on what library or module you would want to use from them. If you don't
want to use VTK, simply tell PCL that you'd like
to compile its modules without VTK. You'll drop the pcl_visualization
library as well as some converter modules in
pcl_io, but that's about it.

  * the errors that you posted regarding the GitHub master branch of PCL
are easily fixable and pertain to the
pcl_people library/module. Simply disable it for now, and contact the
respective developers to fix it, or submit a fix
yourself. It's an open community, open platform, open access, and the
code that you're compiling is bleeding edge
master/trunk.

When it comes to open source 3rd party libraries and Mac OS, we will
always have issues, as Apple is not built around
open source communities, and you'll always find more Linux developers for
a project like ours than anything else. It's
all a matter of how we deal with this as a community and work together to
solve these problems that matters. Rants are
great, but they should be followed with "oh, and here's the patch that
fixes this...". Otherwise they're just long
e-mails that most people, as Alex mentioned it, tend to ignore.

Good luck reimplementing from scratch the algorithms that you need.
Sounds like a great way to spend your time :)
line.png). I'm still hoping that you'll
reconsider -- at least you've gotten awesome support on PCL mailing lists
- so we must be doing something right.

Cheers,
Radu.
--

On 06/13/2013 02:37 AM, Kustaa Nyholm wrote:
Hi Radu,

thanks for the link I had not stumbled up on it earlier.

Reading through Ken's nice writeup it looks daunting and
fragile in that I'm as likely to fail with those instructions
than on my own.

I tried the superbuild but that fails to build flan which
brew builds without a hitch.

At the moment I think I'm going to give PCL a rest and
concentrate on re-implementing from scratch the few bits
and algorithms I was hoping to use from PCL. I think my
time is better utilised in writing code than trying to
resolve build issues and dependencies with huge C-libraries.

PCL looked so promising and interesting that I gave it
a chance and  let my stead fast rule never to use any
large C-code base that does not compile out-of-the-box.

Sad, but there it is, the C-toolchain and the tendency
to re-use code by depending on other complex libraries
seems to me to be the biggest stumbling block for code (re)use.

I hope to come back to PCL in the future when the build
process on Mac is mature enough so that I don't have
to struggle with it.

Meanwhile I hope the project/build structure could
be so re-structured that users could just use the
parts they need without needing to whole rigmarole build.

I can live with boost and eigen and it is difficult
to see that it would make sense to attempt something
like PCL without them but VTK ... oh please...without
that monster I've had been in business long time ago.

Just MO.

br Kusti





On 12/06/2013 17:43, "Radu B. Rusu" <[hidden email]> wrote:

cl
uding-Kinfu-td4022018.html


Cheers,
Radu.
--

On 06/12/2013 04:15 AM, Kustaa Nyholm wrote:
Hi,

having had a frustrating two days trying to install PCL on my
own I decided to seek for help...

I tried the binaries from here:


but they did not work, I've already forgotten what's the issue,
might have been that I was unable to install VTK...
IIRC I could get it to compile by installing a bunch of
stuff via MacPorts but then a simple
C program with just main() with out calling anything
in PCL fails to load because it cannot find VTK...
which is kind...ermh annoying as I have no need for
VTK...to me it seems that strictly 'point cloud only'
library without dependencies on libusb, OpenNI
and VTK would make sense, I could do without boost too,
though eigen seem like a good idea...but I digress.

Anyway, I'm a homebrew user so eventually I just
delete everything related to macports and PCL
and started from scratch with these instructions:

ph
p

This went rather well once I discovered the
'brew tap homebrew/science' to get the dependencies
to install as per instructions, which might be a
handy tip for people like me who
are not so up to speed with all things homebrew.

However at the end this failed because the tar file
the brew expects for PCL has move. Little bit of googling
enabled me to find the 1.6.0 tar file and hacking
the pcl.rb file allowed the download to succeed and
compile begun. BTW is there an up to date .rb file
somewhere?

In the end that compilation failed at 8% mark with
mysterious error

make[2]: *** [io/CMakeFiles/pcl_io.dir/src/ply_io.cpp.o] Error 1
make[1]: *** [io/CMakeFiles/pcl_io.dir/all] Error 2
make: *** [all] Error 2


Manually compiling PCL revealed that this related to
some or other 'at' symbol not being found which after
a little googling seems to be a problem with Apple clang.

I was not prepared to go back to gcc (supposing it
was available for Mountain Lion and latest X-code)
and after googling that the issue was supposed to
be fixed about a year ago I tried to compile from
the trunk with:

brew install pcl --HEAD

this goes quite a long way but eventually fails
with the mysterious Error 2:

dyld: DYLD_ environment variables being ignored because main executable
(/usr/bin/sudo) is setuid or setgid
==> mkdir build
==> cmake -DCMAKE_INSTALL_PREFIX='/usr/local/Cellar/pcl/HEAD'
-DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno
==> make install
[ 98%] Built target test_registration
Linking CXX shared library ../lib/libpcl_recognition.dylib
brew: superenv removed: -Wno-invalid-offsetof
[ 98%] Built target pcl_recognition
make: *** [all] Error 2



At this point I decided to seek some help, especially
as I saw a couple notes that claimed that this
install from source without a hitch on Mountain Lion.

So is there an up to date instruction for doing this somewhere
or can someone please give me hand to make this happen?

br Kusti




This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in
this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________








--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 <tel:%2B358%2020%207795%20572> (direct)
Fax: +358 20 7795 676 <tel:%2B358%2020%207795%20676>
GSM: +358 40 580 5193 <tel:%2B358%2040%20580%205193>







This e-mail may contain confidential or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden. We will not be liable for direct,
indirect, special or consequential damages arising from alteration of
the contents of this message by a third party or as a result of any
virus being passed on or as of transmission of this e-mail in general.
_______________________________________________








--
Kustaa Nyholm
Research Manager, Software
Research and Technology Division
PLANMECA OY
Asentajankatu 6
00880 HELSINKI
FINLAND

Please note our new telephone and fax numbers!
Tel: +358 20 7795 572 <tel:%2B358%2020%207795%20572> (direct)
Fax: +358 20 7795 676 <tel:%2B358%2020%207795%20676>
GSM: +358 40 580 5193 <tel:%2B358%2040%20580%205193>







This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general.
_______________________________________________

_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
PGP KeyID: 2048R/EA31CFC9  subkeys.pgp.net


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users




--
PGP KeyID: 2048R/EA31CFC9  subkeys.pgp.net


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users