Copyright (C) 2020-2025 Frank Eskesen.
This file is free content, distributed under the MIT license. (See the accompanying file LICENSE.MIT or the original contained within https://opensource.org/licenses/MIT)
This is a Software Development Laboratory (SDL) distribution package, sometimes referred to as "The Distribution".
This package contains multiple programming examples in multiple languages. C++, Python, and Java examples also include libraries. A (mostly) bash script library is also provided.
Compiled libraries, sample programs and utilities are built using GNU make from the associated object subdirectory.
Programs are compiled and tested on Cygwin, Fedora, and Ubuntu. While the COM library and some sample programs once ran on Windows, Windows support is deprecated and is no longer tested.
All content is distributed AS-IS, without purpose or warranty of any kind; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Prerequisite packages:
(The prequisites are the same for each environment, but they don't use the same naming conventions.)
These instructions use the SDL package as delivered to install the C++ and python libraries.
git clone https://github.com/franke-hub/SDL.git
cd SDL
. setupSDL
make install
make
(without options) lists available optionsmake install
Installs the C++ and Python librariesmake reinstall
Uninstalls and then installs. (Use this after installing a new Linux version.)make uninstall
Removes all files created by make install.make check
Runs all available test suites.make compile
Compiles (but does not test) all sample programs.make clean
Removes all files created by make check and make compile.make pristine
Essentially the same as running make clean followed by make uninstall.
TODO Implement C# and Java library installation Makefiles. (Only the C++ and Python library installation Makefiles are currently implemented.)
These packages are Cygwin packages, not Windows packages.
Build environment packages:
- autoconf
- automake
- binutils
- gcc-core
- gcc-g++
- gdb
- git
- libtool
- make
- patch
- pkgconf
Build library and sample program packages:
- bzip2
- glm-devel
- ImageMagick (Version >= 7.0)
- libboost-devel
- curl, libcurl-devel
- libdb-devel
- libjpeg-devel
- libhunspell-devel
- libncurses-devel
- libX11-devel
- libX11-xcb-devel
- libX11-xcb1
- libxcb-devel
- libxcb-util-devel
- libxcb-xfixes-devel
- libxcb1
- libXft-devel
- mariadb-common
- ncurses
- openssl
- zlib-devel
Build environment packages:
- autoconf
- automake
- binutils
- gcc
- gcc-c++
- gdb
- git
- libtool
- make
- patch
- pkgconf
Build library packages:
- boost-devel
- bzip2-devel
- glm-devel
- ImageMagick-c++-devel (Version >= 7.0)
- ImageMagick-devel (Version >= 7.0)
- libcurl-devel
- libdb-devel, libdb-cxx-devel
- libhunspell-devel
- libjpeg-turbo-devel
- libX11-devel
- libxcb-devel
- libXft-devel
- mariadb
- ncurses-devel
- openssl-devel
- xcb-util-cursor-devel
- zlib-ng
Build environment packages:
- autoconf
- automake
- binutils
- gcc
- g++
- gdb
- git
- libtool
- make
- patch
- pkgconf
Build library packages:
- ImageMagick-c++-devel (Version >= 7.0)
- ImageMagick-devel (Version >= 7.0)
- libboost-all-dev
- libbz2-dev
- libcurl4-gnutls-dev
- libdb-dev, libdb++-dev
- libglm-dev
- libhunspell-dev
- libjpeg-dev
- libncurses-dev
- libssl-dev
- libx11-dev
- libxcb-image0-dev
- libxcb-xfixes0-dev
- libxcb1-dev
- mariadb
- zlib1g-dev
The distribution primarily uses two git branches:
- The trunk branch, relatively well tested.
- The maint branch, distributed for trunk testing. This branch sometimes contains known errors.
The distribution is kept locally in /home/data/SDL on all local machines, physical or virtual. (Some links rely on this placement.) In addition to this public distribution, the /home/data/ subdirectory contains private information shared via rsync between machines. One of these machines (NFS) exports /home/data in read-only mode and some local virtual machines access that.
The Ubuntu build test (virtual) machine updates only via github. It does not access the exported /home/data Network File System. It's used to verify that maint and trunk releases operate properly as distributed. (It does not access the exported /home/data NFS file system.)
(Root) The distribution root directory, *documented as ~* in this distribution
~
|
[-- bat ((Mostly bash) scripts)
|
[-- doc (Documentation)
|
[-- obj (Object files)
| |
| [-- cpp (C++)
| |
| [-- java (Java)
| |
| [-- mcs (C#)
| |
| [-- py (Python)
|
[-- src (Source files)
| |
| [-- cpp
| |
| [-- java
| |
| [-- mcs
| |
| [-- py
|
[-- usr (Not distributed. Used for machine to machine backup.)
Multiple libraries are also provided:
~
|
[-- obj
| |
| [-- cpp/lib (The library subdirectory)
| | |
| | [-- com (The common library: oldest)
| | |
| | [-- dev (The development library: experimental)
| | |
| | [-- gui (The Graphical User Interface library)
| | |
| | [-- obj (The object library)
| | | (Objects are reference count deleted)
| | |
| | [-- pub (The public library: in active development)
| | |
| | cpp/lib/*/Test (Library test object/executables)
| |
| [-- [java,js,mcs]/lib
| |
| [-- py/site-packages (The python library subdirectory)
| | |
| | The python library
|
[-- src
| |
| [-- cpp/inc (Header files)
| [-- cpp/lib (Source files)
| | |
| | [-- com
| | |
| | [-- dev
| | |
| | [-- gui
| | |
| | [-- obj
| | |
| | [-- pub
| | |
| | cpp/lib/*/Test (Library test source)
| |
| [-- [java,mcs]/lib
| |
| [-- py/site-packages
All C++ libraries have an associated Test subdirectory:
~/src/cpp/lib/*/Test
The dev and pub libraries also contain a regression test script, regression
,
used for distribution testing.
These can be invoked from the root directory using make check
.
For C++ programs, two build helper programs are required.
These programs are built in the ~/obj/cpp/sys/
subdirectory and are
automatically installed into $SDL_ROOT/bin using make install
.
- makeproj: Used to create or update dependencies.
- filecomp: Used in regression testing to (partially) compare files.
In addition to the libraries, (many) sample programs are provided.
The project Wiki contains complete build instructions starting from an "Ubuntu Desktop for developers" package.
TODO Complete the library documentation.
TODO Document the sample programs.