The Build ProcessNeuronetExperimenter
follows a similar convention to that used by most Unix software. That
is, generally new software is built using the commands, './configure;
make; make install'. The 'configure' command builds a Makefile, while
'make' builds the software into the local directory tree, and 'make
install' copies the binaries and associated files into the main system
Below we have listed several of the other build
targets provided in the generated 'Makefile' that may be of interest to
developers in particular:
Builds the core code including all the .oden-generated models and links the code into the NeuronetExperimenter binary. This is called when you just type 'make'.
all the compiled object files and linked libraries from the directory
tree. Useful for making sure that recently modified source code is
being properly linked into the executable.
what the 'clean' target does as well as removes the Makefile itself,
and all the other files generated during the buildModelCode.py
execution. This should result in a directory tree that is clean for
distribution to other systems.
First executes the 'models' target, then installs all the available binaries into the appropriate location on the system.
Removes the files from the system that were moved during the execution of the 'install' target.
Builds the netGen executable binary.
Builds the listToAdjmat executable binary.
Builds the analyzeNetwork executable binary.
Builds the 'models', 'netGen', 'listToAdjmat', and 'analyzeNetwork' targets.
ONLY: Autogenerates the Python stubs for the C++ class interfaces. This
requires the 'swig' executable to be in your PATH.
Builds the 'models' target and also builds the Python/C++ interface. This is the default target, and so is called when you just type 'make'.
Builds the pydocs for the generated Python interface. May be of interested for script developers.