My intention is to port the STLplus library to as many platforms as I can reasonably support.
SourceForge, which hosts STLplus, used to provide a Compile Farm so that I could test STLplus on different platforms. So in the past, the library collection has been extensively tested on a wide range of platforms. This enabled me, for example, to fix problems with data persistence on 64-bit CPUs and to provide a MacOS port. Unfortunately, the Compile Farm has now been withdrawn, so I can only test the library on my own Windows PC and on virtual machines for Free BSD and Gnu/Linux variants. However, this setup means that I can still test against a range of compiler/platform combinations, including gcc on Gnu/Linux and Free BSD, gcc on Windows using the Cygwin Unix emulator, Windows native builds using Visual Studio and Windows native builds using the MinGW version of the gcc compiler.
There are a number of porting issues to be overcome:
One of the objectives of this library is to provide platform-independent access to operating system services that differ between platforms. The idea is to hide the implementation behind a common interface. By writing software to that interface, you automatically get portable software. At least, that is the theory.
STLplus has been built on the following Operating Systems:
Different CPUs have different word lengths, different byte ordering and different integer type definitions. The intention is that STLplus will work with all variations of these characteristics that I come across.
STLplus has been built on the following CPUs:
The concept of portability usually means portability between operating systems, not necessarily portability between compilers. However, to cater for different tastes in compilers, I have supported as many as I have access to.
It is also important that software will build with different versions of each compiler, because I have no control over which compiler you are using and there's a good chance that you don't either. The STLplus library should ideally work in whatever development environment you have chosen (within reason). So, STLplus works with different releases of these compilers, not just the latest one. On the other hand, STLplus requires a good implementation of templates and so this limits the range of compilers supported.
STLplus has been built on the following compilers:
On each operating system there are a number of different combinations of development environments available:
I refer to a "platform" as a particular combination of CPU, Operating System, Word Length (32 or 64 bit) and Compiler.
These requirements create some limitations on the extent of the library - the primary objective is for it to be portable such that it presents exactly the same interface on all platforms. This means that I do not have anything that cannot be implemented on all platforms with all supported compilers.
For example there's no Unicode support because some compilers have little or no support for Unicode and there are major differences in how Unicode is implemented on different operating systems. There are other libraries that deal with this issue better than I can and so I consider it beyond the scope of the STLplus library to resolve it.
If you can confirm the library works on any other platform or compiler combination, please let me know the details - Compiler, Compiler version, OS, CPU etc.
The following table shows the platforms that STLplus3 has been tested on.
|Intel 686||64||Ubuntu Gnu/Linux||gcc||7.2.0||
|Intel 686||64||Windows 10||gcc||5.1.0||
||2017-11-09||27/27||TDM 64-bit version of gcc - native Windows build|
|Intel 686||64||Windows 10||gcc||6.4.0 (Cygwin64)||
||2017-11-09||27/27||Linux-emulation build on Windows|
|Intel 686||64||Windows 10||Microsoft||Visual Studio 2017||x64||
|Intel 686||32||Windows 10||Microsoft||Visual Studio 2017||Win32||
||2017-11-09||27/27||TrueOS used to be PC-BSD which is a distro of FreeBSD. Built using Clang (the default) and not gcc.|
Note 1: The -D directive is a C macro that selects between
different implementations of code for different platforms. For example, a
Windows application will use different system calls to a Unix application. The
correct directive for the platform must be defined for the STLplus library to
build on the target platform. Typically this is set as an option to the
compiler - for example with the gcc compiler you would specify "
-DSOLARIS" when building on Solaris. The _WIN32 value that
selects the Windows native build is set automatically by the compilers
so you don't have to do this. If no -D directive is shown, then the
default build is a generic Unix build and needs no special rules. See
the documentation on building the library
for more on this.