Package Details: include-what-you-use 1:0.12-1

Git Clone URL: (read-only)
Package Base: include-what-you-use
Description: A tool for use with clang to analyze #includes in C and C++ source files
Upstream URL:
Keywords: c c++ format header include iwyu
Licenses: LLVM Release License
Submitter: Mindless
Maintainer: sebschrader (jetm)
Last Packager: jetm
Votes: 25
Popularity: 1.335485
First Submitted: 2011-12-03 05:58
Last Updated: 2019-04-14 18:10

Latest Comments

1 2 3 4 Next › Last »

jetm commented on 2019-07-26 13:54

@a216: Done. Thanks!

a216 commented on 2019-07-26 13:52

This project doesn't seem to show up in a search for "iwyu" - could this term be added as a keyword?

jetm commented on 2019-04-02 14:07

@Aetf: Clang v8 is out, but project upstream is not updated yet. I will update after upstream project update. Removing flag.

Aetf commented on 2019-03-31 19:08

Clang v8 is out...

jmarch commented on 2018-10-17 15:41

Please update to use the most recent clang v7.

Arvedui commented on 2018-08-29 07:46

And please replace patch -Np1 -i "../../fix-clang-6.patch" with patch -Np1 -i "${srcdir}/fix-clang-6.patch" as you can not rely on a relative position for source files.

selmf commented on 2018-07-01 20:34

The PKGBUILD is currently broken. Please add fix-clang-6.patch to the sources list to fix it.

pseyfert commented on 2018-05-29 17:18

@Parkotron Ran into the same error building by hand from github (tag clang_6.0). Cherry-picking more commits from master solves the issue. I suspect it's due to See also

Parkotron commented on 2018-05-15 18:24

I just attempted to modify the PKGBUILD for the recently released v0.10 (the Clang 6.0 version). After just changing the versions and hashes, everything build and installed without issue. Unfortunately, the tool fails to run, yielding

LLVM ERROR: inconsistency in registered CommandLine options
: CommandLine Error: Option 'asan-instrument-assembly' registered more than once!

Apparently this is due to linking against LLVM both statically and dynamically, but at this point I'm in over my head. Hopefully smarter folks will to take a look at packaging 0.10 soon.

spider-mario commented on 2018-04-29 21:06

It seems that the PKGBUILD could use clang50/llvm50 now that the repo packages are 6.0. Quick and dirty patch that does not use $_clang_major/$_clang_minor: