-
Notifications
You must be signed in to change notification settings - Fork 38
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
features.json is missing from Windows installer for docc #337
Comments
DocC currently isn't usable on windows due to the missing pending change (CC: @FranzBusch). I'm happy to add the features.json for clang though. |
It seems that the clang features.json is already present. @jakepetroules is there something that I'm missing here? |
It's referenced in the WiX sources but doesn't actually get installed on the system. Does WiX not error out if it references a file that doesn't exist when building the installer? |
Yes, if the file is missing the installer will fail to build. |
Oh, looks like you fixed clang in fe35b36, but that's not in the 6.0 branch. I'll update the title to reflect that this is only an issue for docc, then. What's the docc usability issue you were referencing above? |
DocC cannot generate the documentation on Windows due to the use of |
Thanks for the reference. I think those two issues could be resolved in parallel, though. |
Yeah, I suppose that we could start building it. The one issue is the build times - I think that using CMake resulted in a 7% build time improvement as well as alleviated some bloat due to being able to do dynamic linking against other toolchain components. |
To be clear, we are currently shipping docc.exe as part of the Swift Windows installer already. Just the features.json is missing. |
Interesting, I don't remember getting that enabled, but that is great! |
Oh, you may be right. I remember seeing it in some toolchain build at least, maybe that was an older version and it's since been removed again. |
We probably need a section similar to this, but for docc:
The text was updated successfully, but these errors were encountered: