cpufetch is a command-line tool designed to display CPU architecture information in a visually appealing and user-friendly format. It provides detailed insights into the processor's microarchitecture, making it easier for users to identify and understand their system's hardware.
Key Features:
Support for multiple architectures including x86_64, ARM, PowerPC, and RISC-V.
Cross-platform compatibility with Linux, Windows, macOS, and Android.
Customizable color schemes for the CPU logo and text output.
Detailed detection of CPU microarchitecture and vendor-specific information.
Audience & Benefit:
Ideal for system administrators, developers, hardware enthusiasts, and anyone requiring detailed insights into their processor's capabilities. cpufetch simplifies the identification of CPU architecture and provides a visually appealing way to display this information, helping users quickly understand their system's hardware configuration.
The tool can be installed via winget on supported platforms, ensuring easy setup for users.
README
Simple yet fancy CPU architecture fetching tool
cpufetch is a command-line tool written in C that displays the CPU information in a clean and beautiful way
By default, cpufetch will print the CPU logo with the system colorscheme. However, you can set a custom color scheme in two different ways:
4.1 Specifying a name
By specifying a name, cpufetch will use the specific colors of each manufacture. Valid values are:
intel
intel-new
amd
ibm
arm
./cpufetch --color intel (default color for Intel)
4.2 Specifying the colors in RGB format
5 colors must be given in RGB with the format: [R,G,B:R,G,B:R,G,B:R,G,B:R,G,B]. These colors correspond to the CPU logo color (first 3 colors) and for the text colors (following 2).
If the error dissapears: It means that this is the first situation. In this case, just use the
latest version of cpufetch which already has support for your hardware.
If the error does not dissapear: It means that this is the
second situation. In this case, please create a new issue with the error message and the output of 'cpufetch --debug' on https://github.com/Dr-Noob/cpufetch/issues