Understanding and reorganization of NEURON libraries #2481
Replies: 1 comment
-
|
Some important information regarding the CMake targets/libraries build for NEURON and CoreNEURON. In CoreNEURON we have a static All below tests were run on an
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This discussion is instantiated to place my findings regarding what libraries are built for NEURON in different building scenarios.
This way I hope that we can get a better overview of all the different ways NEURON is built and how we can reorganize the libraries in such way that we make NEURON building easier to understand, more streamlined and less error prone.
The main
CMakeoptions that influence what and how libraries and executables of NEURON are built are the following:For different combinations of these options I will try to list the resulted libraries, executables and what purpose those options serve.
Some ideas for improvement:
direct modebetween NEURON and CoreNEURON we load in NEURON in nrncore_nrn the CoreNEURON library eitherlibcorenrnmech.sowhich is build usingnrnivmodl-corewith external mod files (fromx86_64) orlibcorenrnmech_internal.so. Instead of doing this dynamically during program execution we could manually link together at build timenrnivwithlibcorenrnmech_internal.soandspecialwithlibcorenrnmech.so. This would simplify both the recipes for building special/special-core and the running codeBeta Was this translation helpful? Give feedback.
All reactions