How to Install and Uninstall iwyu.x86_64 Package on Fedora 39
Last updated: November 30,2024
1. Install "iwyu.x86_64" package
Please follow the instructions below to install iwyu.x86_64 on Fedora 39
$
sudo dnf update
Copied
$
sudo dnf install
iwyu.x86_64
Copied
2. Uninstall "iwyu.x86_64" package
Please follow the instructions below to uninstall iwyu.x86_64 on Fedora 39:
$
sudo dnf remove
iwyu.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the iwyu.x86_64 package on Fedora 39
Last metadata expiration check: 4:46:22 ago on Thu Mar 7 17:44:52 2024.
Available Packages
Name : iwyu
Version : 0.20
Release : 3.fc39
Architecture : x86_64
Size : 666 k
Source : iwyu-0.20-3.fc39.src.rpm
Repository : fedora
Summary : C/C++ source files #include analyzer based on clang
URL : https://github.com/include-what-you-use/include-what-you-use
License : NCSA
Description : "Include what you use" means this: for every symbol (type, function, variable,
: or macro) that you use in foo.cc (or foo.cpp), either foo.cc or foo.h should
: include a .h file that exports the declaration of that symbol. (Similarly, for
: foo_test.cc, either foo_test.cc or foo.h should do the including.) Obviously
: symbols defined in foo.cc itself are excluded from this requirement.
:
: This puts us in a state where every file includes the headers it needs to
: declare the symbols that it uses. When every file includes what it uses,
: then it is possible to edit any file and remove unused headers, without fear
: of accidentally breaking the upwards dependencies of that file. It also
: becomes easy to automatically track and update dependencies in the source
: code.
Available Packages
Name : iwyu
Version : 0.20
Release : 3.fc39
Architecture : x86_64
Size : 666 k
Source : iwyu-0.20-3.fc39.src.rpm
Repository : fedora
Summary : C/C++ source files #include analyzer based on clang
URL : https://github.com/include-what-you-use/include-what-you-use
License : NCSA
Description : "Include what you use" means this: for every symbol (type, function, variable,
: or macro) that you use in foo.cc (or foo.cpp), either foo.cc or foo.h should
: include a .h file that exports the declaration of that symbol. (Similarly, for
: foo_test.cc, either foo_test.cc or foo.h should do the including.) Obviously
: symbols defined in foo.cc itself are excluded from this requirement.
:
: This puts us in a state where every file includes the headers it needs to
: declare the symbols that it uses. When every file includes what it uses,
: then it is possible to edit any file and remove unused headers, without fear
: of accidentally breaking the upwards dependencies of that file. It also
: becomes easy to automatically track and update dependencies in the source
: code.