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.

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

Add documentation about packaging with tkinter. #146

Merged
merged 1 commit into from Apr 5, 2018

Conversation

@ntoll
Copy link
Contributor

ntoll commented Mar 16, 2018

Not sure this is in the right place, so please feel free to move and/or change it as you see fit.

FYI: The work done in Mu to automate this can be found in this PR: mu-editor/mu#391 and makes use of this repository: https://github.com/mu-editor/mu_tkinter

Copy link
Owner

takluyver left a comment

Thanks! This mostly looks like a good description. I'd suggest putting it in FAQ rather than here. It's admittedly a rather vague title, but the idea is that 'installer details' describes the installers and installations that Pynsist produces. Suggestions for better titles for that topic are welcome!

a GUI then you need to find the following assets:

* The ``tcl`` directory in the root directory of the version of Python you are
using in your app. This must be the same bitness and version.

This comment has been minimized.

Copy link
@takluyver

takluyver Mar 17, 2018

Owner

We should say somewhere that these files need to come from a Windows install of Python, since the idea of Pynsist is generally that you can build from Linux/Mac as well, and this is a case where that doesn't easily work.

The ``tcl`` directory should be copied into the root of your project and
renamed to ``lib`` (this is important!).

Create a new directory in the root of your project called ``pynsis_pkgs`` and

This comment has been minimized.

Copy link
@takluyver

takluyver Mar 17, 2018

Owner

pynsist_pkgs (you've missed the t)

Build your installer and test it. You'll know everything is in the right place
if the directory into which your application is installed contains a ``lib``
directory containing the contents of the original ``tcl`` directory and the
``Python`` directory contains the remaining four files. If things still don't

This comment has been minimized.

Copy link
@takluyver

takluyver Mar 17, 2018

Owner

I think they should end up in the pkgs directory, not Python.

@takluyver takluyver merged commit d0f8b03 into takluyver:master Apr 5, 2018
2 checks passed
2 checks passed
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.