-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[question] will this package be published to PyPi? #3
Comments
Unfortunately, as currently implemented, pythonIoc must be generated as a standalone application, linked with your local EPICS installation, so I don't think this integrates terribly well with PyPi as it stands. However, we are already looking at this. @thomascobb, this is relevant to our meeting next week! |
If I recall correctly, pyepics can be installed through PyPi and also makes use of the local installation of EPICS(if present). I wonder if we can borrow some ideas from them. I am a pure noob on EPICS so please forgive me if I am missing some common sense here. |
Some work that @mdavidsaver did on epicscorelibs may help us here. He already did the hard work of packaging EPICS base for all the major arches via CI, and added a dynamic registerRecordDeviceDriver. We could either copy his work and build binary packages via CI here, or maybe even repackage this to be called from ctypes rather than building anything? Not sure if that would work... We'll discuss next week. |
What about a docker container? The container can provide the same functionalities as a pip package. The image would be built with a specific epics version (from source) and a specific python version (most probably from source too). |
Working on this in #5 |
This is now available in beta form at https://pypi.org/project/softioc/. |
The README and docs both require to manually install this package. I wonder if there is a plan to publish it to PyPi so that we can use the
pip
tool to manage this package.If yes, please tell the schedule. If no, please tell the reasoning behind.
// This tool is awesome! Thx for your work!
The text was updated successfully, but these errors were encountered: