Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix monospace render problem in tutorial #349

Merged
merged 1 commit into from
Dec 12, 2023
Merged

Fix monospace render problem in tutorial #349

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/src/tutorial.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -426,7 +426,7 @@ exe app : app.cpp core ;
This works no matter what kind of linking is used. When `core` is built as a
shared library, links `utils` directly into it. Static libraries can't link
to other libraries, so when `core` is built as a static library, its
dependency on `utils` is passed along to `core`'s dependents, causing `app`
dependency on `utils` is passed along to ``core``'s dependents, causing `app`
to be linked with both `core` and `utils`.
====

Expand Down Expand Up @@ -515,7 +515,7 @@ exe app : app.cpp ../util/lib2//lib2 ;
----

As with any target, the alternative selected depends on the properties
propagated from `lib2`'s dependents. If we build the release and debug
propagated from ``lib2``'s dependents. If we build the release and debug
versions of `app` it will be linked with `lib2_release.a` and
`lib2_debug.a`, respectively.

Expand Down