On Unix systems, it returns the same as the output of uname -s (lowercased). On Windows, this function returns the type of Windows kernel, like "winnt". Values returned by this function are stable and will not change over time, so applications can rely on the returned value as an identifier, except that new OS kernel types may be added over time. It's also the kernel the application is running on, unless the host operating system is running a form of compatibility or virtualization layer. Returns the type of the operating system kernel Qt was compiled for. See also QSysInfo::buildAbi() and QSysInfo::buildCpuArchitecture(). However, due to the nature of the operating system functions being used, there may be discrepancies. Values returned by this function are mostly stable: an attempt will be made to ensure that they stay constant over time and match the values returned by QSysInfo::builldCpuArchitecture(). For example, a 32-bit OS running on a 64-bit CPU is usually unable to determine the CPU is actually capable of running 64-bit programs. Note that this function depends on what the OS will report and may not detect the actual CPU architecture if the OS hides that information or is unable to provide it. Returns the architecture of the CPU that the application is running on, in text format. ![]() QString QSysInfo:: currentCpuArchitecture() See also QSysInfo::buildAbi() and QSysInfo::currentCpuArchitecture(). Typical returned values are (note: list not exhaustive): Values returned by this function are stable and will not change over time, so applications can rely on the returned value as an identifier, except that new CPU types may be added over time. To detect that, use currentCpuArchitecture(). Note that this may not match the actual CPU that the application is running on if there's an emulation layer or if the CPU supports multiple architectures (like x86-64 processors supporting i386 applications). Returns the architecture of the CPU that Qt was compiled for, in text format. QString QSysInfo:: buildCpuArchitecture() See also QSysInfo::buildCpuArchitecture(). For example, -qreal long double becomes "qreal_long_20double". If Qt was configured with another type as qreal, that type is present after "qreal_", with all characters other than letters and digits escaped by an underscore, followed by two hex digits. Currently, Qt has optional ABI components for ARM and MIPS processors: one component is the main ABI (such as "eabi", "o32", "n32", "o64") another is whether the calling convention is using hardware floating point registers ("hardfloat" is present).Īdditionally, if Qt was configured with -qreal float, the ABI option tag "qreal_float" will be present. Zero or more components identifying different ABIs possible in this architecture. Whether it's a 32- or 64-bit application. The same as QSysInfo::buildCpuArchitecture(), such as "arm", "i386", "mips" or "x86_64"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |