New Apple LLVM Clang not supported

[ioquatix]

New Apple LLVM Clang not supported

[dholzenburg]

Any updates on this one?

I would like to use
https://github.com/Sellegit/j2objc/tree/master/runtime
which itself uses
https://github.com/robovm/robovm-bro-gen

which uses this project .

I'm trying to execute a script from the top project

./gen_binding.sh 
Invalid/unsupported clang version string.

My current environment:

/usr/bin/clang --version
Apple LLVM version 7.0.2 (clang-700.1.81)
Target: x86_64-apple-darwin15.3.0
Thread model: posix

Same output for
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang --version

[ioquatix]

Can you please submit a PR and I will merge and release.

[ioquatix]

Okay I've merged a PR to add support for this, and released 0.3.0 but the specs are still failing because the string doesn't match the spec expectation.. I guess that is an easy fix.

Do you think there is any way to get the version numbers rather than having to parse the string?

[dholzenburg]

Thank you for merging.

Regarding the version numbers I found this after some researching:

[(http://lists.llvm.org/pipermail/llvm-dev/2015-September/090560.html)]

At the moment I don't have any idea how to deal with that.

[ioquatix]

I was actually thinking perhaps we should just remove the version check. It was more important when 3.2 and 3.3. and 3.4 all had different functionality which we had to be careful about. What do you think?

[dholzenburg]

Maybe yes. It's probably better to check the availability of features instead the version string.

But I have to admit my knowledge about the whole topic is ending at this point. I am no clang expert and I don't have any real idea about ruby and ffi.

[ioquatix]

I think using the version to check for features is a bad idea ultimately. Especially we have a case where it doesn't work. I think I'll rip out all the version detection code and related decisions. we won't support any old versions of libclang (< 3.5). Who cares about those versions now anyway? It would be nice to do a 1.0 release too, with solid support for a specific minimum version.