mirror of
https://github.com/anrieff/libcpuid
synced 2024-12-16 16:35:45 +00:00
c5b459c5b2
There's no reason to keep a configure binary in source control. I added the necessary steps to create it in the README.
26 lines
888 B
Text
26 lines
888 B
Text
libcpuid
|
|
---------
|
|
|
|
libcpuid provides CPU identification for the x86 (and x86_64).
|
|
For details about the programming API, please see the docs
|
|
on the project's site (http://libcpuid.sourceforge.net/)
|
|
|
|
Configuring after checkout
|
|
--------------------------
|
|
|
|
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 autoconf, automake and libtool installed.
|
|
|
|
After that you can run "./configure" and "make" - this will build
|
|
the library.
|
|
|
|
"make dist" will create a tarball (with "configure" inside) with the
|
|
sources.
|