Skip to content

Conversation

sunfishcode
Copy link
Member

This installs unqualified nm, ar, and other symlinks, additional
tools including llvm-objdump and llvm-objcopy, and additional clang
tools such as clang-format and clang-tidy.

This installs unqualified `nm`, `ar`, and other symlinks, additional
tools including `llvm-objdump` and `llvm-objcopy`, and additional clang
tools such as `clang-format` and `clang-tidy`.
Copy link
Collaborator

@pchickey pchickey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks great. we've done a bunch of changes here and in the libc lately. any idea when we want to cut a release?

@sunfishcode
Copy link
Member Author

We can do one any time. I'm interested in getting WebAssembly/wasi-libc#112 and a few related PRs into a release, but we don't need to block on that if you want to do something sooner.

@sunfishcode sunfishcode merged commit ccb15b0 into master Oct 23, 2019
@sunfishcode sunfishcode deleted the llvm-install-targets branch October 23, 2019 17:08
@pchickey
Copy link
Collaborator

ok, lets wait for that one and then do a release.

install-objdump \
install-objcopy \
install-c++filt \
llvm-config
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At some point it probably makes sense just install the whole of llvm (not the devel parts but the user parts) rather than trying maintain this long whitelist?

If space saving are what we are after a better approach would probably be to use LLVM_LINK_LLVM_DYLIB to avoid duplication between all the binaries? (This relies on -Wl,-rpath on linux .. so maybe there windows/mac portability issies?, but other investigating).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If there's a rule to install all the user parts, I'd be happy to switch to it.

And yeah, LLVM_LINK_LLVM_DYLIB is nice, but we should investigate its portability first.

install-clang-format \
install-clang-tidy \
install-clangQuery \
install-clang-apply-replacements \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do all of these targets existing llvm 8 too? Do want want to continue to support llvm-8?

Copy link
Member Author

@sunfishcode sunfishcode Oct 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't tested a full build, but they're all present in the llvm 8 source tree.

kildom pushed a commit to kildom/clang-wasi-port that referenced this pull request Jul 14, 2021
My understanding is that these dummy libs represent libraries who's
contents, under musl, live in libc itself rather than being split out
into separate libs.

libc++/libc++abi are not provided my musl so doesn't make sense to
pretend that we provide them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants