[Ves] ndk-build NDK_DEBUG=1

Ariel Hernán Curiale curiale at gmail.com
Wed Nov 21 04:22:51 EST 2012


Hi Pat,

Thanks for your reply. I was a bit confused. I'll try to split the .h into the class definition and the macro (.cpp) to avoid the multiples redefinitions when I use it to import form the two natives codes.


Thanks,
__________________________________
| Ariel Hernán Curiale Ph.D Student
| ETSI Telecomunicación
| Universidad de Valladolid
| Campus Miguel Delibes
| 47011 Valladolid, Spain
| Phone: 983-423000 ext. 5590
| Web: www.curiale.com.ar
|_________________________________

El 21/11/2012, a las 00:52, Pat Marion escribió:

> Hi Ariel,
> 
> vtkStandardNewMacro() is used in all VTK class definitions, it generates the New() and Delete() methods that are VTK's way of handling reference counting.  The macro is defined in vtkSetGet.h.
> 
> You say that you don't know how to use the vtkAndroidOutputWindow.h, what's the problem?  It is used to route VTK logging messages to the Android logger.  You should create one instance of it when you initialize the app.  You should avoid creating multiple instances of it, but I don't think it would break anything even if you did.
> 
> Pat
> 
> 
> On Mon, Nov 19, 2012 at 8:06 PM, Ariel Hernán Curiale <curiale at gmail.com> wrote:
> Thanks Pat, I will see its during the weekend.
> 
> I've had another doubt about how to merge four different types of view in the app. I want to merge three 2D  (axial, coronal and sagittal) views  and one 3D.
> I'm thinking to use four different vesKiwiViewerApp but I don't know how to use the vtkAndroidOutputWindow.h provided by the Kiwi App and what is really the function of the vtkStandardNewMacro(vtkAndroidOutputWindow) macro.
> 
> If you could give me some tips about how I have to do this it will be great.
> 
> 
> Saludos
> __________________________________
> | Ariel Hernán Curiale Ph.D Student
> | ETSI Telecomunicación
> | Universidad de Valladolid
> | Campus Miguel Delibes
> | 47011 Valladolid, Spain
> | Phone: 983-423000 ext. 5590
> | Web: www.curiale.com.ar
> |_________________________________
> 
> El 19/11/2012, a las 08:53, Pat Marion escribió:
> 
>> Hi Ariel,
>> 
>> You should use CMAKE_BUILD_TYPE=Debug, which will pass the CMAKE_CXX_FLAGS_DEBUG to the compiler.  If you need to add additional flags, you can modify that variable.  If you want to debug native code on android using the ndk gdb, you could try following some tutorials like this one:  http://vilimpoc.org/blog/2010/09/23/hello-gdbserver-a-debuggable-jni-example-for-android/
>> 
>> Pat
>> 
>> On Sun, Nov 18, 2012 at 5:22 AM, Ariel Hernán Curiale <curiale at gmail.com> wrote:
>> Hi all,
>> 
>> I did a native library and I want to debug it. I know how to do this using eclipse and Android.mk but using VES I have some scripts to create and configure the project . Also, I have some CMakeLists.txt and I don't know how to set properly the debugger.
>> 
>> I tried to set using the flag CMAKE_BUILD_TYPE (-DCMAKE_BUILD_TYPE="Debug") but nothing.
>> 
>> 
>> If anyone knows how to debug a native library built using VES please tell me how can I debug it.
>> 
>> Thanks,
>> __________________________________
>> | Ariel Hernán Curiale Ph.D Student
>> | ETSI Telecomunicación
>> | Universidad de Valladolid
>> | Campus Miguel Delibes
>> | 47011 Valladolid, Spain
>> | Phone: 983-423000 ext. 5590
>> | Web: www.curiale.com.ar
>> |_________________________________
>> 
>> 
>> _______________________________________________
>> Ves mailing list
>> Ves at public.kitware.com
>> http://public.kitware.com/cgi-bin/mailman/listinfo/ves
>> 
>> 
> 
> 
> _______________________________________________
> 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/20121121/fcd9b83f/attachment-0001.html>


More information about the Ves mailing list