I have the OMAPL137EVM board.
I want to use RTTI (dynamic_cast) in my C++ project.
I use NDK also.
Should I rebuild NDK libraries with the --rtti key?
Does the speed penalty using RTTI is much sufficient?
Best regards,
Yuriy
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I have the OMAPL137EVM board.
I want to use RTTI (dynamic_cast) in my C++ project.
I use NDK also.
Should I rebuild NDK libraries with the --rtti key?
Does the speed penalty using RTTI is much sufficient?
Best regards,
Yuriy
Yuriy,
Yuriy Kubasov said:Should I rebuild NDK libraries with the --rtti key?
Yes. Check the reference below:
Yuriy Kubasov said:Does the speed penalty using RTTI is much sufficient?
Since NDK was never tested with RTTI enabled, I don't have a conclusive answer but just some comments:
Since all the time-based functions of NDK are based on DSP/BIOS timers, I don't foresee a functional problem with the code overhead that RTTI will add - in other words, it should work. However, I would expect some performance loss especially if you need high throughput. At last, make sure that DSP/BIOS libraries have RTTI support enabled - I am not sure if they currently have this option, though.
Best regards,
Rafael