Skip to content

Include curses in macOS support package #109

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

Merged
merged 2 commits into from
Mar 6, 2021

Conversation

samschott
Copy link
Member

As discussed in beeware/briefcase#516, this PR includes curses in the support package.

MacOS already comes with ncurses bundled so we only need to include Python package and extension module, increasing the size of the support package by roughly 0.3 MB.

PR Checklist:

  • All new features have been tested
  • All new features have been documented
  • I have read the CONTRIBUTING.md file
  • I will abide by the code of conduct

Copy link
Member

@freakboy3742 freakboy3742 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 I've updated the patch so that it's compatible with the embedded executable changes from beeware/briefcase#525; otherwise, thanks for the patch!

@freakboy3742 freakboy3742 merged commit 576c68f into beeware:dev Mar 6, 2021
@samschott
Copy link
Member Author

Seems like curses was removed again from the Python 3.10 macOS build. Was this intentional?

@samschott samschott deleted the inlcude-curses branch November 28, 2021 09:56
@samschott samschott restored the inlcude-curses branch November 28, 2021 09:56
@samschott samschott deleted the inlcude-curses branch November 28, 2021 09:56
@samschott
Copy link
Member Author

Hm, I think this was a side effect of 7b35fc5.

@freakboy3742
Copy link
Member

Oh drat. No, it wasn't intentional; I got overzealous with some refactoring.

We (by which I mean, probably I) really do need to work out how to do an automated release test on these builds...

@samschott
Copy link
Member Author

This may be a stupid question, but why did excluding any of the other .so files not cause any problems?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants