|
2 | 2 |
|
3 | 3 | In most cases, installing *stringi* is as simple as calling:
|
4 | 4 |
|
5 |
| - |
6 | 5 | ```r
|
7 | 6 | install.packages("stringi")
|
8 | 7 | ```
|
9 | 8 |
|
10 |
| - |
11 | 9 | However, due to the overwhelming complexity of the ICU4C library,
|
12 |
| -upon which *stringi* is based, and the colourful diversity of operating systems, |
13 |
| -their flavours, and particular setups, some users may still experience |
14 |
| -a few issues that hopefully can be resolved with the help of this short manual. |
| 10 | +upon which *stringi* is based, and the colourful diversity of environments |
| 11 | +it operates on, you might still experience a few issues. |
| 12 | +Hopefully, they can be resolved with the help of this short manual. |
15 | 13 |
|
16 |
| -Also, some build tweaks are possible. |
| 14 | +Below we also describe some available build process tweaks. |
17 | 15 |
|
18 | 16 |
|
19 | 17 | ## ICU4C
|
20 | 18 |
|
21 | 19 | The stringi package depends on the ICU4C >= 61 library.
|
22 | 20 |
|
23 |
| - |
24 |
| -If we install the package from sources and either: |
| 21 | +If we install the package from sources and one of the following is true: |
25 | 22 |
|
26 | 23 | * this requirement is not met (check out <https://icu.unicode.org/download>,
|
27 |
| - the `libicu-devel` rpm on Fedora/CentOS/OpenSUSE, |
28 |
| - `libicu-dev` on Ubuntu/Debian, etc.), |
| 24 | + the `libicu-devel` package on Fedora/CentOS/OpenSUSE, |
| 25 | + `libicu-dev` on Ubuntu/Debian, etc.), or |
29 | 26 |
|
30 | 27 | * `pkg-config` fails to find appropriate build settings
|
31 |
| - for ICU-based projects, or |
| 28 | + for ICU-based projects, or |
32 | 29 |
|
33 | 30 | * `R CMD INSTALL` is called with the `--configure-args='--disable-pkg-config'`
|
34 |
| - argument, or environment variable `STRINGI_DISABLE_PKG_CONFIG` is |
35 |
| - set to non-zero or |
| 31 | + argument, or the `STRINGI_DISABLE_PKG_CONFIG` environment variable |
| 32 | + is set to non-zero or |
36 | 33 | `install.packages("stringi", configure.args="--disable-pkg-config")`
|
37 | 34 | is executed,
|
38 | 35 |
|
39 |
| -then ICU will be built together with stringi. |
40 |
| -A custom subset of ICU4C 74.1 is shipped with the package. |
41 |
| - |
| 36 | +then ICU will be built together with stringi based on the customised |
| 37 | +ICU4C 74.1 source bundle that is shipped with the package. |
42 | 38 |
|
43 |
| -> To get the most out of stringi, you are strongly encouraged to rely on our |
44 |
| -> ICU4C package bundle. This ensures maximum portability across all platforms |
45 |
| -> (Windows and macOS users by default fetch the pre-compiled binaries |
| 39 | +> Actually, to get the most out of stringi, you are strongly encouraged to rely |
| 40 | +> on our ICU4C bundle. This ensures maximum portability across all platforms |
| 41 | +> (Windows and macOS users fetch the pre-compiled binaries |
46 | 42 | > from CRAN built precisely this way).
|
47 | 43 |
|
48 | 44 |
|
|
0 commit comments