[vtk-developers] VES-Kiwi

[Cameron Lowell Palmer]

Well, I’m quite proud to say, it works, finally.

I can now set breakpoints in Eclipse! The scripting to pull the code into the right places is documented on my GitHub project:
https://github.com/palmerc/VES-Kiwi-NDK

I still need to clean this up further, do some better organization and apply it to our custom version, but I might actually meet my self imposed deadline to finish my first paper next month.

The work done here on VTK is super valuable. It would be a pity if it stays locked behind cmake.

From: Aashish Chaudhary <aashish.chaudhary at kitware.com<mailto:aashish.chaudhary at kitware.com>>
Date: mandag 27. oktober 2014 19.53
To: Cameron Lowell Palmer <cameron.palmer at ntnu.no<mailto:cameron.palmer at ntnu.no>>
Cc: Bill Hoffman <bill.hoffman at kitware.com<mailto:bill.hoffman at kitware.com>>, "vtk-developers at vtk.org<mailto:vtk-developers at vtk.org>" <vtk-developers at vtk.org<mailto:vtk-developers at vtk.org>>
Subject: Re: [vtk-developers] VES-Kiwi

FYI: Most (if not all) of the debugging we did was using command line tools (some of them generates stack trace which can be viewed in the eclipse plugin (specially the OpenGL ones).

- Aashish

On Mon, Oct 27, 2014 at 9:55 AM, Cameron Lowell Palmer <cameron.palmer at ntnu.no<mailto:cameron.palmer at ntnu.no>> wrote:
That is what I don¹t get, how was the original Kiwi C++ code debugged on
Android?

I would be happy if cmake could generate a Makefile that just output a
hierarchy of source and Android.mk files.



On 27.10.14, 14.28, "Bill Hoffman" <bill.hoffman at kitware.com<mailto:bill.hoffman at kitware.com>> wrote:

>On 10/25/2014 5:26 AM, Cameron Lowell Palmer wrote:
>>
>> Let me illustrate. https://www.youtube.com/watch?v=kjsC-lKUgM8 is a
>> video from Intel demonstrating debugging the NDK with Eclipse. This is a
>> great resource for getting started with this problem, but it is
>> unworkable because cmake creates a build directory with a project that
>> is effectively just a binary with no source. I think it is important to
>> address in the roadmap leveraging the Best Practices for the supported
>> targets.
>>
>> At least that is my current thinking.
>The idea would be to continue to enhance CMake to support the mobile
>IDEs better as time moves forward.  We need something that is seamless
>across windows, mac, and Linux, and works with iOS and Android.  Having
>to maintain N different IDE files in VTK will never work.   NVIDIA has
>been working on adding this type of support to CMake:
>
>http://www.cmake.org/pipermail/cmake-developers/2014-September/011308.html
>
>We worked some to get the build and debugging working with Eclipse here:
>http://www.kitware.com/blog/home/post/642
>
>Ditching CMake does not make sense for VTK, it is how VTK is developed.
>  CMake does need some enhancements to make it work better with mobile
>development environments.  Working on enhancing CMake would be a much
>better place to put effort than to have multiple build systems inside
>VTK-VES.
>
>-Bill
>
>
>--
>Bill Hoffman
>Kitware, Inc.
>28 Corporate Drive
>Clifton Park, NY 12065
>bill.hoffman at kitware.com<mailto:bill.hoffman at kitware.com>
>http://www.kitware.com
>518 881-4905<tel:518%20881-4905> (Direct)
>518 371-3971 x105<tel:518%20371-3971%20x105>
>Fax (518) 371-4573<tel:%28518%29%20371-4573>
>_______________________________________________
>Powered by www.kitware.com<http://www.kitware.com>
>
>Visit other Kitware open-source projects at
>http://www.kitware.com/opensource/opensource.html
>
>Follow this link to subscribe/unsubscribe:
>http://public.kitware.com/mailman/listinfo/vtk-developers
>

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/vtk-developers




--
| Aashish Chaudhary
| Technical Leader
| Kitware Inc.
| http://www.kitware.com/company/team/chaudhary.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20141027/711066be/attachment.html>