Version: 0.17, Package name: include-what-you-use-0.17 |
Maintained by: Jonathan Gray |
Master sites: |
Description Include what you use means this: for every symbol (type, function variable, or macro) that you use in foo.cc, either foo.cc or foo.h should #include a .h file that exports the declaration of that symbol. The include-what-you-use tool is a program that can be built with the clang libraries in order to analyze #includes of source files to find include-what-you-use violations, and suggest fixes for them. The main goal of include-what-you-use is to remove superfluous #includes. It does this both by figuring out what #includes are not actually needed for this file (for both .cc and .h files), and replacing #includes with forward-declares when possible. |
Filesize: 729.771 KB |
Version History (View Complete History) |
|
2021-11-01 18:00:27 by Stuart Henderson | Files touched by this commit (99) |
Log message: bump REVISION for switch from Python 3.8 -> 3.9 |
2021-05-13 17:55:13 by Jeremie Courreges-Anglas | Files touched by this commit (3) |
Log message: Update to include-what-you-use-0.15 to support llvm-11 ok jsg@ (maintainer) |
2021-02-23 12:39:53 by Stuart Henderson | Files touched by this commit (743) |
Log message: Reverse the polarity of MODPY_VERSION; default is now 3.x, if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}. This commit doesn't change any versions currently used; it may be that some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those should be cleaned up in the course of updating ports where possible. Python module ports providing py3-* packages should still use FLAVOR=python3 so that we don't have a mixture of dependencies some using ${MODPY_FLAVOR} and others not. |
2020-08-05 02:13:37 by Jeremie Courreges-Anglas | Files touched by this commit (3) |
Log message: Update to include-what-you-use-0.14, which supports llvm-10 ok jsg@ (maintainer) |
2020-07-03 15:13:23 by Stuart Henderson | Files touched by this commit (1032) |
Log message: bump REVISION; python 3 default changed to 3.8 |
2019-12-05 08:51:55 by Jeremie Courreges-Anglas | Files touched by this commit (2) |
Log message: Drop powerpc-specific patch now that llvm provides all backends on powerpc from Brad, ok jsg@ (maintainer) |
2019-09-08 04:40:39 by Jeremie Courreges-Anglas | Files touched by this commit (8) |
Log message: Update to llvm-8.0.1 Similar diff from Brad; bulk build by ajacoutot@ |
2019-07-06 10:16:27 by Jeremie Courreges-Anglas | Files touched by this commit (1) |
Log message: Let include-what-you-use build on powerpc. powerpc is the only platform where llvm isn't built with all supported targets (only the powerpc backend is enabled). So include-what-you-use can't call LLVMInitializeX86*() there. Maybe llvm should also ship the X86 backend on powerpc, as suggested by jsg@, but this is not trivial. Tests by cwen@, ok cwen@ jsg@ (maintainer) |
2019-07-06 09:07:55 by Jeremie Courreges-Anglas | Files touched by this commit (4) |
Log message: Update to include-what-you-use-0.12, to unbreak with llvm-8.0.0 |
2019-06-17 15:33:45 by Klemens Nanni | Files touched by this commit (2) |
Log message: Ship docs, use Python 3, enable tests, drop libexecinfo dependency libexecinfo is not used at all and Python is merely a RUN_DEPENDS. Use TLS and derive PKGNAME from DISTNAME while here. Documentation input ingo WANTLIB help and OK sthen |
2019-02-16 05:06:23 by Jonathan Gray | Files touched by this commit (1) |
Log message: Add a RUN_DEPENDS on devel/llvm as include-what-you-use links libLLVM and drop no longer required IWYU_LLVM_ROOT_PATH env var. From Caspar Schutijser. sthen@ noted this can't be a LIB_DEPENDS as libLLVM is not installed as a major.minor library. |
2019-01-27 23:27:28 by Jeremie Courreges-Anglas | Files touched by this commit (93) |
Log message: Update to llvm-7.0.1 (and include-what-you-use-0.11) All the work done by Brad except for some fixes from base by mortimer@ and patrick@ Tests: amd64 Brad, jsg@ and me, i386: Brad, mips64: visa@, sparc64 me. No tests on powerpc but a test build with only the PowerPC backend packages on amd64. |
2018-11-02 02:50:13 by Jonathan Gray | Files touched by this commit (3) |
Log message: update to include-what-you-use 0.10 from Brad |
2018-05-22 01:34:09 by Jonathan Gray | Files touched by this commit (1) |
Log message: include-what-you-use now uses the FindBacktrace cmake module which results in an undeclared dependency on libexecinfo. Reported by espie@ |
2018-04-07 08:56:24 by Antoine Jacoutot | Files touched by this commit (5) |
Log message: Adapt to new LLVM. from Brad |
2018-03-16 19:31:21 by Jonathan Gray | Files touched by this commit (3) |
Log message: update to include-what-you-use 0.9 from Brad |
2017-09-08 05:53:41 by Antoine Jacoutot | Files touched by this commit (1) |
Log message: Bump after llvm update (static libs linked into the binary). from Brad |
2017-09-01 00:41:56 by Antoine Jacoutot | Files touched by this commit (2) |
Log message: Fix for llvm>=5.0.0rc4 and make use of COMPILER. from Brad |
2017-08-13 04:15:23 by Jonathan Gray | Files touched by this commit (6) |
Log message: update to include-what-you-use 0.8 from Brad |
2017-03-14 11:30:31 by Antoine Jacoutot | Files touched by this commit (1) |
Log message: Bump LLVM version. from Brad |
2017-02-10 02:39:21 by Antoine Jacoutot | Files touched by this commit (4) |
Log message: Fix with llvm>=4.0.0rc2. from Brad |
2016-12-31 23:58:37 by Jonathan Gray | Files touched by this commit (6) |
Log message: update to include-what-you-use 0.7 from Brad Smith |
2016-10-07 02:57:13 by Antoine Jacoutot | Files touched by this commit (3) |
Log message: Fix iwyu to build with llvm 3.9. "should be good" jsg@ from Brad |
2016-05-14 18:03:43 by Jonathan Gray | Files touched by this commit (3) |
Log message: update to 0.6 for llvm 3.8 compatibility from Brad |