epsi
/
msspec_python3
3
0
Fork 0
Code Issues 6 Pull Requests Releases Wiki Activity

Change list formatting.
epsi-builds/msspec_python3/pipeline/head This commit looks good Details

This commit is contained in:
Sylvain Tricot 2021-02-22 15:52:42 +01:00
parent a4c13d3bdb
commit 7a64213a32
1 changed files with 29 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

57
README.md
View File

@ -12,26 +12,26 @@ Requirements
To compile MsSpec shared libraries, you need: To compile MsSpec shared libraries, you need:
- Python >= 3.6 - Python >= 3.6
- gfortran compiler - gfortran compiler
- cairo library (runtime files and header files) - cairo library (runtime files and header files)
Depending on your OS and Python version, you may need all the requirements (runtime libraries Depending on your OS and Python version, you may need all the requirements (runtime libraries
and header files) to build wxPython (please consult your distribution's package list for the and header files) to build wxPython (please consult your distribution's package list for the
appropriate package names) and their dependencies: appropriate package names) and their dependencies:
- python-dev (for your version of python) - python-dev (for your version of python)
- gtk (preferably version 3, but depends on your needs) - gtk (preferably version 3, but depends on your needs)
- gstreamer - gstreamer
- gstreamer-plugins-base - gstreamer-plugins-base
- glut - glut
- libwebkitgtk (matching your gtk version) - libwebkitgtk (matching your gtk version)
- libjpeg - libjpeg
- libpng - libpng
- libtiff - libtiff
- libsdl - libsdl
- libnotify - libnotify
- libsm - libsm
You also need a tool to create and manage Python virtual environments. For now only You also need a tool to create and manage Python virtual environments. For now only
*virtualenv* is supported. So if you plan to install msspec with the one-step command, *virtualenv* is supported. So if you plan to install msspec with the one-step command,
@ -70,23 +70,24 @@ make devel
``` ```
This will: This will:
- Create a Python virtual environment in the "\_venv" folder inside the msspec\_python3 folder.
- Install all the required Python packages in this virtual environment. - Create a Python virtual environment in the "\_venv" folder inside the msspec\_python3 folder.
- Install (or even maybe build) wxPython for your OS and Python version in this virtual environment. - Install all the required Python packages in this virtual environment.
- Build the msspec shared librarires. - Install (or even maybe build) wxPython for your OS and Python version in this virtual environment.
- Install msspec in *edit mode* in this virtual environment. - Build the msspec shared librarires.
- Install msspec in *edit mode* in this virtual environment.
You can tweak the process by specifying space separated key=value pairs on the command line. You can tweak the process by specifying space separated key=value pairs on the command line.
Allowed keys are: Allowed keys are:
- PYTHON, to give the executable name of the python interpreter to use rather than the default (python) - PYTHON, to give the executable name of the python interpreter to use rather than the default (python)
- VERBOSE, set to 1 if you want the install process to be more verbose - VERBOSE, set to 1 if you want the install process to be more verbose
- NO\_VENV, set to 1 to not create a virtual environment - NO\_VENV, set to 1 to not create a virtual environment
- VENV\_PATH, specify the path to a virtual environment root folder - VENV\_PATH, specify the path to a virtual environment root folder
- DEBUG, set to 1 to add debugging symbols - DEBUG, set to 1 to add debugging symbols
- BUILDDIR, to set a different name than the default to store building artifacts (./build) - BUILDDIR, to set a different name than the default to store building artifacts (./build)
- FC, the Fortran compiler to use (gfortran) - FC, the Fortran compiler to use (gfortran)
- F2PY - F2PY
Work with msspec Work with msspec