Lerking/Phoenix
1
0
Fork 0
mirror of https://github.com/wxWidgets/Phoenix.git synced 2025-12-15 17:20:07 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Recursive submodule updates are needed now.

Browse Source
This commit is contained in:
Robin Dunn
2018-03-15 15:39:19 -07:00
parent 5505161843
commit 4a90db1c3b
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
README.rst
View File

@@ -79,8 +79,7 @@ you will need to do an additional step. The git repository is set up to bring
in the wxWidgets code as a git "submodule" so after cloning the Phoenix
repository, you can get the wxWidgets source with these commands::
$ git submodule init
$ git submodule update
$ git submodule update --init --recursive
This will clone the wxWidgets repo into: ``Phoenix/ext/wxWidgets``. Once the
submodule is updated, the build script should be able to build wxWidgets.
@@ -91,8 +90,8 @@ details. However be aware that doing so will require a wxWidgets that is
**very** close to the same age as the Phoenix code, at least for the
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 Phoenix is expecting to be used with
a wxWidgets built from the ``WX_3_0_BRANCH`` git branch.
Phoenix code was checked out. Currently the master branch of Phoenix is
tracking the master branch of wxWidgets.
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