<div dir="ltr">The Android build is optional. You can disable it by setting the cmake variable VES_ANDROID_SUPERBUILD to OFF. Try that, then run make again.<br><br>Pat<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Jun 12, 2013 at 3:59 AM, Christopher Herbon <span dir="ltr"><<a href="mailto:chrisherbon@gmail.com" target="_blank">chrisherbon@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Hi Pat,<div><br></div><div>thank you so much for your help! I mistakenly assumed that compiling it for Android was optional, because I don't really need it. So I downloaded the Android NDK (Mac OS 64 Bit) and put it in /opt/android-ndk. I then deleted the build directory and ran cmake again, as you can see in the log I attached. I am not quite sure why, but the Android-NDK does not seem to be found.</div>
<div><br></div><div>Chris</div><div><br></div><div></div></div><br><div style="word-wrap:break-word"><div></div><div><br></div><div> <br><div><div>Am 11.06.2013 um 16:25 schrieb Pat Marion <<a href="mailto:pat.marion@kitware.com" target="_blank">pat.marion@kitware.com</a>>:</div>
<br><blockquote type="cite"><div dir="ltr"><div><div>Hi Chris,<br><br>In the build log you attached, it shows that you did not set the ANDROID_NDK environment variable. You should set that to the path to your installed NDK directory, something like:<br>
<br>export ANDROID_NDK=/path/to/android-ndk-r8<br><br></div>Then do a clean build (remove the build directory and start over). The reason your build stops at different times is because you are doing a parallel make using the argument -j4. So some make jobs will continue to run a while before stopping. If you remove -j4 then the build will stop consistently, but it will run slower.<br>
<br>Hope this helps!<br><br></div>Pat<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 11, 2013 at 4:35 AM, Christopher Herbon <span dir="ltr"><<a href="mailto:chrisherbon@gmail.com" target="_blank">chrisherbon@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Ok, so I did what you asked and you can see the results attached below. It seems very strange to me, that the error always occurs at a different time, but always when processing VTK. Sometimes it stops after two minutes of processing (which is the case for the attached output), sometimes after an hour or so. <div>
<br></div><div>My problem is, that I cannot use the precompiled pcl.framework for iOS, because it wasn't compiled with libc++ but with libstdc++, which I cannot use because of other libraries. You wouldn't happen to know if or where such a version of a pcl.framework was available?<br>
<div><br></div><div></div></div></div><br><div style="word-wrap:break-word"><div></div><div><br><div><div>Am 10.06.2013 um 16:27 schrieb Pat Marion <<a href="mailto:pat.marion@kitware.com" target="_blank">pat.marion@kitware.com</a>>:</div>
<br><blockquote type="cite"><div dir="ltr">The build output you provided does not give enough information, you'll have to send the full output. Even better, run "make VERBOSE=1" to capture even more output, then compress the build output and attach it to the email.<br>
<br>What version of pcl-superbuild are you using? If you cd to the pcl-superbuild directory, and run "git rev-parse HEAD" what does it print?<br><br>Pat<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Jun 10, 2013 at 10:03 AM, Christopher Herbon <span dir="ltr"><<a href="mailto:chrisherbon@gmail.com" target="_blank">chrisherbon@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When following the guide (<a href="http://www.vtk.org/Wiki/VES/Point_Cloud_Library" target="_blank">http://www.vtk.org/Wiki/VES/Point_Cloud_Library</a>) I always get the error shown below. What can I do about this? I need PCL for iOS which was compiled using libc++, therefore I connot use the precompiled version.<br>
<br>
[ 30%] Completed 'ves-fetch'<br>
[ 30%] Built target ves-fetch<br>
remote: Total 32985 (delta 13679), reused 32985 (delta 13679)<br>
Receiving objects: 100% (32985/32985), 52.74 MiB | 956 KiB/s, done.<br>
Resolving deltas: 100% (13679/13679), done..99 MiB | 597 KiB/s<br>
Checking out files: 100% (31207/31207), done.9 MiB | 1.10 MiB/s<br>
Note: checking out 'origin/master'.730), 70.71 MiB | 960 KiB/s<br>
<br>
You are in 'detached HEAD' state. You can look around, make experimental<br>
changes and commit them, and you can discard any commits you make in this<br>
state without impacting any branches by performing another checkout.<br>
<br>
If you want to create a new branch to retain commits you create, you may<br>
do so (now or later) by using -b with the checkout command again. Example:<br>
<br>
git checkout -b new_branch_name<br>
<br>
HEAD is now at 0fc3888... fix for compiling on Apple iOS<br>
[ 31%] [ 32%] Performing update step (git fetch) for 'boost-fetch'<br>
No patch step for 'boost-fetch'<br>
HEAD is now at 0fc3888... fix for compiling on Apple iOS KiB/s<br>
[ 33%] No configure step for 'boost-fetch'2.21 MiB | 766 KiB/s<br>
[ 33%] No build step for 'boost-fetch'<br>
[ 34%] No install step for 'boost-fetch'<br>
[ 34%] Completed 'boost-fetch'<br>
[ 34%] Built target boost-fetch<br>
remote: Total 337730 (delta 267693), reused 336460 (delta 266951)<br>
Receiving objects: 100% (337730/337730), 93.51 MiB | 2.08 MiB/s, done.<br>
Resolving deltas: 100% (267693/267693), done.<br>
Checking out files: 100% (8565/8565), done.<br>
Note: checking out 'ce4a267'.<br>
<br>
You are in 'detached HEAD' state. You can look around, make experimental<br>
changes and commit them, and you can discard any commits you make in this<br>
state without impacting any branches by performing another checkout.<br>
<br>
If you want to create a new branch to retain commits you create, you may<br>
do so (now or later) by using -b with the checkout command again. Example:<br>
<br>
git checkout -b new_branch_name<br>
<br>
HEAD is now at ce4a267... Fix a problem when cross compiling using NMake.<br>
[ 35%] [ 35%] Performing update step (git fetch) for 'vtk-fetch'<br>
No patch step for 'vtk-fetch'<br>
HEAD is now at ce4a267... Fix a problem when cross compiling using NMake.<br>
[ 36%] No configure step for 'vtk-fetch'<br>
[ 36%] No build step for 'vtk-fetch'<br>
[ 36%] No install step for 'vtk-fetch'<br>
[ 37%] Completed 'vtk-fetch'<br>
[ 37%] Built target vtk-fetch<br>
make: *** [all] Error 2<br>
_______________________________________________<br>
Ves mailing list<br>
<a href="mailto:Ves@public.kitware.com" target="_blank">Ves@public.kitware.com</a><br>
<a href="http://public.kitware.com/cgi-bin/mailman/listinfo/ves" target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/ves</a><br>
</blockquote></div><br></div>
</blockquote></div><br></div></div><br></blockquote></div><br></div>
</blockquote></div><br></div></div><br></blockquote></div><br></div>