Why no std::byte in qt?!!

[Engelard]

Oh and in the Kits i just now noticed, for some reason there is compilers for amd chosen, when i have normal for intel i suppose in my VS. And i can't change it, when i press manage - it's simply throw me in to compilers tab so i don't know how to change it:

AND. i just now added one more custom compiler, also from VS2017 but 64 version, since i have x64 CPU and windows, maybe should be proper one, am i right?

Only one thing (as i understand) left to do. Is apply compiler which i chose in 'compilers' tab, because there is still my old as you can see from screenshot

[jsulm]

@Engelard "How your argument should work?" - easy. You should understand the difference between a compiler, an IDE and a framework. Qt is a C++ framework (not a compiler), QtCreator is an IDE which supports many different compilers, but does not contain own compilers. C++standard library (std::*) comes as part of the compiler and NOT Qt, that's why it is "completely unrelated to Qt". So, as already explained by others you need a compiler supporting C++2017 and activate C++2017 supports in the pro file (not sure it is needed with Microsoft compilers).

Didn't QtCreator auto-detect your VS2017 compiler? Usually there is no need to configure compilers manually. The 15.0 is already the C++ compiler from VS2017, why do you add the compiler manually? Does it now work with your "Desktop Qt 5.10.1 MSVC2017 64bit2" Kit and autodetected VS2017 compiler?

One note: an IDE does not have to contain any compilers. Microsoft Compilers can be installed and used without Visual Studio. The reasons are: it must be possible to use compilers without a huge IDE (for example in a continuous integration system) and many IDEs (like QtCreator) support different compilers which come from different companies or are open source. QtCreator, for example, supports Microsoft Compilers and MinGW on Windows. Qt Online Installer for Windows provides the possibility to install MinGW as it is Open Source. Microsoft compilers on the other hand can't be provided by Qt Online Installer as this not allowed by Microsoft.

[VRonin]

@Engelard said in Why no std::byte in qt?!!:

still it says that byte is not part of std.

• Did you #include <cstddef>?
• Can you open Visual Studio 2017, create a simple console program and test if it works there?

[kshegunov]

@Engelard said in Why no std::byte in qt?!!:

there is compilers for amd chosen, when i have normal for intel i suppose in my VS

This is the CPU instruction set. Intel processors use amd64, so it's correct.

[kkoehne]

@Engelard said in Why no std::byte in qt?!!:

CONFIG += c++17
QMAKE_CXXFLAGS += -std:c++17

Please try

CONFIG +=c++1z

This works for me with Visual Studio 2017 compiler.

[kenchan]

@Engelard
OK, problem solved...
In spite the Microsoft docs which say the -std:c++17 flag can be used in VS2017 to enable the c++17 features it does not seem to work though the command line via qmake!
but adding...
DEFINES += _HAS_STD_BYTE
and
QMAKE_CXXFLAGS += -std:c++17
to the pro file does work and I can use std::byte in the code.

QMAKE_CXXFLAGS += -std:c++1z also worked

I hope this works for you too.

[Engelard]

@VRonin said in Why no std::byte in qt?!!:

@Engelard said in Why no std::byte in qt?!!:

still it says that byte is not part of std.

• Did you #include <cstddef>?

Yes, i mentioned in firsts posts.

• Can you open Visual Studio 2017, create a simple console program and test if it works there?

In first post i told that original program which widely using std::byte was from my VS2017(ofc it works).

@kshegunov

This is the CPU instruction set. Intel processors use amd64, so it's correct.

lol

[Engelard]

@kshegunov said in Why no std::byte in qt?!!:

@Engelard said in Why no std::byte in qt?!!:

there is compilers for amd chosen, when i have normal for intel i suppose in my VS

This is the CPU instruction set. Intel processors use amd64, so it's correct.

lol

@kkoehne said in Why no std::byte in qt?!!:

@Engelard said in Why no std::byte in qt?!!:

CONFIG += c++17
QMAKE_CXXFLAGS += -std:c++17

Please try

CONFIG +=c++1z

This works for me with Visual Studio 2017 compiler.

Sorry, no effect. Tried both of them, separately and together like in your message.

[Engelard]

@kenchan damn it worked! At least now after typing std::b it advice me byte type and word now not dead black but violet like all valid variables should be(finally).

But!)

It still rejects to compile. I tried to clean all, then rebuild, but same error:

[Engelard]

Even restart of Qt don't help, what's wrong...

[kenchan]

@Engelard
hmm?? looks like you have another problem somewhere.
Can you show us your pro file?
Can you show us a screen shot of your kits panel for the kit you are currently using again please?
Can you show us a screen shot the qt versions panel and the compilers panel again please?
Can can you show a screen shot of the compiler output when you compile your code with the std::byte declaration please?

Thank you

[kenchan]

@Engelard
I few tests show me that you can actually get away with using either DEFINES += _HAS_STD_BYTE or QMAKE_CXXFLAGS += -std:c++17 when using the VS 15.0 compiler.
Using both is obviously twice as safe.

Just make sure you blow away the build folder, rerun qmake and rebuild just to be sure.

creating a new Non-Qt Plain C++ project with this pro file

 TEMPLATE = app
CONFIG += console
CONFIG -= app_bundle
CONFIG -= qt
DEFINES += _HAS_STD_BYTE
QMAKE_CXXFLAGS += -std:c++17
 
SOURCES += \
        main.cpp

and this c++ code worked fine for me.

#include <iostream>
#include <cstddef>
 
using namespace std;
 
int main()
{
    byte stdbyte;
    stdbyte = std::byte(0);
    byte *arr = new std::byte[2];
    arr[0] = std::byte(0x2a);
 
    cout << "Hello World!" << endl;
    return 0;
}

Why don't you try this and see if it works?

[Engelard]

This post is deleted!

[Engelard]

Seems the problem was in old build directory. After complete deletion of it - program finally compiles:

DAMN it was hard and so long. New features of new C++17 in Qt cost so much...

[kenchan]

@Engelard
Yes, that is what I suspected was the problem.
Glad you finally got it working.