Skip to content

Commit dfd8d2c

Browse files
Update build.md
1 parent 5617086 commit dfd8d2c

1 file changed

Lines changed: 17 additions & 20 deletions

File tree

build.md

Lines changed: 17 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,21 @@
11
## Building P4Python from Source
22

3-
1. Download the r23.1 Perforce C++ API from the Perforce FTP site at
4-
"ftp://ftp.perforce.com/perforce". The API archive is located
5-
in release and platform-specific subdirectories.
3+
1. Download the corresponding Perforce C++ API (e.g. if you trying to build P4Python 2023.1, download the r23.1 P4API) from
4+
https://ftp.perforce.com/perforce. The API archive is located in release and platform-specific subdirectories.
65

7-
Under Linux the p4api is named p4api-glib<GLIBVER>-openssl<SSLVER>.tgz\
8-
Note that setup.py will download the correct p4api automatically from
9-
ftp.perforce.com if you do not provide an --apidir parameter to the
10-
setup.py "build" command.
6+
Under Linux, the p4api is named _p4api-glib\<GLIBVER>-openssl\<SSLVER>.tgz_
7+
8+
Note that setup.py will download the correct p4api automatically from
9+
https://ftp.perforce.com/perforce if you do not provide an\
10+
_--apidir_ parameter to the "setup.py build" command.
1111

1212
Mac OS X users should get the API from the relevant platform directory e.g.
13-
"**bin.macosx1010x86_64**" or "**bin.macosx12arm64**". The p4api is named
14-
p4api-openssl<SSLVER>.tgz
13+
"**bin.macosx1015x86_64**" or "**bin.macosx12arm64**".\
14+
The p4api is named _p4api-openssl\<SSLVER>.tgz_
1515

1616
Under Windows the p4api needs to match your compiler, build type (static
1717
or dynamic) and SSL version. for instance:
18-
19-
"**p4api_vs2010_static_openssl1.1.1.zip**" or\
20-
"**p4api_vs2015_dyn_openssl1.0.2.zip**"
18+
"**p4api_vs2019_static_openssl3.zip**" or "**p4api_vs2019_dyn_openssl3.zip**"
2119

2220
Note: 32-bit builds of P4Python require a 32-bit version of the
2321
C++ API and a 32-bit version of Python. 64-bit builds of
@@ -26,33 +24,32 @@
2624

2725
Unzip the archive into an empty directory.
2826

29-
2. Download and extract the P4Python API archive into a new, empty directory.
27+
4. Download the P4Python source code from https://github.com/perforce/p4python and extract the archive into a new empty directory.
3028

31-
3. If needed, install the Openssl libraries.
29+
5. If needed, install the Openssl libraries.
3230

33-
4. To build P4Python, run the following command:
31+
6. To build P4Python, run the following command:
3432

35-
_python3 setup.py build --apidir <Perforce C++ API absolute path>
36-
--ssl <OpenSSL library path> _
33+
_python3 setup.py build --apidir <Perforce C++ API absolute path> --ssl \<OpenSSL library path>_
3734

3835
Note: in order to reinstall cleanly P4Python, remove the
3936
directory named "build".
4037

41-
5. To test your P4Python build, run the following command:
38+
7. To test your P4Python build, run the following command:
4239

4340
_python3 p4test.py_
4441

4542
Note: this test harness requires the Perforce server executable
4643
p4d 17.1 or better to be installed and in the PATH.
4744

48-
6. To install P4Python, run the following command:
45+
8. To install P4Python, run the following command:
4946

5047
_python3 setup.py install_
5148

5249
if this doesn't work, you may need to both build and install in the same
5350
incantation:
5451

55-
_python3 setup.py build --apidir <Perforce C++ API absolute path> --ssl <OpenSSL library path> install_
52+
_python3 setup.py build --apidir <Perforce C++ API absolute path> --ssl \<OpenSSL library path> install_
5653

5754
Note: on Unix/Mac platforms, the installation must be performed
5855
as the root user, so usually these commands are preceded by "sudo".

0 commit comments

Comments
 (0)