About Orwell Dev-C++ as the IDE of the author's choice 24 Jan 2018 GLF --------------------------------------------------------------------------------------------- The author (GLF) first started programming C/C++ ias Windows code using the free Bloodshed Dev-C++ IDE in the late 1990s. It was free, easy to find on the internet, it contained all the necessary tools to compile and run C/C++ programs, and had a built-in packaging system which encouraged extenson by third party library development. It had what the author needed at the time, and much of the author's code was ported to Windows by about 2005 using it. At the time the latest avilable GCC compiler for Dev-C++ was GCC 3.4.2. Many users discovered this IDE and built a following for it. However, the original developer stopped significant development of Dev-C++ and it gradually grew obsolete. The compiler on which it was based, the minGW32 port of GCC, was itself a slowly developing project and though it's support continued, it tended to have older versions of GCC than were currently supported on other platforms. Dev-C++ was openly distributed, but the source code on which it was based was harder to acquire, and written in Pascal with an ideosycratic build system, so it was harder to adapt, so the executable reamined at version 4.9.9.2 for years. One major advantage of Dev-C++ was the project file structure. Project files specify the makeup of all the files needed to build project executables, as well as various compilation and linking options. Within the IDE, when "Rebuild All" is selected, the project file is processed into a Makefile (Makefile.win) compatible with the underlying GCC compiler system as a command-line back end to the IDE. Then the Makefile itself is processed by GCC to produce the actual executable program or library module. The advantage of the Dev-C++ project file format is that it was ASCII plaintext, easily edited, copied, cut-and-pasted into other project files. It was easy to write programs to either read or create new comopatible project files. That was valuable to the author as he strove to port progrmas from one OS platform to another. Because the Dev-C++ IDE continued to be was available as an executable package, and was readily adaptable to alternate compilers, it was still a usable base toolset for the author. The author continued to find newer versions of MinGW32 GCC and for some years periodically adapted the toolset to newer GCC versions. However the real workload in the adaptation was in acquisition of and compilation from source of a large number of support libraries (such as libpng and zlib). That work effort led to large gaps between versions of the author's personal toolset. Eventually the lack of ongoing support for Bloodshed Dev-C++, while still retaining a small but enthusiastic following, led to forks of the original project. Two significan forks appeared at different times. For a while wxDev-C++ was a viable alternative, and came with a newer compiler bundled with the wxWidgets GUI library. The author used it for a few years, but apparently development stalled on wxDev-C++. About the time the author began thinking of the concept of a "GLFPE", a compiler environment portable across OS types, he adopted wxDev-C++ as a base toolset (about 2010). Later, the Orwell Dev-C++ project emerged, with yet another variation of bundling. However, it appeared that Orwell development was onging, and certain improvements were made that fixed old bugs. The author re-adapted the GLFPE to Orwell Dev-C++ in about 2013. The compiler and library toolset was rebuilt again using Orwell in 2016. The version of the compiler used at that time was TDM-GCC, the MinGW32 package, with GCC 4.8.1. The author has successfully experimented with other IDE packages, both simpler (V IDE) and more complex (Code::Blocks), but for Windows, still gravitates to Orwell Dev-C++. The interested user is free to try to use othe rIDE applications, or just use the command line itself, leaning on the built-in toolset under \glfpe\mgw481 (MinGW32 with GCC 4.8.1). The Orwell Dev-C++ IDE can be started either in a portable or nonportable mode, using alternate versions of executables (bothe available under \glfpe\orwmgw481). The installed version (devcpp.exe) uses config fioes stored inthe host "Users" folders. The portable version uses configs stored in \glfpe\orwmgw481\config. Default configurations usually work OK, but certain of the author's sample programs have tricky requirements, and it has been found that Orwell's configuration settings can make or break some builds, sometimes in inexplicable ways. To prevent long-term trouble, a ZIP archive with known wirking config files is retained in the \glfpe\orwmgw481 folder, just in case something goes wrong and you can't figure it out. Sometimes restoring the configs will make a compilation succeed where it formerly blew up.