How GLFPE sample source help files are produced 02/04/2019 GLF ---------------------------------------------------------------------------- HTML help files which describe the sample source files provided to work with the GLF programming Environment (GLFPE) are produced semiautomatically by scanning the source tree folders for project files. The scanned files inform the production of a set of HTML files which describe the structure of each project, including all source files and libraries required. Because each OS uses different IDEs, with different project file formats, each OS produces its own set of help files to match the IDE and library assumptions. GLFPE for Windows uses orwell Dev-C++ as IDE, so it uses *.dev project files. GLFPE for Linux uses the V IDE, and uses *.vpj files for its projects. Linux projects are further subdivided into Debian 32-bit, Debian 64-bit, and Raspberry Pi Raspbian Arm 32-bit variants, but each uses the V IDE project files with some project-level variations across OS types. The help files for Windows are generated by a structured batch invocation of "32docudevhd.exe". Equivalent help files for Linux or Rpi are produced similarly using the program "lxdocuvpjhd". The top level file (index) for each HTML file set provides clickable links to GLFPE source groups, and the links in turn point to more detailed documentation on each project within those groups. Included are lists of alll source code modules, which also provide clickable links to the source code itself, provided both the help files and the code are installed to the standard locations expected within the GLFPE source tree. Also, the "images" subfolder includes JPG picture files taken from screen snapshots for many of the applications. The file names for each of those images is only relevant within GLFPE and specific to the OS platform such that the HTML code can find the pictures. For each platform, the help is intended to be extracted to the relevant "help" subfolder of the OS-specific IDE source tree (e.g. orw630 for Windows, v64_630 or v32_630 for Debian Linux, and rpi630 for Raspberry Pi).