The install process consists of the classic step:
$ ./configure
$ make
$ sudo make install
The configure system is a plain script written in bash. It is not based on autoconf and automake. There are some configuration options that can be configured when starting the script. Here is a summary:
usage: ./configure [options]
options:
--prefix=<path>: installation prefix (default /usr/local)
--enable-debug: include debug symbols (default on)
--disable-debug: do not include debug symbols
--enable-profile: include profile symbols (default off)
--disable-profile: do not include profile symbols
--enable-shared: build dynamic linked library. (default on)
--disable-shared: build static linked library
--enable-npz: build system with .npz features. (default on)
--disable-npz: build system without .npz features.
all invalid options are silently ignored
The .npz file support depend on libzip library, and the configure script will check if libzip can
be found on the system before enabling the feature. A pkg-config .pc file will also be generated
and installed if an installation of pkg-config is found on the system.
There is also a 'uninstall' target in the Makefile.
If you are working on an embedded system, there might not be all tools available for running the configure script. It should then be pretty simple to just run a compiler that parses ANSI C99. For example:
gcc -std=c99 -c -I. -Wall -Wextra -O3 npy_array.c
will probably compile an object file that can be linked into your project.
Good luck!