Lerking/Phoenix
1
0
Fork 0
mirror of https://github.com/wxWidgets/Phoenix.git synced 2026-01-27 14:10:07 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #2846 from vadz/improve-build-instructions

Browse Source 
Minor improvements to the build instructions in README
This commit is contained in:
Scott Talbert
2026-01-24 20:36:22 -05:00
committed by GitHub
parent 09516ed4f0 69adb5dc60
commit d70dd99974
1 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
README.rst
View File

@@ -120,7 +120,12 @@ details. However be aware that doing so will require a wxWidgets that is
unreleased preview snapshots. In other words, the wxWidgets build should use
code from the wxWidgets source repository within a few days of when the
Phoenix code was checked out. Currently the master branch of Phoenix is
tracking the master branch of wxWidgets.
tracking the master branch of wxWidgets. Also note that even when using an
external copy of wxWidgets with ``--use_syswx`` option, you still need the
contents of ``ext/nanosvg`` submodule for the build to succeed, so you will
still need to run at least::
git submodule update --init ext/nanosvg
On the other hand, it is probably best to just let wxPython build and bundle
wxWidgets. The build tools will by default build wxWidgets in a way that
@@ -228,7 +233,11 @@ Example build command-lines
^^^^^^^^^^^^^^^^^^^^^^^^^^^
To do a complete build from a totally clean git workspace, you will
need to use several of the commands listed above. For example::
need to install the requirements first with::
python -m pip install -r requirements.txt
and then use several of the commands listed above. For example::
python build.py dox etg --nodoc sip build