-
Notifications
You must be signed in to change notification settings - Fork 153
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
build GenerateReferenceDocs succeeds, but produces no output #231
Comments
It also appears that ReferenceBinaries isn't set properly during the init phase - it's coming through as empty. However, setting it up manually doesn't seem to change the output. |
After further investigating, it appears that the
And then run, the main help generation succeeds (and prints as expected), but I then see:
Note that the FAKE.exe line reported (and I verified this) is being called with (Again, this is using the standard build.fsx/generate.fsx, with the only "change" being running the setup once) |
is a workaround until we know how to solve fsharp/fsharp-compiler-docs#511 |
It was an issue with FAKE's script caching. fsiOptions need to invalidate the cache as well. In order to fix your issue: "paket update nugate FAKE" should do the trick cc @matthid |
Thanks for the CC. I think this was one of the arguments for FAKE targets instead of compiler directives. I really think we should make the documentation generation a proper FAKE script with multiple targets. |
I've been trying to update my project to use the latest ProjectScaffold, but even with a brand new copy (just download and build, on Windows, using VS2013 tools),
build GenerateReferenceDocs
succeeds, but generates no output.The build step runs, and shows:
But, as you can see from the above, nothing is put in the
reference
folder under output, and no reference docs are generated.Again, this was just taking the current master, downloading as a zip, running build, then
build GenerateReferenceDocs
- with no changes or updates. The command "succeeds" but doesn't seem to actually generate the reference folder or documentation.The text was updated successfully, but these errors were encountered: