|anonymous 949420b7d4 why are we doing this?||1 year ago|
|cpuid_tool||1 year ago|
|debian||1 year ago|
|libcpuid||1 year ago|
|tests||2 years ago|
|.gitignore||4 years ago|
|AUTHORS||11 years ago|
|COPYING||11 years ago|
|ChangeLog||3 years ago|
|Makefile.am||4 years ago|
|NEWS||11 years ago|
|Readme.md||1 year ago|
|configure.ac||2 years ago|
|libcpuid.pc.in||11 years ago|
libcpuid provides CPU identification for the x86 (and x86_64). For details about the programming API, you might want to take a look at the project's old website on sourceforge (http://libcpuid.sourceforge.net/)(Warning: sourceforge link). There you'd find a short tutorial(Warning: sourceforge link), as well as the full API reference(Warning: sourceforge link).
(This branch of libcpuid is intended to be the main one, post-microsoft's purchasing of github.)
Under Linux, where you download the sources, there's no configure script to run. This is because it isn't a good practice to keep such scripts in a source control system. To create it, you need to run the following commands once, after you checkout the libcpuid sources from github:
1. run "libtoolize" 2. run "autoreconf --install"
You need to have
After that you can run
make - this will build
make dist will create a tarball (with "configure" inside) with the
Using libcpuid requires no dependencies on any of the supported OSes. Building it requires the aforementioned libtool and autotools commands to be available, which is a matter of installing a few common packages with related names (e.g. automake, autoconf, libtool). It also requires a POSIX-compatible shell. On NetBSD, you may need to install one (credits to @brucelilly):
After any change to the detection routines or match tables, it's always
a good idea to run
make test. If some test fails, and you're confident
that the test is wrong and needs fixing, run
You can also add a new test (which is basically a file containing
the raw CPUID data and the expected decoded items) by using
tests/create_test.py. The workflow there is as follows:
For non-developers, who still want to contribute tests for the project, use this page to report misdetections or new CPUs that libcpuid doesn't handle well yet.
So far, I'm aware of the following projects which utilize libcpuid:
We'd love to hear from you if you are also using libcpuid and want your project listed above.