You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,8 @@ Running stdlib **requires** the following prerequisites:
64
64
65
65
Most functionality in stdlib is implemented exclusively in JavaScript; however, some implementations try to capture performance benefits by using [native bindings][node-js-add-ons] and/or [WebAssembly][webassembly]. While **not** required to run stdlib, as **every** stdlib implementation has a JavaScript fallback, the following dependencies are **required** for building native add-ons, including linking to BLAS and LAPACK libraries:
66
66
67
-
-[GNU make][gnu-make]: development utility and task runner
67
+
-[GNU make][make]: development utility and task runner
68
+
-[GNU bash][bash]: an sh-compatible shell
68
69
-[gcc & g++][gcc] or [Clang][clang]: C/C++ compilation and linking (g++ version `>= 4.8`; clang version `>= 3.5`, Xcode version `>=8.3.1` on OS X)
69
70
-[gfortran][gfortran]: Fortran compilation and linking (version `>= 4.8`)
Copy file name to clipboardExpand all lines: docs/development.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
7
7
We are super excited that you have decided to develop stdlib, and we welcome you to the stdlib developer community. We have done our best to provide a complete environment for testing, benchmarking, documenting, and developing project code. And if you have any ideas as to how we can make it better, let us know!
8
8
9
-
Before we begin, developing stdlib requires some setup and configuration. What follows is an overview of environment requirements and a sequence of steps for getting up and running with stdlib. We use [Git][git] for version control, and for most tasks, we use [GNU make][gnu-make] (the original task runner) to help us get things done quickly and effectively. For the most part, the project is able to internally manage dependencies for testing, benchmarking, and linting, so, once you follow the steps below, you should be ready to start developing!
9
+
Before we begin, developing stdlib requires some setup and configuration. What follows is an overview of environment requirements and a sequence of steps for getting up and running with stdlib. We use [Git][git] for version control, and for most tasks, we use [GNU make][make] (the original task runner) to help us get things done quickly and effectively. For the most part, the project is able to internally manage dependencies for testing, benchmarking, and linting, so, once you follow the steps below, you should be ready to start developing!
10
10
11
11
So, without further ado, let's get you started!
12
12
@@ -15,7 +15,8 @@ So, without further ado, let's get you started!
15
15
Developing and running stdlib **requires** the following prerequisites:
16
16
17
17
-[Git][git]: version control
18
-
-[GNU make][gnu-make]: development utility and task runner
18
+
-[GNU make][make]: development utility and task runner
19
+
-[GNU bash][bash]: an sh-compatible shell
19
20
-[curl][curl], [wget][wget], or [fetch][fetch] (FreeBSD): utilities for downloading remote resources
Copy file name to clipboardExpand all lines: docs/links/database.json
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -3065,6 +3065,16 @@
3065
3065
"build"
3066
3066
]
3067
3067
},
3068
+
"https://www.gnu.org/software/bash/": {
3069
+
"id": "bash",
3070
+
"description": "The official site of GNU bash, an sh-compatible shell.",
3071
+
"short_url": "",
3072
+
"keywords": [
3073
+
"bash",
3074
+
"gnu",
3075
+
"shell"
3076
+
]
3077
+
},
3068
3078
"https://www.gnu.org/software/make/": {
3069
3079
"id": "make",
3070
3080
"description": "A development utility which controls the generation of executables and other non-source files of a program from the program's source files.",
-[limitations of usual tools](https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Limitations-of-Usual-Tools.html#Limitations-of-Usual-Tools)
# * `.SHELLFLAGS` was introduced in GNU Make 3.82 and has no effect on the version of GNU Make installed on Mac OS X, which is 3.81.
26
+
# * The `-e` flag causes `bash` to exit immediately if a `bash` executed command fails.
27
+
# * The `-u` flag causes `bash` to exit with an error message if a variable is accessed without being defined.
28
+
# * The `pipefail` option specifies that, if any of the commands in a pipeline fail, the entire pipeline fails. Otherwise the return value of a pipeline is the return value of the last command.
29
+
# * The `-c` flag is in the default value of `.SHELLFLAGS`, which must be preserved, as this is how `make` passes the script to be executed to `bash`.
30
+
#
31
+
.SHELLFLAGS := -eu -o pipefail -c
32
+
33
+
# Remove targets if its recipe fails.
34
+
#
35
+
# ## Notes
36
+
#
37
+
# * Mentioning this target anywhere in a Makefile prevents a user from re-running make and using an incomplete or invalid target.
38
+
# * When debugging, it may be necessary to comment this line out so the incomplete or invalid target can be inspected.
Copy file name to clipboardExpand all lines: tools/make/lib/addons/Makefile
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ endif
29
29
# This target installs native add-ons. If unable to install a native add-on, the target prints an error message and proceeds to try installing the next add-on.
0 commit comments