-
Notifications
You must be signed in to change notification settings - Fork 7
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
Compilation failures due to ambiguous dependencies for code blocks #9
Comments
The example I gave with changing features at least has a workaround: you can delete the directory I think the fundamental problem is that getting the rustc command-line arguments right is difficult in the general case. I don't currently understand the approach taken in
|
Thanks for the ideas, I'll investigate this further. |
So I've looked into it, and I think using some of these features is just going to cause more headaches. I think my new plan works, but I'd love your thoughts. For each test:
This should even mean we don't need any list of |
It's still an issue when you are working with |
Some examples fail to compile because rustc can't resolve the extern/dependencies.
A small, concrete example (mdbook-keeper-tokio.zip):
Initially, if we run
mdbook serve
the test fails because tokio didn't include the macro feature. So, we update Cargo.toml toNow, if we
mdbook serve
we'll get a compiler error like the following:I've observed a couple seemingly-similar problems
thiserror
conflicts between the Cargo workspace for the book and the one in sysroot (due to usingbuild-std
at one point, I think???)tokio
fails to link on Windowserror: linking with
link.exefailed: exit code: 1181 = note: LINK : fatal error LNK1181: cannot open input file 'windows.0.48.0.lib'
(dump of paths omitted, full error below)Full error for Tokio on Windows:
The text was updated successfully, but these errors were encountered: