• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

.ci/H07-Sep-2021-6441

.github/workflows/H07-Sep-2021-170140

CMakeModules/H07-Sep-2021-258201

dev/H03-May-2022-969929

examples/H03-May-2022-6,3944,727

src/H03-May-2022-211,99277,228

submodules/H07-Sep-2021-

tests/H03-May-2022-17,76815,329

.gitattributesH A D07-Sep-2021483 2320

.gitignoreH A D07-Sep-20212 KiB175140

.gitmodulesH A D07-Sep-2021365 1110

.sonarcloud.propertiesH A D07-Sep-2021245 88

.travis.ymlH A D07-Sep-20211.5 KiB4140

NEWS.mdH A D07-Sep-2021998 3119

README.mdH A D07-Sep-20213.5 KiB6944

formatfiles.batH A D07-Sep-2021622 2623

formatfiles.shH A D07-Sep-2021586 3026

README.md

1# LibSEDML
2Some time ago I developed [libSedML](http://libsedml.sf.net) a C# library that fully supports [SED-ML](http://sed-ml.org) for SBML as well as CellML models for creation of the description just as for the execution of Simulation Experiments. However, frequently the question to a C++ based library comes up. This project makes use of [libSBML](http://sbml.org/Software/libSBML) XML layer as well as code generation as starting point to produce a library for reading and writing of SED-ML models.
3
4## Dependencies
5
6This library requires libSBML to be present, as its XML parsing layer will be used. for that either expat, xerces-c or libXML2 needs to be available. Additionally libSEDML makes use of libnuml. All dependencies are available as git submodule.
7
8## Building Python wheels
9
10Since all dependencies are included as submodules, be sure to checkout the project with submodules:
11
12	git clone --recurse-submodules https://github.com/fbergmann/libSEDML
13
14Then a build is as easy as:
15
16	cd libSEDML
17	python src/bindings/python/setup.py build
18
19or install, if you prefer. It requires cmake and swig installed.
20
21## Building
22
23This library uses [CMake](http://cmake.org) to build the library, so from an initial checkout all you would need todo is to run:
24
25
26    mkdir build
27    cd build
28    cmake -DLIBSBML_LIBRARY=< path to libsbml lib> -DLIBSBML_INCLUDE_DIR=< path to includes > ... -DEXTRA_LIBS= < comma separated list of xml libraries>
29    make
30    make install
31
32Should libSBML be installed in a default location it will be found automatically. Note that you do need to list the xml libraries that libSBML was linked against. In most cases libSBML is compiled against libXML and have compression enabled, so your `EXTRA_LIBS` would be:
33
34	EXTRA_LIBS=xml2;bz2;z;iconv
35
36note the semicolon denoting the listing of several libraries. Of course you could also enter the full path to each individual file, just to give an example, on windows I use:
37
38	EXTRA_LIBS=D:/dependencies/lib/expat.lib
39
40for linking against `expat` and indicating, that libSBML was compiled without compression.
41
42## License
43
44This project is open source and freely available under the [Simplified BSD](http://opensource.org/licenses/BSD-2-Clause) license. Should that license not meet your needs, please contact me.
45
46
47Copyright (c) 2013-2021, Frank T. Bergmann
48All rights reserved.
49
50Redistribution and use in source and binary forms, with or without
51modification, are permitted provided that the following conditions are met:
52
531. Redistributions of source code must retain the above copyright notice, this
54   list of conditions and the following disclaimer.
552. Redistributions in binary form must reproduce the above copyright notice,
56   this list of conditions and the following disclaimer in the documentation
57   and/or other materials provided with the distribution.
58
59THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
60ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
61WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
62DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
63ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
64(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
65LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
66ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
67(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
68SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
69