1

in codeblocks There isn't a C++17 option in the Build or Compiler options, only C++14 how can i enable it in codeblocks so that both coding tools and compiler support it?

amir linux
  • 65
  • 1
  • 1
  • 4

1 Answers1

8

Code::Blocks is not a compiler (but some glorified source code editor, sometimes calling themselves IDEs, which runs some external compiler).

You need a C++17 compiler (and once you've got one you might configure your IDE or editor to use it with the appropriate options). Try the very latest version of GCC (at least GCC 7, and perhaps wait for GCC 8) or Clang (wait for Clang5) and pass it the -std=c++17 option

Note that C++17 is the C++ standard slated to be published by the end of 2017. You may need to wait a bit (perhaps a year or two) for compilers and the standard library implementations to correctly and completely implement it.

Therefore I don't recommend using C++17 features on a project to be released soon (at end of 2017), since you are then building on β quality foundations. However, if you work on a large project to be released in 2019, you might take the risk of betting that the C++17 features you are using in it will become mature by that time.

Regarding standard libraries functions (such as std::filesystem) you'll easily find approximate equivalent (e.g. in native OS or POSIX APIs, in Boost, in Qt, in POCO, ...) that should be reasonably easy to port once C++17 implementations are common.

(I recommend using your compiler on the command line, or using make, ninja, or some other build automation system running compiler commands; details can be operating system and compiler specific.)

Basile Starynkevitch
  • 223,805
  • 18
  • 296
  • 547
  • 1
    Please recommend *anything* besides `make`. A build system like CMake, which is cross-platform would be a good recommendation. – tambre Sep 02 '17 at 18:04
  • `cmake` generate `Makefile`s – Basile Starynkevitch Sep 02 '17 at 18:06
  • 1
    Sure, it's one thing it can generate. Realistically you wouldn't want to generate Makefiles anymore, but rather Ninja files, as they're superior in every way. You can also generate project files for many different IDEs. There's something fitting for every platform and taste. – tambre Sep 02 '17 at 18:11
  • Both GCC and Clang support all C++17 **language** features on their latest releases. There are a few missing standard library things, but they are usually fairly small. – tambre Sep 02 '17 at 18:15
  • 1
    Oh, also, Clang 4 doesn't support the `-std=c++17` flag, but Clang 5, which should be releasing this upcoming week, does. – tambre Sep 02 '17 at 18:18
  • 1
    @tambre: If by "fairly small", you mean the FileSystem, then yes, there will only be a "few" missing features. Neither libc++ nor libstdc++ implement the filesystem as defined in C++17. – Nicol Bolas Sep 02 '17 at 18:30
  • @NicolBolas That's true. Actually `std::filesystem` is the only blocker preventing my code from compiling on both GCC and Clang (besides porting it to Linux). If I'm understanding correctly, then Clang 5, which is shipping this upcoming week, should support C++17 filesystem library in full (although some error resolutions aren't implemented). – tambre Sep 02 '17 at 18:42