Technical notes for Elgrint compilation
- Elgrint supports all the desktop versions of Microsoft Windows from XP Service Pack 2 (although it may partially work even with earlier versions) through Windows 8.1 (desktop mode only). Support for other platforms, starting with Google Android, is coming. Elgrint's interface is designed to be fully platform-agnostic, which means it can be seamlessly adapted to practically any modern graphic operating system, and with a relatively small effort too.
- Elgrint compilation has been tested with Microsoft Visual C++ 2008, 2010, and 2012, and with MinGW 4.8. Contact Us if you're having compilation problems with these compilers, or if you need support for other compilers.
- The distributed version of Elgrint currently supports only 32-bit compilations, which means your apps can use up to 4GB of operating memory (which is usually more than enough). Contact Us if you need a 64-bit version (which has no practical limit on the usable memory)
- The MinGW (GCC) compiler creates additional limitations, as follows:
- The MMultimedialLabel widget doesn't work at all, although it can be used in apps (compilation will succeed, but the widget will do nothing). This is the only serious limitation - the rest are not crucial
- MSys::getVideoRecordingDevices and MSys::getAudioRecordingDevices return empty results, but they are needed only for MMultimediaLabel, so it doesn't matter much
- The DirectX graphics is not supported, so the apps fall back on legacy GDI+ graphics. As a result, the apps may appear to work slower on MS-Windows 8 and later, which don't support hardware acceleration for GDI+
- MMainFrame can be switched to a full-screen mode (frHuge), but the switch may not work smoothly (although that depends on the system, and in any case, the difference should be barely noticeable)
- MFile::setPos and MFile::truncate are limited to 2GB. If these functions are used so that the new position or size (respectively) is greater than 2GB, the file will be closed and an error will be generated (the app will continue working fine, though). That being said, the reading and writing operations of MFile are not limited to 2GB
- GetName(MWindow&) and GetName() return mangled class names (although they are still recognizable and usable)
Microsoft Visual C++ doesn't have these limitations. We are working on eliminating these limitations in MinGW as well.
- The Cloud Compilation Service currently works only with the MinGW 4.8 compiler, so it is subject to the preceding limitations.