docs: Be explicit up front about getting the actual executable.#98
Open
gnprice wants to merge 2 commits into
Open
docs: Be explicit up front about getting the actual executable.#98gnprice wants to merge 2 commits into
gnprice wants to merge 2 commits into
Conversation
This is what it looks like for me with the v0.2.0 release (modulo adjusting the project's root directory to follow the example.) Various other bits of output in examples have also changed. But it'd be a lot of work to update them all comprehensively, and I think better to update piecemeal than not at all.
Looking at the getting-started page of the docs, because everything is in terms of `pyoxidizer run` it's not obvious how to actually lay hands on the single executable file that PyOxidizer produces. Here's one example of a puzzled would-be user: https://groups.google.com/forum/#!topic/pyoxidizer-users/rUyM3iTpZq0 Fix that by breaking up the first example into `pyoxidizer build` and then an explicit invocation of the built executable.
indygreg
force-pushed
the
main
branch
2 times, most recently
from
February 28, 2020 04:00
d719386 to
afbcecb
Compare
indygreg
force-pushed
the
main
branch
17 times, most recently
from
May 10, 2020 20:24
48fe3a7 to
48a4cab
Compare
indygreg
force-pushed
the
main
branch
6 times, most recently
from
November 22, 2020 20:03
b008149 to
3f2bf93
Compare
indygreg
force-pushed
the
main
branch
25 times, most recently
from
November 23, 2020 01:46
296b083 to
13e08f6
Compare
indygreg
force-pushed
the
main
branch
3 times, most recently
from
December 1, 2021 03:16
8f998b7 to
5c5ac33
Compare
indygreg
force-pushed
the
main
branch
2 times, most recently
from
May 31, 2022 04:07
5e0524b to
789c62e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Looking at the getting-started page of the docs, because everything
is in terms of
pyoxidizer runit's not obvious how to actuallylay hands on the single executable file that PyOxidizer produces.
Here's one example of a puzzled would-be user:
https://groups.google.com/forum/#!topic/pyoxidizer-users/rUyM3iTpZq0
Fix that by breaking up the first example into
pyoxidizer buildand then an explicit invocation of the built executable.
(Also a smaller preparatory commit.)