[Ves] New VES for Android configuration error?
Casey Goodlett
casey.goodlett at kitware.com
Fri Oct 11 10:20:55 EDT 2013
Sorry I had meant to say next instead of master.
Something like this is how I would normally use ccmake
http://www.vtk.org/Wiki/VTK/Building/Linux
I notice the VES android build instructions instruct the use of cmake
directly so there may be a subtlety I am not aware of.
On Fri, Oct 11, 2013 at 10:12 AM, Tom Panzarella <
tpanzarella at loveparkrobotics.com> wrote:
> Hi Casey,
>
> Thanks for the pointer. I'm not too familiar with using the CMake GUI
> interfaces. With respect to building VES, how would you invoke ccmake or
> cmake-gui to perform this configuration change?
>
> Also, I did another checkout from master and tried to build per the normal
> instructions (based on your earlier email about trying again). It results
> in the same `android-curl` related error.
>
> FWIW, my other build is still going with no problems...
>
> Best,
> Tom
>
>
> On 10/11/2013 10:05 AM, Casey Goodlett wrote:
>
>> Hi Tom,
>>
>> Those values only setup the default options for cmake. Its better if
>> you configure those values when using ccmake or cmake-gui then to modify
>> the hard-coded values in the CMakeLists.txt
>>
>> Thanks
>>
>>
>> On Fri, Oct 11, 2013 at 10:04 AM, Tom Panzarella
>> <tpanzarella at loveparkrobotics.**com <tpanzarella at loveparkrobotics.com>
>> <mailto:tpanzarella@**loveparkrobotics.com<tpanzarella at loveparkrobotics.com>>>
>> wrote:
>>
>> Thank you Casey, it seems to be working.
>>
>> For those following along, here is a diff to do what Casey suggests:
>>
>> [ ~/dev/android/VES/CMake ]
>> tpanzarella at jelly: $ git diff
>> diff --git a/CMake/ves-superbuild.cmake b/CMake/ves-superbuild.cmake
>> index c5a034f..005abb9 100644
>> --- a/CMake/ves-superbuild.cmake
>> +++ b/CMake/ves-superbuild.cmake
>> @@ -2,8 +2,8 @@ project(VES_SUPERBUILD NONE)
>>
>> include(ExternalProject)
>>
>> -option(VES_USE_LIBARCHIVE "Should VES include libarchive support" ON)
>> -option(VES_USE_CURL "Should VES include cURL support" ON)
>> +option(VES_USE_LIBARCHIVE "Should VES include libarchive support"
>> OFF)
>> +option(VES_USE_CURL "Should VES include cURL support" OFF)
>> option(VES_USE_PCL "Should VES include PCL support" OFF)
>> set(PCL_SUPERBUILD_DIR "PCL_SUPERBUILD_DIR-NOTFOUND" CACHE PATH
>> "Directory containing CMakeExternals/Install with PCL and its
>> dependencies")
>>
>> The code is currently building for me.
>>
>> Thanks,
>> Tom
>>
>>
>> On 10/11/2013 09:59 AM, Casey Goodlett wrote:
>>
>> For now you can work around by disabling curl and libarchive when
>> building for android.
>>
>>
>> On Fri, Oct 11, 2013 at 9:55 AM, Tom Panzarella
>> <tpanzarella at loveparkrobotics.**__com
>> <mailto:tpanzarella@**loveparkrobotics.com<tpanzarella at loveparkrobotics.com>
>> >
>> <mailto:tpanzarella at __lovepark**robotics.com<http://loveparkrobotics.com>
>>
>> <mailto:tpanzarella@**loveparkrobotics.com<tpanzarella at loveparkrobotics.com>>>>
>> wrote:
>>
>> Hi,
>>
>> I'm not sure what errors you are encountering but I am also
>> having
>> trouble building the code from a fresh VES checkout. Here
>> is what I get:
>>
>> tpanzarella at jelly: $ cmake -P configure.cmake
>> CMake Error at
>> /usr/share/cmake-2.8/Modules/_**___ExternalProject.cmake:718
>>
>> (get_property):
>>
>>
>> get_property could not find TARGET curl-android.
>> Perhaps it has
>> not yet
>> been created.
>> Call Stack (most recent call first):
>> /usr/share/cmake-2.8/Modules/_**
>> ___ExternalProject.cmake:932
>> (ExternalProject_Get_Property)
>> /usr/share/cmake-2.8/Modules/_**
>> ___ExternalProject.cmake:1488
>> (_ep_get_step_stampfile)
>> /usr/share/cmake-2.8/Modules/_**
>> ___ExternalProject.cmake:1702
>>
>>
>> (_ep_add_configure_command)
>>
>> CMake/ves-superbuild.cmake:337 (ExternalProject_Add)
>> CMake/ves-superbuild.cmake:390 (crosscompile_ves)
>> CMakeLists.txt:3 (include)
>>
>>
>> CMake Error at
>> /usr/share/cmake-2.8/Modules/_**___ExternalProject.cmake:720
>>
>> (message):
>>
>>
>> External project "curl-android" has no stamp_dir
>> Call Stack (most recent call first):
>> /usr/share/cmake-2.8/Modules/_**
>> ___ExternalProject.cmake:932
>> (ExternalProject_Get_Property)
>> /usr/share/cmake-2.8/Modules/_**
>> ___ExternalProject.cmake:1488
>> (_ep_get_step_stampfile)
>> /usr/share/cmake-2.8/Modules/_**
>> ___ExternalProject.cmake:1702
>>
>>
>> (_ep_add_configure_command)
>>
>> CMake/ves-superbuild.cmake:337 (ExternalProject_Add)
>> CMake/ves-superbuild.cmake:390 (crosscompile_ves)
>> CMakeLists.txt:3 (include)
>>
>>
>> -- Configuring incomplete, errors occurred!
>>
>> Any help is greatly appreciated.
>>
>> Best,
>> Tom
>>
>>
>> On 10/11/2013 09:40 AM, DEB63 at pitt.edu
>> <mailto:DEB63 at pitt.edu> <mailto:DEB63 at pitt.edu
>>
>> <mailto:DEB63 at pitt.edu>> wrote:
>>
>> Hi
>>
>> You mentioned below to try the current master. These
>> Android
>> configuration errors appear to be happening on the master
>> branch.....
>> Here is what I get, as I type the following, to perform
>> a fresh
>> build from
>> the command prompt...
>> - - - - - - -
>> { ~ }-> git clone git://vtk.org/VES.git
>> <http://vtk.org/VES.git> <http://vtk.org/VES.git>
>>
>>
>> Cloning into 'VES'...
>> remote: Counting objects: 9593, done.
>> remote: Compressing objects: 100% (2998/2998), done.
>> remote: Total 9593 (delta 6433), reused 9525 (delta 6391)
>> Receiving objects: 100% (9593/9593), 26.32 MiB | 8.86
>> MiB/s, done.
>> Resolving deltas: 100% (6433/6433), done.
>> { ~ }-> cd VES
>> { ~/VES }-> git branch
>> * master < < < < < On the master
>> branch < < <
>> { ~/VES }-> cd Apps/Android/CmakeBuild
>> { ~/VES/Apps/Android/CmakeBuild }-> cmake -P
>> configure.cmake
>>
>> [> > > > >(after a bunch of journal lines...)< < < < ]
>>
>> -- Configuring incomplete, errors occurred! < <
>> < Error <
>> < <
>> { ~/VES/Apps/Android/CmakeBuild }->
>>
>> - - - - - -
>> Thanks
>> Dave
>>
>>
>>
>>
>> On Wed, Oct 9, 2013 at 8:00 AM, Casey Goodlett
>> <casey.goodlett at kitware.com
>> <mailto:casey.goodlett@**kitware.com <casey.goodlett at kitware.com>
>> >
>> <mailto:casey.goodlett at __kitwa**re.com<http://kitware.com>
>>
>> <mailto:casey.goodlett@**kitware.com <casey.goodlett at kitware.com>
>> >>>__wrote:
>>
>>
>> Aashish,
>>
>> I think we also have problems on the VES
>> dashboard. I
>> think there may
>> be
>> a problem with android builds with curl and
>> libarchive
>> enabled.
>>
>>
>> I see. I can look into it today if you haven't done
>> it
>> already. Thanks for
>> pointing it out.
>>
>> - Aashish
>>
>>
>>
>>
>> On Tue, Oct 8, 2013 at 12:58 PM, Aashish
>> Chaudhary <
>> aashish.chaudhary at kitware.com <mailto:aashish.chaudhary@**
>> kitware.com <aashish.chaudhary at kitware.com>>
>> <mailto:aashish.chaudhary at __ki**tware.com<http://kitware.com>
>>
>> <mailto:aashish.chaudhary@**kitware.com<aashish.chaudhary at kitware.com>>>>
>> wrote:
>>
>> Could you please try the current master. We
>> have
>> done quite a bit of
>> work
>> on resolving most of the build issues and
>> most of
>> these changes are in
>> master now.
>>
>> - Aashish
>>
>>
>>
>> On Tue, Oct 8, 2013 at 12:44 PM,
>> <DEB63 at pitt.edu <mailto:DEB63 at pitt.edu>
>> <mailto:DEB63 at pitt.edu
>>
>> <mailto:DEB63 at pitt.edu>>> wrote:
>>
>> Hi
>>
>> I tried to download/setup a fresh
>> installation
>> of VES for Android for
>> a
>> project that I have been working on -
>> specifically using the
>> kiwi-next-apps-resolved-next branch.
>> However,
>> after trying to build
>> my
>> code with the new download, I ended up
>> getting
>> some link errors...
>> errors
>> that were never there before...
>>
>> "undefined reference to
>>
>> `vesKiwiDataLoader::____**setErrorOnMoreThan65kVertices(**
>> ____bool)'
>>
>>
>>
>> I will note that this code will build
>> correctly
>> using a VES install I
>> did
>> 2-3 weeks ago.
>>
>> In an effort to track down the problem,
>> I tried
>> to perform a clean
>> superbuild for Android... as per the
>> basic setup
>> instructions...
>> $ export
>>
>> ANDROID_NDK=/path/to/____**installed/android-ndk
>>
>>
>> $ cd Apps/Android/CMakeBuild
>> $ cmake -P configure.cmake
>> $ cd build
>> $ make -j4
>>
>> however, the cmake -P configure.cmake
>> now produces some errors, such as:
>>
>>
>> { ~/VES/Apps/Android/CMakeBuild }->
>> cmake -P
>> configure.cmake
>> -- Found PythonInterp: /usr/bin/python
>> (found
>> version "2.7.2")
>> -- Found Git: /usr/bin/git (found version
>> "1.7.12.4 (Apple Git-37)")
>> CMake Error at /Applications/CMake
>>
>> 2.8-10.app/Contents/share/____**cmake-2.8/Modules/____**
>> ExternalProject.cmake:718
>>
>>
>> (get_property):
>> get_property could not find TARGET
>> curl-android. Perhaps it has not
>> yet
>> been created.
>> Call Stack (most recent call first):
>> /Applications/CMake
>>
>> 2.8-10.app/Contents/share/____**cmake-2.8/Modules/____**
>> ExternalProject.cmake:932
>> (ExternalProject_Get_Property)
>> /Applications/CMake
>>
>> 2.8-10.app/Contents/share/____**cmake-2.8/Modules/____**
>> ExternalProject.cmake:1488
>> (_ep_get_step_stampfile)
>> /Applications/CMake
>>
>> 2.8-10.app/Contents/share/____**cmake-2.8/Modules/____**
>> ExternalProject.cmake:1702
>>
>>
>> (_ep_add_configure_command)
>> CMake/ves-superbuild.cmake:337
>> (ExternalProject_Add)
>> CMake/ves-superbuild.cmake:390
>> (crosscompile_ves)
>> CMakeLists.txt:3 (include)
>>
>>
>> CMake Error at /Applications/CMake
>>
>> 2.8-10.app/Contents/share/____**cmake-2.8/Modules/____**
>> ExternalProject.cmake:720
>>
>>
>> (message):
>> External project "curl-android" has
>> no stamp_dir
>> Call Stack (most recent call first):
>> /Applications/CMake
>>
>> 2.8-10.app/Contents/share/____**cmake-2.8/Modules/____**
>> ExternalProject.cmake:932
>> (ExternalProject_Get_Property)
>> /Applications/CMake
>>
>> 2.8-10.app/Contents/share/____**cmake-2.8/Modules/____**
>> ExternalProject.cmake:1488
>> (_ep_get_step_stampfile)
>> /Applications/CMake
>>
>> 2.8-10.app/Contents/share/____**cmake-2.8/Modules/____**
>> ExternalProject.cmake:1702
>>
>>
>> (_ep_add_configure_command)
>> CMake/ves-superbuild.cmake:337
>> (ExternalProject_Add)
>> CMake/ves-superbuild.cmake:390
>> (crosscompile_ves)
>> CMakeLists.txt:3 (include)
>>
>>
>> -- Configuring incomplete, errors
>> occurred!
>>
>> <<<<<<<<
>>
>> Any suggestions?
>>
>> Thanks
>> Dave
>>
>>
>>
>> ______________________________**_____________________
>>
>> Ves mailing list
>> Ves at public.kitware.com <mailto:Ves at public.kitware.com**>
>> <mailto:Ves at public.kitware.com
>> <mailto:Ves at public.kitware.com**>__>
>> http://public.kitware.com/cgi-**____bin/mailman/listinfo/ves<http://public.kitware.com/cgi-____bin/mailman/listinfo/ves>
>> <http://public.kitware.com/**cgi-__bin/mailman/listinfo/ves<http://public.kitware.com/cgi-__bin/mailman/listinfo/ves>
>> **>
>>
>>
>> <http://public.kitware.com/__**cgi-bin/mailman/listinfo/ves<http://public.kitware.com/__cgi-bin/mailman/listinfo/ves>
>>
>> <http://public.kitware.com/**cgi-bin/mailman/listinfo/ves<http://public.kitware.com/cgi-bin/mailman/listinfo/ves>
>> >>
>>
>>
>>
>>
>> --
>> | Aashish Chaudhary
>> | R&D Engineer
>> | Kitware Inc.
>> | www.kitware.com <http://www.kitware.com>
>> <http://www.kitware.com>
>>
>>
>> ______________________________**_____________________
>>
>> Ves mailing list
>> Ves at public.kitware.com <mailto:Ves at public.kitware.com**>
>> <mailto:Ves at public.kitware.com <mailto:Ves at public.kitware.com**
>> >__>
>> http://public.kitware.com/cgi-**____bin/mailman/listinfo/ves<http://public.kitware.com/cgi-____bin/mailman/listinfo/ves>
>> <http://public.kitware.com/**cgi-__bin/mailman/listinfo/ves<http://public.kitware.com/cgi-__bin/mailman/listinfo/ves>
>> **>
>>
>>
>> <http://public.kitware.com/__**cgi-bin/mailman/listinfo/ves<http://public.kitware.com/__cgi-bin/mailman/listinfo/ves>
>>
>> <http://public.kitware.com/**cgi-bin/mailman/listinfo/ves<http://public.kitware.com/cgi-bin/mailman/listinfo/ves>
>> >>
>>
>>
>>
>>
>> --
>> Casey B. Goodlett, Ph.D.
>> R&D Engineer
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> (919) 969-6990 x310 <tel:%28919%29%20969-6990%**20x310>
>> <tel:%28919%29%20969-6990%__**20x310>
>>
>>
>>
>>
>>
>>
>> --
>> | Aashish Chaudhary
>> | R&D Engineer
>> | Kitware Inc.
>> | www.kitware.com <http://www.kitware.com>
>> <http://www.kitware.com>
>> ______________________________**
>> _____________________
>>
>> Ves mailing list
>> Ves at public.kitware.com <mailto:Ves at public.kitware.com**>
>> <mailto:Ves at public.kitware.com <mailto:Ves at public.kitware.com**
>> >__>
>> http://public.kitware.com/cgi-**____bin/mailman/listinfo/ves<http://public.kitware.com/cgi-____bin/mailman/listinfo/ves>
>> <http://public.kitware.com/**cgi-__bin/mailman/listinfo/ves<http://public.kitware.com/cgi-__bin/mailman/listinfo/ves>
>> **>
>>
>> <http://public.kitware.com/__**cgi-bin/mailman/listinfo/ves<http://public.kitware.com/__cgi-bin/mailman/listinfo/ves>
>> <http://public.kitware.com/**cgi-bin/mailman/listinfo/ves<http://public.kitware.com/cgi-bin/mailman/listinfo/ves>
>> >>
>>
>>
>> ______________________________**_____________________
>>
>> Ves mailing list
>> Ves at public.kitware.com <mailto:Ves at public.kitware.com**>
>> <mailto:Ves at public.kitware.com <mailto:Ves at public.kitware.com**
>> >__>
>> http://public.kitware.com/cgi-**____bin/mailman/listinfo/ves<http://public.kitware.com/cgi-____bin/mailman/listinfo/ves>
>> <http://public.kitware.com/**cgi-__bin/mailman/listinfo/ves<http://public.kitware.com/cgi-__bin/mailman/listinfo/ves>
>> **>
>>
>> <http://public.kitware.com/__**cgi-bin/mailman/listinfo/ves<http://public.kitware.com/__cgi-bin/mailman/listinfo/ves>
>> <http://public.kitware.com/**cgi-bin/mailman/listinfo/ves<http://public.kitware.com/cgi-bin/mailman/listinfo/ves>
>> >>
>>
>> ______________________________**_____________________
>>
>> Ves mailing list
>> Ves at public.kitware.com <mailto:Ves at public.kitware.com**>
>> <mailto:Ves at public.kitware.com <mailto:Ves at public.kitware.com**
>> >__>
>> http://public.kitware.com/cgi-**____bin/mailman/listinfo/ves<http://public.kitware.com/cgi-____bin/mailman/listinfo/ves>
>> <http://public.kitware.com/**cgi-__bin/mailman/listinfo/ves<http://public.kitware.com/cgi-__bin/mailman/listinfo/ves>
>> **>
>>
>> <http://public.kitware.com/__**cgi-bin/mailman/listinfo/ves<http://public.kitware.com/__cgi-bin/mailman/listinfo/ves>
>>
>> <http://public.kitware.com/**cgi-bin/mailman/listinfo/ves<http://public.kitware.com/cgi-bin/mailman/listinfo/ves>
>> >>
>>
>>
>>
>>
>> --
>> Casey B. Goodlett, Ph.D.
>> R&D Engineer
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> (919) 969-6990 x310 <tel:%28919%29%20969-6990%**20x310>
>>
>>
>>
>>
>> --
>> Casey B. Goodlett, Ph.D.
>> R&D Engineer
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> (919) 969-6990 x310
>>
>
--
Casey B. Goodlett, Ph.D.
R&D Engineer
Kitware, Inc. - North Carolina Office
http://www.kitware.com
(919) 969-6990 x310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ves/attachments/20131011/9975b6f1/attachment-0001.html>
More information about the Ves
mailing list