[Ves] Compiler error PCL for iOS

[Pat Marion]

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.

Pat


On Wed, Jun 12, 2013 at 3:59 AM, Christopher Herbon
<chrisherbon at gmail.com>wrote:

> Hi Pat,
>
> 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.
>
> Chris
>
>
>
>
> Am 11.06.2013 um 16:25 schrieb Pat Marion <pat.marion at kitware.com>:
>
> Hi Chris,
>
> 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:
>
> export ANDROID_NDK=/path/to/android-ndk-r8
>
> 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.
>
> Hope this helps!
>
> Pat
>
>
> On Tue, Jun 11, 2013 at 4:35 AM, Christopher Herbon <chrisherbon at gmail.com
> > wrote:
>
>> 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.
>>
>> 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?
>>
>>
>>
>> Am 10.06.2013 um 16:27 schrieb Pat Marion <pat.marion at kitware.com>:
>>
>> 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.
>>
>> 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?
>>
>> Pat
>>
>>
>> On Mon, Jun 10, 2013 at 10:03 AM, Christopher Herbon <
>> chrisherbon at gmail.com> wrote:
>>
>>> When following the guide (
>>> http://www.vtk.org/Wiki/VES/Point_Cloud_Library) 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.
>>>
>>> [ 30%] Completed 'ves-fetch'
>>> [ 30%] Built target ves-fetch
>>> remote: Total 32985 (delta 13679), reused 32985 (delta 13679)
>>> Receiving objects: 100% (32985/32985), 52.74 MiB | 956 KiB/s, done.
>>> Resolving deltas: 100% (13679/13679), done..99 MiB | 597 KiB/s
>>> Checking out files: 100% (31207/31207), done.9 MiB | 1.10 MiB/s
>>> Note: checking out 'origin/master'.730), 70.71 MiB | 960 KiB/s
>>>
>>> You are in 'detached HEAD' state. You can look around, make experimental
>>> changes and commit them, and you can discard any commits you make in this
>>> state without impacting any branches by performing another checkout.
>>>
>>> If you want to create a new branch to retain commits you create, you may
>>> do so (now or later) by using -b with the checkout command again.
>>> Example:
>>>
>>>   git checkout -b new_branch_name
>>>
>>> HEAD is now at 0fc3888... fix for compiling on Apple iOS
>>> [ 31%] [ 32%] Performing update step (git fetch) for 'boost-fetch'
>>> No patch step for 'boost-fetch'
>>> HEAD is now at 0fc3888... fix for compiling on Apple iOS KiB/s
>>> [ 33%] No configure step for 'boost-fetch'2.21 MiB | 766 KiB/s
>>> [ 33%] No build step for 'boost-fetch'
>>> [ 34%] No install step for 'boost-fetch'
>>> [ 34%] Completed 'boost-fetch'
>>> [ 34%] Built target boost-fetch
>>> remote: Total 337730 (delta 267693), reused 336460 (delta 266951)
>>> Receiving objects: 100% (337730/337730), 93.51 MiB | 2.08 MiB/s, done.
>>> Resolving deltas: 100% (267693/267693), done.
>>> Checking out files: 100% (8565/8565), done.
>>> Note: checking out 'ce4a267'.
>>>
>>> You are in 'detached HEAD' state. You can look around, make experimental
>>> changes and commit them, and you can discard any commits you make in this
>>> state without impacting any branches by performing another checkout.
>>>
>>> If you want to create a new branch to retain commits you create, you may
>>> do so (now or later) by using -b with the checkout command again.
>>> Example:
>>>
>>>   git checkout -b new_branch_name
>>>
>>> HEAD is now at ce4a267... Fix a problem when cross compiling using NMake.
>>> [ 35%] [ 35%] Performing update step (git fetch) for 'vtk-fetch'
>>> No patch step for 'vtk-fetch'
>>> HEAD is now at ce4a267... Fix a problem when cross compiling using NMake.
>>> [ 36%] No configure step for 'vtk-fetch'
>>> [ 36%] No build step for 'vtk-fetch'
>>> [ 36%] No install step for 'vtk-fetch'
>>> [ 37%] Completed 'vtk-fetch'
>>> [ 37%] Built target vtk-fetch
>>> make: *** [all] Error 2
>>> _______________________________________________
>>> Ves mailing list
>>> Ves at public.kitware.com
>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ves
>>>
>>
>>
>>
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ves/attachments/20130612/c07dcd6c/attachment-0002.html>