@alonbl, @Guozht, @Azer0s, @anonimal, @wildbiotiger, @UKMonkey, @UKMonkey, @Marc--Olivier, @Romain-Geissler-1A, @ZahlGraf, @NexusSafe, @egorpugin, @HeinrichJanzing, @geoffbeier, @FloriansGit, @steady286, @zabulus, @morozovcookie, @GamePad64, @solvingj,
One of the ways we test Crypto++ is through the GCC Compile Farm. The compile farm is open to anyone working on free and open software projects. The farm provides access to additional hardware, operating systems and compilers, like PowerPC and PPC-64, Aarch64, AIX, and IBM XL C/C++ compiler.
Another good testing practice is to buy a few inexpensive dev-boards, like a BeagleBone, CubieTruck and MIPS Creator. They offer you local ARM and MIPS testing for 30 to 50 US dollars. And don't forget Android because its NDK uses some unusual flags, like -mfloat-abi=soft (Linux usually uses hard floats).
Yet another good testing practice is to setup VMs with Solaris and some of the BSDs, like OpenBSD, FreeBSD, NetBSD and DragonFly. Solaris is one of the most frustrating platforms to work on, so be sure to have one handy for testing. Sun's C++ compiler is full of surprises.
Finally, Debian Chroots are useful for testing Debian. You get access to the supported ports and some unsupported ports. Be sure to visit the Crypto++ wiki documentation at Debian Chroots. It has the recipes to set up the chroots.
CMake testing on some of the lesser used platforms will go a long way in promoting the stability of the CMake project files.
@alonbl, @Guozht, @Azer0s, @anonimal, @wildbiotiger, @UKMonkey, @UKMonkey, @Marc--Olivier, @Romain-Geissler-1A, @ZahlGraf, @NexusSafe, @egorpugin, @HeinrichJanzing, @geoffbeier, @FloriansGit, @steady286, @zabulus, @morozovcookie, @GamePad64, @solvingj,
One of the ways we test Crypto++ is through the GCC Compile Farm. The compile farm is open to anyone working on free and open software projects. The farm provides access to additional hardware, operating systems and compilers, like PowerPC and PPC-64, Aarch64, AIX, and IBM XL C/C++ compiler.
Another good testing practice is to buy a few inexpensive dev-boards, like a BeagleBone, CubieTruck and MIPS Creator. They offer you local ARM and MIPS testing for 30 to 50 US dollars. And don't forget Android because its NDK uses some unusual flags, like
-mfloat-abi=soft(Linux usually uses hard floats).Yet another good testing practice is to setup VMs with Solaris and some of the BSDs, like OpenBSD, FreeBSD, NetBSD and DragonFly. Solaris is one of the most frustrating platforms to work on, so be sure to have one handy for testing. Sun's C++ compiler is full of surprises.
Finally, Debian Chroots are useful for testing Debian. You get access to the supported ports and some unsupported ports. Be sure to visit the Crypto++ wiki documentation at Debian Chroots. It has the recipes to set up the chroots.
CMake testing on some of the lesser used platforms will go a long way in promoting the stability of the CMake project files.