polysquare / clang-conan

Clang compiler and tools for Conan
MIT License
3 stars 2 forks source link

clang doesn't package the actual clang binary #2

Open russelltg opened 7 years ago

russelltg commented 7 years ago

Hey!

I know this is an old project but I'm looking for a bit of support.

It seems that after running conan install clang/3.8.0@smspillaz/stable --build and looking inside the package directory there isn't a clang executable!

My system: Arch Linux GCC 6.2.1

In the package directory:

$ pwd
/home/russellg/.conan/data/clang/3.8.0/smspillaz/stable/package/64e4f631b5b6e48c61788344ac830b9abb1e9726
$ ls bin
c-index-test  clang-apply-replacements  clang-query  clang-rename  clang-tidy  modularize  scan-build  scan-view
smspillaz commented 7 years ago

Looks like this project is getting some attention!

I can certainly have a look into that issue. It has been a while since I last worked on this, but I suspect it may be because the binary is not being built and thus not copied over. Maybe there is a new command line option.

smspillaz commented 7 years ago

Hey, I saw that you closed your PR.

I'm still not entirely sure what the best way forward is for this. As I mentioned in the PR - we're disabling building the binary since I don't think there's a meaningful way it can be used. However, I haven't used conan in a while and things may have changed. Did you have any thoughts on that?

russelltg commented 7 years ago

Well it's useful for me because I call clang from the library I create, so I'm not actually using it to build my library.

I was just cleaning up branches and forgot I still had an open PR :laughing:

smspillaz commented 7 years ago

Interesting. If you don't mind me asking, what are you calling clang for? Sounds like there may be a usecase here.

smspillaz commented 7 years ago

Ah I see, you're calling it directly from a library at runtime (and so you need clang to be in PATH for that to work).

To be honest, I don't see the harm in including CFE in that case. The only problem is that clang's build time is quite long and I had tried to slim down the build earlier to get it to build on the public travis buildbots. It looks like that isn't going to happen, so I'm looking around for other infrastructure to get the binary packages to build (I don't think everyone wants to compile their own copy of clang N times).