We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 3677 - SDL2 cannot be compiled with CLANG, LLVM-vs2014, vs2017, v141
Summary: SDL2 cannot be compiled with CLANG, LLVM-vs2014, vs2017, v141
Status: ASSIGNED
Alias: None
Product: SDL
Classification: Unclassified
Component: *don't know* (show other bugs)
Version: 2.0.5
Hardware: x86_64 Windows 10
: P2 enhancement
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-22 05:46 UTC by Paul
Modified: 2017-08-19 10:13 UTC (History)
0 users

See Also:


Attachments
result of building via LLVM-vs2014 chain (31.57 KB, text/plain)
2017-06-22 05:46 UTC, Paul
Details
remaining warnings after removing files (55.52 KB, text/plain)
2017-06-22 09:40 UTC, Paul
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul 2017-06-22 05:46:13 UTC
Created attachment 2766 [details]
result of building via LLVM-vs2014 chain

Flooded with bad defines and cant find identifiers correctly, bad includes.
Comment 1 Paul 2017-06-22 09:40:28 UTC
Created attachment 2767 [details]
remaining warnings after removing files

Ok, after removing SDL_string.c and SDL_fillrect.c, it compiled with a long list of warnings that need fixing, which might be fine for now as I don't need either of those components...
Comment 2 Paul 2017-06-22 09:42:34 UTC
I will also note, some log and build directories need fixing in cmake as it currently places them outside the build tree, you'll see which ones when you do a full build.
Comment 3 Sam Lantinga 2017-08-19 10:13:43 UTC
This is partially fixed with this commit, allowing SDL applications to build with clang on Visual Studio:
https://hg.libsdl.org/SDL/rev/6ae35c5f7f7b

We don't currently support building SDL with LLVM on Windows, so I'm lifting this bug from blocking the 2.0.6 release.

Please feel free to submit a patch if you implement this yourself.