aboutsummaryrefslogtreecommitdiff
path: root/reproduce/software/config/numpy-scipy.cfg
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2020-04-17 01:06:20 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-04-17 01:06:20 +0100
commit8eb0892e179b4970a9835d29b5f57dd912ca4464 (patch)
treeb0858d1021efc399106e2936aa44c4fc37196edb /reproduce/software/config/numpy-scipy.cfg
parente0a57efde9206c0c7420e03e5fb2a354d568c3ad (diff)
IMPORTANT: software config directly under reproduce/software/config
Until now the software configuration parameters were defined under the `reproduce/software/config/installation/' directory. This was because the configuration parameters of analysis software (for example Gnuastro's configurations) were placed under there too. But this was terribly confusing, because the run-time options of programs falls under the "analysis" phase of the project. With this commit, the Gnuastro configuration files have been moved under the new `reproduce/analysis/config/gnuastro' directory and the software configuration files are directly under `reproduce/software/config'. A clean build was done with this change and it didn't crash, but it may cause crashes in derived projects, so after merging with Maneage, please re-configure your project to see if anything has been missed. Please let us know if there is a problem.
Diffstat (limited to 'reproduce/software/config/numpy-scipy.cfg')
-rw-r--r--reproduce/software/config/numpy-scipy.cfg47
1 files changed, 47 insertions, 0 deletions
diff --git a/reproduce/software/config/numpy-scipy.cfg b/reproduce/software/config/numpy-scipy.cfg
new file mode 100644
index 0000000..82cc1e1
--- /dev/null
+++ b/reproduce/software/config/numpy-scipy.cfg
@@ -0,0 +1,47 @@
+# THIS IS A COPY OF NUMPY'S site.cfg.example, CUSTOMIZED FOR THIS TEMPLATE
+# ------------------------------------------------------------------------
+
+# This file provides configuration information about non-Python
+# dependencies for numpy.distutils-using packages. Create a file like this
+# called "site.cfg" next to your package's setup.py file and fill in the
+# appropriate sections. Not all packages will use all sections so you
+# should leave out sections that your package does not use.
+#
+# Copyright (C) 2018-2020 Mohammad Akhlaghi <mohammad@akhlaghi.org>
+# Copyright (C) 2019-2020 Raul Infante-Sainz <infantesainz@gmail.com>
+#
+# Copying and distribution of this file, with or without modification, are
+# permitted in any medium without royalty provided the copyright notice and
+# this notice are preserved. This file is offered as-is, without any
+# warranty.
+
+# IMPORTANT NOTE
+# --------------
+#
+# The `ALL' grouping does't apply to ATLAS!!!!!
+
+ [ALL]
+ library_dirs = @LIBDIR@
+ include_dirs = @INCDIR@
+
+
+# FFT libraries
+# -------------
+# There are two FFT libraries that we can configure here: FFTW (2 and 3) and djbfft.
+# Note that these libraries are not used by numpy or scipy.
+#
+# http://fftw.org/
+# https://cr.yp.to/djbfft.html
+#
+# Given only this section, numpy.distutils will try to figure out which version
+# of FFTW you are using.
+
+# Even with this section, Numpy apparently does not use fftw. But we will
+# keep it here for the future (if a solution is found).
+[fftw]
+libraries = fftw3
+#
+# For djbfft, numpy.distutils will look for either djbfft.a or libdjbfft.a .
+#[djbfft]
+#include_dirs = /usr/local/djbfft/include
+#library_dirs = /usr/local/djbfft/lib