INTRODUCTION

When C++11 was released I wanted to learn the new features introduced. I soon realized that it was unlikely to happen at work. Migrating the company C++ source code, projects, solutions, etc. was simply to big a task. I wanted a reasonably challenging idea for a hobby project and decided to try implement an MFC-based application using the MVVM (Model–View–ViewModel) architecture pattern. This was the start of the GO C++ Libraries.

The GO C++ Libraries have two main implementations. The first uses C++11/14/17/20 and the C++ Standard Library. The second uses C++98/03 and the Boost Libraries. I find it interesting to do both implementations. Doing the first std-based implementation gives me the opportunety to learn about new C++11/14/17/20 features. The second boost-based implementation broaden my knowledge of the Boost Libraries.

Documentation for GO C++ Libraries is found at goranorsander.github.io/go_libs.

HOW-TO BUILD

Boost Libraries

If you want to use the boost-based implementation of the GO C++ Libraries you need to build the Boost Libraries. This is a short how-to.

1. Download the Boost Libraries source code from www.boost.org
2. Extract the boost source code archive
3. Open a command prompt or terminal and cd to the boost source code root directory
4. Bootstrap, i.e. build the Boost.Build tools, by calling
   • bootstrap.sh (on Linux)
   • bootstrap.bat (on Windows)
5. Build boost by calling b2 with appropriate options, properties, and target, e.g.
   • b2 boost.locale.icu=off --build-dir=build --toolset=clang debug threading=multi link=static --build-type=complete address-model=64 --layout=versioned -j 3 stage (on Linux, using clang, debug build, 64 bits, 3 cores)
   • b2.exe --build-dir=build --toolset=msvc-14.1 release threading=multi link=static --build-type=complete address-model=32 --layout=versioned -j 6 stage (on Windows, using Visual Studio 2017 C++, release build, 32 bits, 6 cores)
   • b2.exe boost.locale.iconv=off --build-dir=build --toolset=gcc debug threading=multi link=static --build-type=complete address-model=64 --layout=versioned -j 6 stage (on Windows, using MinGW/GCC, debug build, 64 bits, 6 cores)

For more information see the Boost.Build Tutorial.

I currently use Boost Libraries version 1.78.0 when developing the GO C++ Libraries.

GO C++ Libraries

The GO C++ Libraries use CMake to manage the build process. CMake can be downloaded from cmake.org/download.

CMake configuration:

• BOOST_INCLUDEDIR = path to boost (e.g. C:\path\to\boost_1_78_0)
• BOOST_LIBRARYDIR = path to boost link libraries (e.g. C:\path\to\boost_1_78_0\stage\x64\lib)
• BOOST_MAJOR_VERSION = 1
• BOOST_MINOR_VERSION = 78
• BOOST_PATCH_LEVEL = 0
• BUILD_BOOST_EXAMPLES = TRUE|FALSE
• BUILD_BOOST_MFC_EXAMPLES = TRUE|FALSE
• BUILD_BOOST_RND = TRUE|FALSE
• BUILD_BOOST_TESTS = TRUE|FALSE
• BUILD_STD_EXAMPLES = TRUE|FALSE
• BUILD_STD_MFC_EXAMPLES = TRUE|FALSE
• BUILD_STD_RND = TRUE|FALSE
• BUILD_STD_TESTS = TRUE|FALSE
• CXX_COMPILER_WARNING_LEVEL = W0|W1|W2|W3|W4|W5 (W0 disables all warnings, W5 enables all warnings)
• ENABLE_SUPPRESS_WARNINGS = TRUE|FALSE
• CMAKE_CONFIGURATION_TYPES = Debug;Release
• CMAKE_INSTALL_PREFIX = path to install directory
• CMAKE_GNUtoMS = TRUE|FALSE
• USE_SOLUTION_FOLDERS = TRUE|FALSE
• BUILD_GMOCK = TRUE|FALSE
• INSTALL_GTEST = TRUE|FALSE

Use CMake to configure and generate a build solution for your toolset.

The CMake configurations I use:

SETTING \ TOOLSET	clang 12.0.1	gcc 11.1.0	MSYS2 MinGW gcc 10.2.0	Visual Studio 2022 Community	Visual Studio 2019 Community	Visual Studio 2017 Community	Visual Studio 2015 Community	Visual Studio 2013 Express	Visual Studio 2012 Express	Visual Studio 2010 Express	Visual Studio 2008 Express
BOOST_MAJOR_VERSION	1	1	1	1	1	1	1	1	1	1	1
BOOST_MINOR_VERSION	78	78	78	78	78	78	78	78	78	78	78
BOOST_PATCH_LEVEL	0	0	0	0	0	0	0	0	0	0	0
BUILD_BOOST_EXAMPLES	X	X	X	X	X	X	X	X	X	X	X
BUILD_BOOST_MFC_EXAMPLES				X	X	X	X
BUILD_BOOST_RND	X	X	X	X	X	X	X	X	X	X	X
BUILD_BOOST_TESTS	X	X	X	X	X	X	X	X	X	X	X
BUILD_STD_EXAMPLES	X	X	X	X	X	X	X	X	X	X	X
BUILD_STD_MFC_EXAMPLES				X	X	X	X
BUILD_STD_RND	X	X	X	X	X	X	X	X	X	X
BUILD_STD_TESTS	X	X	X	X	X	X	X	X	X	X
CXX_COMPILER_WARNING_LEVEL	W4	W4	W4	W4	W4	W4	W4	W4	W4	W4	W4
ENABLE_SUPPRESS_WARNINGS	X	X	X	X	X	X	X	X	X	X	X
USE_SOLUTION_FOLDERS	X	X	X	X	X	X	X	X	X
BUILD_GMOCK	X	X	X	X	X	X	X	X	X	X	X
INSTALL_GTEST	X	X	X	X	X	X	X	X	X	X	X

The settings BOOST_INCLUDEDIR, BOOST_LIBRARYDIR, CMAKE_CONFIGURATION_TYPES, and CMAKE_INSTALL_PREFIX must be set to match your development environment and toolset.

My development environment and toolset details:

• Manjaro Linux Qonos 21.2.0, Xfce, 64 bits
  • cmake version 3.22.1
  • clang version 13.0.0
  • gcc (GCC) 11.1.0
  • git 2.34.1
  • GNU Make 4.3
  • Code::Blocks 20.03
  • ruby 3.0.3p157 (2021-11-24 revision 3fb7d2cadc) [x86_64-linux]
  • Visual Studio Code 1.19.2 - with same extensions as in Windows environment
• Windows 10 Professional, 64 bit
  • cmake version 3.22.1
  • MSYS2 64bit 20200720
  • gcc (GCC) 10.2.0-1
  • git 2.34.0.windows.1
  • GNU Make 4.2.1
  • Code::Blocks 17.12
  • ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x64-mingw32]
  • TortoiseGit 2.12.0.0
  • Visual Studio 2008 Express Edition with SP1
  • Visual Studio 2010 Express
  • Visual Studio Express 2012 for Windows Desktop
  • Visual Studio Express 2013 for Windows Desktop
  • Visual Studio Community 2015
  • Visual Studio 2017, Community Edition, version 15.9.42
  • Visual Studio 2019, Community Edition, version 16.11.8
  • Visual Studio 2022, Community Edition, version 17.0.4
  • Visual Studio Code 1.63.2 - with extensions:
    • C/C++ 1.7.1 (C/C++ IntelliSense, debugging, and code browsing)
    • CMake 0.0.17 (CMake language support)
    • CMake Tools 1.9.2 (Extended CMake support)
    • Git Lens 11.7.0 (Supercharge Visual Studio Code's Git capabilities)
    • Markdown All in One 3.4.0 (All you need to write Markdown)

GOOGLE TEST

I use the Google Test framework for unit testing. See github.com/google/googletest for more information.

CODESCENE ANALYSIS

Get more details at codescene.io.