[Ves] Build VES Android on Windows

Vincent Kaestle vincent.kaestle at gmail.com
Mon Apr 14 11:18:50 EDT 2014


Hello,

Do you have any progress in this issue ?

Thank you,
Vincent


2014-04-02 10:07 GMT+02:00 Vincent Kaestle <vincent.kaestle at gmail.com>:

> Hello Aashish,
>
> It was already how I sent the apk file to the device. I'm using ndk-r9c.
>
> Thanks,
> Vincent Kaestle
>
>
> 2014-04-02 3:16 GMT+02:00 Aashish Chaudhary <aashish.chaudhary at kitware.com
> >:
>
> Dear Vincent,
>>
>> Can you try this for me? Once your build APK, can you manually copy it to
>> the device?
>>
>> adb install -r path_to_kiwi_apk?
>>
>> Thanks,
>>
>>
>>
>> On Tue, Apr 1, 2014 at 4:08 AM, Vincent Kaestle <
>> vincent.kaestle at gmail.com> wrote:
>>
>>> Hi Aashish,
>>>
>>> Ok, I'm glad that it's a known issue. Thank you
>>>
>>>
>>> 2014-03-29 2:57 GMT+01:00 Aashish Chaudhary <
>>> aashish.chaudhary at kitware.com>:
>>>
>>> Hi Vincent,
>>>>
>>>> We had seen the same as well. It is somewhat related with recent
>>>> version of NDK. Let me look into it and I will get back to you sometime
>>>> soon.
>>>> I believe it is something to do with matrix data corruption but I have
>>>> to test my theory.
>>>>
>>>> - Aashish
>>>>
>>>>
>>>> On Fri, Mar 28, 2014 at 11:33 AM, Vincent Kaestle <
>>>> vincent.kaestle at gmail.com> wrote:
>>>>
>>>>> If I can continue to bother you.. Now, I've a problem with KiwiViewer.
>>>>> I compiled KiwiViewer. And I pushed it on a tablet Nexus 10 with
>>>>> Android 4.4.2.
>>>>> It looks like the resizing of image isn't correct. In attchment,
>>>>> you'll find the thinest teepot you ever saw.
>>>>>
>>>>>
>>>>> 2014-03-28 15:44 GMT+01:00 Aashish Chaudhary <
>>>>> aashish.chaudhary at kitware.com>:
>>>>>
>>>>>
>>>>>> On Fri, Mar 28, 2014 at 9:29 AM, Vincent Kaestle <
>>>>>> vincent.kaestle at gmail.com> wrote:
>>>>>>
>>>>>>> Finally I made it works by using nmake in a Visual Studio command
>>>>>>> prompt.
>>>>>>> Sorry for this inconvience.
>>>>>>>
>>>>>>
>>>>>> No problem. Glad that it worked for you. I thought you were already
>>>>>> using the VS command prompt.
>>>>>>
>>>>>> - Aashish
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2014-03-28 12:04 GMT+01:00 Vincent Kaestle <
>>>>>>> vincent.kaestle at gmail.com>:
>>>>>>>
>>>>>>> I've also tried something which works better :
>>>>>>>>
>>>>>>>>    - ninja
>>>>>>>>    - specific C&CXX compiler = MinGW/bin/mingw32-gcc.exe &
>>>>>>>>    MinGW/bin/mingw32-g++.exe
>>>>>>>>    - check VES_ANDROID_SUPERBUILD
>>>>>>>>
>>>>>>>> But build stops during build step for 'vtk-android' with this error
>>>>>>>> :
>>>>>>>> FAILED :
>>>>>>>> D:\android-ndk-r9c\toolchains\arm-linux-androideabi-4.8\prebuilt\windows-x86_64\lesvtkCommonCore.dirvtkAbstractArray.cxx.o:
>>>>>>>> No such file or directory
>>>>>>>>
>>>>>>>> Find attached the vtk-android/CMakeError.log file.
>>>>>>>>
>>>>>>>>
>>>>>>>> 2014-03-28 10:06 GMT+01:00 Vincent Kaestle <
>>>>>>>> vincent.kaestle at gmail.com>:
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> But if I don't select toolchain, it uses the compiler of VS10 :
>>>>>>>>> VC/bin/cl.exe
>>>>>>>>> And then I have an error during vtk-host build :
>>>>>>>>>
>>>>>>>>> Compiling the C compiler identification source file
>>>>>>>>>> "CMakeCCompilerId.c" failed.
>>>>>>>>>> Compiler: C:/Program Files (x86)/Microsoft Visual Studio
>>>>>>>>>> 10.0/VC/bin/cl.exe
>>>>>>>>>> Build flags:
>>>>>>>>>> Id flags:
>>>>>>>>>>
>>>>>>>>>> The output was:
>>>>>>>>>> Exit code 0xc0000135
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Compiling the C compiler identification source file
>>>>>>>>>> "CMakeCCompilerId.c" failed.
>>>>>>>>>> Compiler: C:/Program Files (x86)/Microsoft Visual Studio
>>>>>>>>>> 10.0/VC/bin/cl.exe
>>>>>>>>>> Build flags:
>>>>>>>>>> Id flags: -c
>>>>>>>>>>
>>>>>>>>>> The output was:
>>>>>>>>>> Exit code 0xc0000135
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Compiling the C compiler identification source file
>>>>>>>>>> "CMakeCCompilerId.c" failed.
>>>>>>>>>> Compiler: C:/Program Files (x86)/Microsoft Visual Studio
>>>>>>>>>> 10.0/VC/bin/cl.exe
>>>>>>>>>> Build flags:
>>>>>>>>>> Id flags: -Aa
>>>>>>>>>>
>>>>>>>>>> The output was:
>>>>>>>>>> Exit code 0xc0000135
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Checking whether the C compiler is IAR using "" did not match
>>>>>>>>>> "IAR .+ Compiler":
>>>>>>>>>> Compiling the CXX compiler identification source file
>>>>>>>>>> "CMakeCXXCompilerId.cpp" failed.
>>>>>>>>>> Compiler: C:/Program Files (x86)/Microsoft Visual Studio
>>>>>>>>>> 10.0/VC/bin/cl.exe
>>>>>>>>>> Build flags:
>>>>>>>>>> Id flags:
>>>>>>>>>>
>>>>>>>>>> The output was:
>>>>>>>>>> Exit code 0xc0000135
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Compiling the CXX compiler identification source file
>>>>>>>>>> "CMakeCXXCompilerId.cpp" failed.
>>>>>>>>>> Compiler: C:/Program Files (x86)/Microsoft Visual Studio
>>>>>>>>>> 10.0/VC/bin/cl.exe
>>>>>>>>>> Build flags:
>>>>>>>>>> Id flags: -c
>>>>>>>>>>
>>>>>>>>>> The output was:
>>>>>>>>>> Exit code 0xc0000135
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Checking whether the CXX compiler is IAR using "" did not match
>>>>>>>>>> "IAR .+ Compiler":
>>>>>>>>>> Determining if the C compiler works failed with the following
>>>>>>>>>> output:
>>>>>>>>>> Change Dir:
>>>>>>>>>> D:/VES/VES_next/Apps/Android/CMakeBuild/build/CMakeExternals/Build/vtk-host/CMakeFiles/CMakeTmp
>>>>>>>>>>
>>>>>>>>>> Run Build Command:nmake /NOLOGO  "cmTryCompileExec227739764\fast"
>>>>>>>>>>     "C:\Program Files (x86)\Microsoft Visual Studio
>>>>>>>>>> 10.0\VC\bin\nmake.exe" -f
>>>>>>>>>> CMakeFiles\cmTryCompileExec227739764.dir\build.make /nologo
>>>>>>>>>> -L                  CMakeFiles\cmTryCompileExec227739764.dir\build
>>>>>>>>>>
>>>>>>>>>>     "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E
>>>>>>>>>> cmake_progress_report
>>>>>>>>>> D:\VES\VES_next\Apps\Android\CMakeBuild\build\CMakeExternals\Build\vtk-host\CMakeFiles\CMakeTmp\CMakeFiles
>>>>>>>>>> 1
>>>>>>>>>>
>>>>>>>>>> Building C object
>>>>>>>>>> CMakeFiles/cmTryCompileExec227739764.dir/testCCompiler.c.obj
>>>>>>>>>>
>>>>>>>>>>     C:\PROGRA~2\MICROS~1.0\VC\bin\cl.exe    -o
>>>>>>>>>> CMakeFiles\cmTryCompileExec227739764.dir\testCCompiler.c.obj   -c
>>>>>>>>>> D:\VES\VES_next\Apps\Android\CMakeBuild\build\CMakeExternals\Build\vtk-host\CMakeFiles\CMakeTmp\testCCompiler.c
>>>>>>>>>>
>>>>>>>>>> NMAKE : fatal error U1077:
>>>>>>>>>> 'C:\PROGRA~2\MICROS~1.0\VC\bin\cl.exe' : code retour '0xc0000135'
>>>>>>>>>>
>>>>>>>>>> Stop.
>>>>>>>>>>
>>>>>>>>>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft
>>>>>>>>>> Visual Studio 10.0\VC\bin\nmake.exe"' : code retour '0x2'
>>>>>>>>>>
>>>>>>>>>> Stop.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Please find attached a screenshot of CMake-Gui config. (I kept the
>>>>>>>>> same build directory, but I deleted its content and the cache before)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2014-03-27 18:19 GMT+01:00 Aashish Chaudhary <
>>>>>>>>> aashish.chaudhary at kitware.com>:
>>>>>>>>>
>>>>>>>>> You first have to build superbuild.
>>>>>>>>>>
>>>>>>>>>> - source code setting seems  right
>>>>>>>>>> - set build to some other directory
>>>>>>>>>> - you don't want to select toolchain
>>>>>>>>>> - check VES_ANDROID_SUPERBUILD
>>>>>>>>>> - configure
>>>>>>>>>> - generate
>>>>>>>>>>
>>>>>>>>>> exit and then run nmake
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, Mar 27, 2014 at 12:05 PM, Vincent Kaestle <
>>>>>>>>>> vincent.kaestle at gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> I'm traying to build VES for Android on a Windows 7. I have some
>>>>>>>>>>> problems, you may help me.
>>>>>>>>>>>
>>>>>>>>>>> What I did is :
>>>>>>>>>>>
>>>>>>>>>>>    - start CMake-Gui
>>>>>>>>>>>    - set "source code" to VES root
>>>>>>>>>>>    - set "build" to Apps/Android/CMakeBuild/build
>>>>>>>>>>>    - *configure* with NMake and select
>>>>>>>>>>>    toolchain=CMake/toolchains/android.toolchain.cmake
>>>>>>>>>>>    - check "VES_ANDROID_SUPERBUILD"
>>>>>>>>>>>    - *generate*
>>>>>>>>>>>    - then go to the build dir and launch *nmake*
>>>>>>>>>>>
>>>>>>>>>>> During vtk-host build, it stopped because it didn't find the
>>>>>>>>>>> compiler. To solve it, I added in macro(compile_vtk proj) of
>>>>>>>>>>> ves-superbuild.cmake a CMAKE_ARGS :
>>>>>>>>>>> -DCMAKE_TOOLCHAIN_FILE:FILEPATH=${CMAKE_TOOLCHAIN_FILE}
>>>>>>>>>>>
>>>>>>>>>>> Then I rebuilt, but I got an other error during vtk-host build :
>>>>>>>>>>> Could not find a package configuration file provided by "
>>>>>>>>>>> *VTKCompileTools*" with any of the following names :
>>>>>>>>>>> *VTCompileToolsConfig.cmake* *vtkcompiletools-config.cmake*.
>>>>>>>>>>>
>>>>>>>>>>> Do you think I'm in the wrong way ?
>>>>>>>>>>>
>>>>>>>>>>> Thank you in advance,
>>>>>>>>>>> Best,
>>>>>>>>>>>
>>>>>>>>>>> Vi.
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Ves mailing list
>>>>>>>>>>> Ves at public.kitware.com
>>>>>>>>>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ves
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> | Aashish Chaudhary
>>>>>>>>>> | R&D Engineer
>>>>>>>>>> | Kitware Inc.
>>>>>>>>>> | www.kitware.com
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> | Aashish Chaudhary
>>>>>> | R&D Engineer
>>>>>> | Kitware Inc.
>>>>>> | www.kitware.com
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> | Aashish Chaudhary
>>>> | R&D Engineer
>>>> | Kitware Inc.
>>>> | www.kitware.com
>>>>
>>>
>>>
>>
>>
>> --
>> | Aashish Chaudhary
>> | R&D Engineer
>> | Kitware Inc.
>> | www.kitware.com
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ves/attachments/20140414/59c6669b/attachment-0002.html>


More information about the Ves mailing list