document building with vcpkg

[ghost]

Document how to use vcpkg to build tectonic on macOS.
Adapted the details from #420.

[pkgw]

Thanks! The CI is complaining because you need to add a language specifier to the code blocks to prevent mdbook test from trying to compile them as Rust, like here.

[pkgw]

Also ... I am kind of old-fashioned and prefer hard linewraps at ~80 characters. Would one of those .editorconfig files encourage people's tools to do that kind of wrapping?

[ghost]

Ah, thanks, I'll fix that.
editorconfig is only for indentation and trailing white space I think.
We could explore a markdown linter or another kind of tool to enforce that.

[ghost]

Although they do have some research on the topic: https://github.com/editorconfig/editorconfig/wiki/Property-research:-maximum-line-length

[codecov]

Codecov Report

Merging #451 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #451      +/-   ##
==========================================
+ Coverage   45.54%   45.55%   +<.01%     
==========================================
  Files         138      138              
  Lines       59814    59814              
==========================================
+ Hits        27244    27246       +2     
+ Misses      32570    32568       -2

Impacted Files	Coverage Δ
tectonic/dpx-pdfobj.c	46.55% <0%> (+0.12%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fe9aaa0...78cd3fe. Read the comment docs.

[ghost]

I've worked with prettier but think that is overkill here.
We could consider using remark-lint to enforce the maximum length. Their rule document is here.

[pkgw]

Thanks for researching linters while you're at it!

FWIW I think I'd ideally like to have this text in a section of the book named Installation or Development (or maybe Contributing?), but as I wrote before, I think it's best to get text in first and rearrange later. I guess my current thinking is that Getting Started should have a Quick Installation section, which should point to an Installation document with less-common cases.

[ghost]

Certainly!
I think Installation or Development would be helpful sections. I would want to migrate the other description of how to build a static binary using docker to that section as well.
I also think we could move the fuzzing guide there as well.

[ghost]

In the spirit of being a Rust project, textwrap in a simple CLI would be great.