You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After reading your documentation, I was led to an incorrect understanding of how to use the --library-path option for mdbook test.
What it says:
The --library-path (-L) option allows you to add directories to the library
search path used by rustdoc when it builds and tests the examples. Multiple
directories can be specified with multiple options (-L foo -L bar) or with a
comma-delimited list (-L foo,bar).
What I thought it meant:
Pass the cargo workspace as an argument. (e.g. -L project/)
What it actually meant:
Pass the compilation artifacts as an argument. (e.g. -L project/target/debug/deps/)
How I found out what it actually meant:
I looked through the code, until I determined that it repasses the argument to rustdoc.
I looked at the rustdoc guide, which contained an example that corrected my misconception.
It looks like the person who wrote this issue had the same misconception that I did.
The text was updated successfully, but these errors were encountered:
After reading your documentation, I was led to an incorrect understanding of how to use the
--library-path
option formdbook test
.What it says:
What I thought it meant:
What it actually meant:
How I found out what it actually meant:
rustdoc
.rustdoc
guide, which contained an example that corrected my misconception.It looks like the person who wrote this issue had the same misconception that I did.
The text was updated successfully, but these errors were encountered: