1# GSL: Guidelines Support Library [](https://travis-ci.org/Microsoft/GSL) [](https://ci.appveyor.com/project/neilmacintosh/GSL) 2 3The Guidelines Support Library (GSL) contains functions and types that are suggested for use by the 4[C++ Core Guidelines](https://github.com/isocpp/CppCoreGuidelines) maintained by the [Standard C++ Foundation](https://isocpp.org). 5This repo contains Microsoft's implementation of GSL. 6 7The library includes types like `span<T>`, `string_span`, `owner<>` and others. 8 9The entire implementation is provided inline in the headers under the [gsl](./include/gsl) directory. The implementation generally assumes a platform that implements C++14 support. There are specific workarounds to support MSVC 2015. 10 11While some types have been broken out into their own headers (e.g. [gsl/span](./include/gsl/span)), 12it is simplest to just include [gsl/gsl](./include/gsl/gsl) and gain access to the entire library. 13 14> NOTE: We encourage contributions that improve or refine any of the types in this library as well as ports to 15other platforms. Please see [CONTRIBUTING.md](./CONTRIBUTING.md) for more information about contributing. 16 17# Project Code of Conduct 18This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 19 20# Usage of Third Party Libraries 21This project makes use of the [Catch](https://github.com/philsquared/catch) testing library. Please see the [ThirdPartyNotices.txt](./ThirdPartyNotices.txt) file for details regarding the licensing of Catch. 22 23# Quick Start 24## Supported Platforms 25The test suite that exercises GSL has been built and passes successfully on the following platforms:<sup>1)</sup> 26 27* Windows using Visual Studio 2015 28* Windows using Visual Studio 2017 29* Windows using Clang/LLVM 3.6 30* Windows using Clang/LLVM 7.0.0 31* Windows using GCC 5.1 32* Windows using Intel C++ Compiler 18.0 33* GNU/Linux using Clang/LLVM 3.6-3.9 34* GNU/Linux using Clang/LLVM 4.0 35* GNU/Linux using Clang/LLVM 5.0 36* GNU/Linux using Clang/LLVM 6.0 37* GNU/Linux using Clang/LLVM 7.0 38* GNU/Linux using GCC 5.1 39* OS X Yosemite using Xcode with Apple Clang 7.0.0.7000072 40* OS X Yosemite using GCC-5.2.0 41* OS X Sierra 10.12.4 using Apple LLVM version 8.1.0 (Clang-802.0.42) 42* OS X El Capitan (10.11) using Xcode with AppleClang 8.0.0.8000042 43* OS X High Sierra 10.13.2 (17C88) using Apple LLVM version 9.0.0 (clang-900.0.39.2) 44* FreeBSD 10.x with Clang/LLVM 3.6 45 46> If you successfully port GSL to another platform, we would love to hear from you. Please submit an issue to let us know. Also please consider 47contributing any changes that were necessary back to this project to benefit the wider community. 48 49<sup>1)</sup> For `gsl::byte` to work correctly with Clang and GCC you might have to use the ` -fno-strict-aliasing` compiler option. 50 51## Building the tests 52To build the tests, you will require the following: 53 54* [CMake](http://cmake.org), version 3.1.3 or later to be installed and in your PATH. 55 56These steps assume the source code of this repository has been cloned into a directory named `c:\GSL`. 57 581. Create a directory to contain the build outputs for a particular architecture (we name it c:\GSL\build-x86 in this example). 59 60 cd GSL 61 md build-x86 62 cd build-x86 63 642. Configure CMake to use the compiler of your choice (you can see a list by running `cmake --help`). 65 66 cmake -G "Visual Studio 14 2015" c:\GSL 67 683. Build the test suite (in this case, in the Debug configuration, Release is another good choice). 69 70 cmake --build . --config Debug 71 724. Run the test suite. 73 74 ctest -C Debug 75 76All tests should pass - indicating your platform is fully supported and you are ready to use the GSL types! 77 78## Using the libraries 79As the types are entirely implemented inline in headers, there are no linking requirements. 80 81You can copy the [gsl](./include/gsl) directory into your source tree so it is available 82to your compiler, then include the appropriate headers in your program. 83 84Alternatively set your compiler's *include path* flag to point to the GSL development folder (`c:\GSL\include` in the example above) or installation folder (after running the install). Eg. 85 86MSVC++ 87 88 /I c:\GSL\include 89 90GCC/clang 91 92 -I$HOME/dev/GSL/include 93 94Include the library using: 95 96 #include <gsl/gsl> 97 98## Debugging visualization support 99For Visual Studio users, the file [GSL.natvis](./GSL.natvis) in the root directory of the repository can be added to your project if you would like more helpful visualization of GSL types in the Visual Studio debugger than would be offered by default. 100
){kind=link}