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

Update vagrant configs for distros that have Python 3.6 available

Browse Source
This commit is contained in:
Robin Dunn
2017-01-30 15:13:13 -08:00
parent 07a7440093
commit e3d15a2d36
2 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
vagrant/README.rst
View File

@@ -39,7 +39,7 @@ The Vagrant VMs are provisioned to contain everything they need to build
Phoenix packages, except for two things: the source code and a build script to
do all the work. To make this a little simpler, the VMs are also configured to
share the ``{PhoenixRoot}/dist`` folder, and the
``{PhoenixRoot}/vagrant/scrtpts`` folder so they can access those two things
``{PhoenixRoot}/vagrant/scripts`` folder so they can access those two things
as well.
To perform a build there must be a Phoenix source tarball located in the
@@ -56,11 +56,11 @@ example::
Please note that currently this will do up to 6 complete builds, one for each
supported version of Python on that distro, for both gtk2 and gtk3. Additional
paramters can be passed to the ``build.sh`` script to narrow the build down to
parameters can be passed to the ``build.sh`` script to narrow the build down to
a specific Python version or port. See ``build.sh`` for details.
The wheel file(s) generated by the build will be placed in subfolders of
``{PhoenixRoot}/dist``.
``{PhoenixRoot}/dist/linux``.

4
vagrant/centos-7/bootstrap.sh
View File

@@ -20,12 +20,14 @@ yum -y install gtk2 gtk2-devel gtk3 gtk3-devel \
yum -y install python python-tools python-devel python-virtualenv
yum -y install python34u python34u-tools python34u-devel
yum -y install python35u python35u-tools python35u-devel
yum -y install python36u python36u-tools python36u-devel
# Set up virtual environments for each Python where the Phoenix builds will be
# done. set them to the vagrant user so the venv's can be updated by pip later.
# done. Set them to the vagrant user so the venvs can be updated by pip later.
mkdir venvs
virtualenv --python=python2.7 venvs/Py27
pyvenv-3.4 venvs/Py34
pyvenv-3.5 venvs/Py35
python3.6 -m venv venvs/Py36
chown -R vagrant:vagrant venvs