sergeyvl12 wrote:
could be true. But I think it is very big and complex, isn't it?
But my problem is not the decision for an IDE (though i would prefer an easy to use IDE), but how to get your or the "official" SDK working at all - in what IDE ever.
About 64Bit:
I get everything running (ARM, ARM-EABI as well as Emulator) on 32-Bit Ubuntu.
My "normal" system is 64-Bit OpenSuse and I would prefer to use this.
But, if I build for Emulator, I can not stable convince the gcc-system to
either:
-make a 64-Bit target, beacause of the (32-Bit) "libinkview.so"
or
-make a 32-bit target (adding "-m32" to gxx and gcc commandlines), because it always uses wrong libraries: sometimes it is the 64-Bit "glibc" (libgcc.a and some .o -files) that are wrong, sometimes it's libcurl.so. Adding -L\usr\lib or
-L\usr\lib32 does not solve this problem.
I got it running only once, when I renamed and replace the folder that contains the "libgcc.a" with the 32-Bit version. But after that, the cmake's check for a working gcc fails.
It's all in all does not seem easy to use the emulator on 64-Bit Systems.
Isn't there a posssibility to get a 64-Bit "libinkview.so" ??
Perhaps some kind of wrapper that is 64Bit but internally uses 32Bit-libinkview?