-
-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emscripten #826
Comments
I haven't been following Emscripten in quite a while, so I'm not sure about its status. However, judging from the below results from LLVM trunk, it doesn't seem to be supported in the way you think at all:
It does not.
My guess is that Clang interprets it as a linker script. At least that's what it seems to do on Linux, albeit with a warning.
LDC doesn't use OPTLINK at all. Regarding your observation, Clang probably tries to invoke the Microsoft |
|
Bummer :( I have another opportunity to get D into use in my company, but I need to be able to target at least Emscripten, ideally nacl too. Library is not important; -betterc would be a perfectly acceptable starting point. I'm happy to flesh out the runtime/phobos ports for those platforms as I go if there was a working compiler available. |
|
So why not just compile llvm yourself with the Emscripten backend included? |
|
Because I have no idea what I'm doing, and I don't have any free time to learn :( |
|
close? see |
|
Yeah, superseded by WebAssembly. |
Hey people, I was trying to use Emscripten with LDC. I didn't get very far.
As far as I can tell, Emscripten appears to be an officially supported platform in LLVM these days, so I figured there was good chance that it would 'just work'... but not so lucky.
I tried to supply
-mtriple=asmjs-unknown-emscripten, which as far as I can tell is the way to inform LLVM that my target shall be Emscripten, but it fails with:Error: unable to get target for 'asmjs-unknown-emscripten', see -version and -mtriple.Any ideas?
Tried this before?
On an unrelated side note, how is that that when I run Clang on a .d file, it somehow invokes LDC?
> clang test.d-> doesn't complain about d source code, then errors about OPTLINK, which is not what I was expecting (I initially invoked Clang by accident). There's no Clang exe in the LDC distribution (Windows)... so I can't imagine where that logic comes from?The text was updated successfully, but these errors were encountered: