Repository navigation
Daemon and Python module become linkable libraries - #47
Conversation
core declares its own camerad and module only when top-level
|
The library restructure is great! The second change removes the ability to have per instrument python packages, it would mean one python environment per instrument, for Hispec and possibly for future instruments retaining the flexibility of multiple instrument builds per env would be nice to have. |
with camerad and emulator named for it * CAMERAD_PYTHON_PACKAGE, empty by default, leaves generic build unchanged
|
@mikelangmayr I updated this so that multiple instruments can share one environment without a per-build module name. I made a new install-inly setting, Use a So |
mikelangmayr
left a comment
There was a problem hiding this comment.
This is great! Thanks Dave
required to meet camera 2.0 design
The daemon and Python module are now libraries,
camerad_daemonandcamerad_python, withcamerad::names. The core builds its owncameradand module only when top-level, and an instrument's build declares its own and links these.External libs moved onto libs that use them.
The module always imports as
camera_interface, one instrument per Python process. @mikelangmayr this meanspackage/trackingnow buildscamera_interfacetoo, so use one environemnt per instrument.This replaces PR #46 .
Verified locally with generic, hispec, and python.
CI jobs that check out submodules will continnue to fail for now.