Caution -- GLFPE work in progress 21 Mar 2018 GLF ----------------------------------------------------------------------------------------------- Why is the GLFPE for Windows toolset a work in progress ------------------------------------------------------- GLF distributes a complete installer set and documentation of procedures which allow a user to install the GLFPE compiler toolset and associated sample compilable source code onto a Windows computer (XP or 10). The Windows version of GLFPE is built from scratch. All the component libraries NOT contained in the core GCC (MinGW32) toolset or the Orwell Dev-C++ IDE installer are built from source. That is a long, painstaking process which tends to change with each major release of the GLFPE for Windows integrated package. That is why it doesn't get updated very often by the author (GLF). The latest working version of an installer package which is PROVEN to work and which compiles all current GLF source code is that from March 2018. The installer .ZIP files for that version have been tested to work under Windows XP and Windows 10. Only 32 bit executables are used for all tools and the compiler only creates 32 bit executables. The compiler is GCC 6.3.0, and included languages are C, C++, Fortran, Gnu COBOL, and Python 2.7. The great amount of work involved in rebuilding the Windows libraries (a mostly manual process) and keeping up with the changes in library versions and code compatibility mean that the rebuilding work isn't done often. The author tries to update the GLFPE compiler toolset every 2 years or so. What about the sample source code? ---------------------------------- The GLF sample source code distributed with the GLFPE is up-to-date as of this writing, in that it is the latest available to GLF and all of it can be compiled with this version of the GLFPE for Windows. The IDEAS embodied in the code may be quite old, since the sample code comes from a career history of programming by GLF for work and personal applications, and he tends to keep everything forever. Some of the programs have been in active (or inactive) use for decades by GLF. The author took astrong interedt in supporting open and free source libraries, particularly imaging and GUI support libraries, and includes many samples of code which uses them. however, GLF has never actively developed code for a broad audience, and the samples are more important to illistrate possibilities than oresent useful applications with universal appeal. The code works such as it is, whether anybody else may be eager to use it is uncertain. They are, however free to do so if they wish. GLF intends for everything in the GLFPE to be as open and free as possible, and as traceable and reproducible to build as possible. How is it built and can anybody do it? --------------------------------------- The procedures to rebuild a working GLFPE Windows toolset package are manual, arcane, mostly but not fully documented. Since the author has recently rebuilt the compiler toolset, the procedures are reasonably complete, and the documentation has been updated for the most part. It is the author's intent that procedures, source files, and other content provided be complete enough such that anyone sufficiently interested CAN reproduce the work and generate a working toolset which can compile everything included, and perhaps much more if the user desires to add more libraries. Code ports to other OS environments than Windows also have priority ------------------------------------------------------------------- Since 2016, most GLF attention and development has been to improve and keep updated the GLFPE for Linux, a live boot Debian 9 OS environment which also can compile all available GLF source code. Sinxce Linux has become the primary working environment, GLF maintains the primary versions of all programs in a Linux environment, As such, the code and most documentation is written with Linux tools, with Linux line endings (LF instead of CRLF as in Windows). Any user should be aware of that, and use text editors which handle and maintain the Linux style, except where it might be important to function under Windows. The Windows built-in Notepad will NOT handle Linux line endings well, and will run all lines together on screen. The built-in Wordpad, however, can read Linux files properly and transparently, and if Wordpad is used to write a file with linux LF endings, it transforms text into a Windows CRLF format. The author recommends acquiring Notepad++ for Windows, a free editor which handles either and has a LOT more features of great utility to a programmer. There are some programs in the source suite which apply to a subset of available OSes to which the overall syatem has been ported, and may not appear in the archives for other OS versions. The original historical GLF code was written under MS-DOS, using Borland Turbo C 2.01, a proprietary (and obsolete) compiler. GLF personally retains the MS-DOS code, but in general does not distribute it anymore. The the systems on which the DOS 16-bit code runs are generally unavailable (but might be emulated with DOSbox or in a FreeDOS VM environment). That old DOS code was eventually ported to Windows (circa 1997). By about 2004, Windows which became the author's primary development environment for a few years. Later (about 2008+) the code was ported to various Linux OS environments (Ubuntu, Mint, Debian).