Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
fengzch-das
multibuild
Commits
8d02160d
Commit
8d02160d
authored
Sep 26, 2016
by
Andrew Murray
Committed by
GitHub
Sep 26, 2016
Browse files
Fixed typos
parent
5baab77d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
README.rst
README.rst
+2
-2
No files found.
README.rst
View file @
8d02160d
...
@@ -108,7 +108,7 @@ It then (in the container) runs the real ``install_run`` command, which comes
...
@@ -108,7 +108,7 @@ It then (in the container) runs the real ``install_run`` command, which comes
Standard build and test functions
Standard build and test functions
*********************************
*********************************
The standard build comm
m
and is ``build_wheel``. This is a bash function. By
The standard build command is ``build_wheel``. This is a bash function. By
default the function that is run on OSX, and in the Manylinux container for
default the function that is run on OSX, and in the Manylinux container for
the build phase, is defined in ``multibuild/common_utils.sh``. You can
the build phase, is defined in ``multibuild/common_utils.sh``. You can
override the default function in the project ``config.sh`` file (see below).
override the default function in the project ``config.sh`` file (see below).
...
@@ -131,7 +131,7 @@ but you in that case you will need to define a ``run_tests`` function, to run
...
@@ -131,7 +131,7 @@ but you in that case you will need to define a ``run_tests`` function, to run
your tests, returning a non-zero error code for failure. The default
your tests, returning a non-zero error code for failure. The default
``install_run`` implementation calls the ``run_tests`` function, which you
``install_run`` implementation calls the ``run_tests`` function, which you
will likely define in ``config.sh``. See the examples below for examples of
will likely define in ``config.sh``. See the examples below for examples of
less and more complicate
b
builds, where the complicated builds override more
less and more complicate
d
builds, where the complicated builds override more
of the default implementations.
of the default implementations.
********************
********************
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment