Closed nithins closed 8 years ago
The solution is very simple :) -- don't build for 32 bit mode. This issue has already been discussed here many times, and it's really not a nanogui problem, so I'll close this ticket.
Ouch, ok. I didn't spot any ticket/issue that said so. My bad. I'm forced to use 32bit, so I'll stick to my solution. Thanks for the great code anyway. :)
On Mon, Jul 25, 2016 at 11:48 PM Wenzel Jakob notifications@github.com wrote:
The solution is very simple :) -- don't build for 32 bit mode. This issue has already been discussed here many times, and it's really not a nanogui problem, so I'll close this ticket.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wjakob/nanogui/issues/90#issuecomment-235037702, or mute the thread https://github.com/notifications/unsubscribe-auth/AAMNSpZdLHEoSSbBwwiqQmdqKayu8xDLks5qZP3EgaJpZM4JUXlE .
An runtime crash with win32 apps using nanogui (with IGL) crops up with VS2015 (Haven't tested on other versions).
Specifically, I managed to trace the issue to the definition of the color definition in common.h . The problem and the quickfix suggested here solves this problem. Particularly, adding a compiler "-DEIGEN_DONT_ALIGN_STATICALLY" .
But, I imagine that this flag should NOT be used for optimal Eigen code and is a problem when mixing computational code with the viewer.