|
|
# Abstract #
|
|
|
This document outlines some guidelines for software in CDS. It is an aspirational document that is at least partially implemented at this time. It is targeted towards the full time software development effort.
|
|
|
This document outlines some guidelines for LIGO software in CDS. It is an aspirational document that is at least partially implemented at this time. It is targeted towards the full time software development effort.
|
|
|
|
|
|
This document is certainly not complete and is also certainly not structured correctly.
|
|
|
|
... | ... | @@ -209,7 +209,7 @@ If we are creating a base library that will be consumed by outside applications |
|
|
# Interfacing with multiple languages #
|
|
|
|
|
|
## SWIG ##
|
|
|
[Swig](https://www.swig.org/) is useful when interfacing C/C++ code with many different languages.
|
|
|
[Swig](http://swig.org/) is useful when interfacing C/C++ code with many different languages.
|
|
|
|
|
|
## PyBind11 ##
|
|
|
When a C++ library need only be exported to Python (and not to Java/Matlab/…) [PyBind11](https://pybind11.readthedocs.io/en/stable/) may be a better choice as it provides good integration and keeps the bindings in C++ (instead of the including another language [the SWIG system] into the mix).
|
... | ... | |