: a) cpu -amd64, 64-bit cblfs linux, kernel-2.6.38.2 Microwindows is 64-bit clean for the nano-X api and all nano-X applications, which I assume you're using. Win32 applications using older constructs like SetWindowLong have some issues with offsets and pointer lengths, but these aren't portable in Win32 without modifying the storage to always allocate space for 64 bit pointers at all times. Win32 apps can be fixed with no modifications by compiling for 32 bits.
> gcc-4.5.2, I haven't tested with this but don't forsee any problems, as most changes in gcc are in C++ not C. : b) freetype -2.4.4, t1lib-5.1.2. T1lib has been tested with that version, and I would think that freetype 2.4.4 should run without issues. The last version I tested with was 2.3.12. Freetype issues arise when their structure members change names without introducing a new API, which has occured regularly in the 2.2-2.3 series. Overall, should be no problems. Use v0.92 or CVS. Regards, Greg : : I would be grateful to know if these are likely to work. Any other hints : and tips would be gratefully received. : : sincerely : sibuXolo : : --------------------------------------------------------------------- : To unsubscribe, e-mail: nanogui-unsubscr...@linuxhacker.org : For additional commands, e-mail: nanogui-h...@linuxhacker.org : : --------------------------------------------------------------------- To unsubscribe, e-mail: nanogui-unsubscr...@linuxhacker.org For additional commands, e-mail: nanogui-h...@linuxhacker.org
