31 lines
1.2 KiB
Plaintext
31 lines
1.2 KiB
Plaintext
# pyDevSup as a module loadable via require
|
|
|
|
pyDevSup is not you standard EPICS extension in that it tightly interacts with the
|
|
python interpreter. This causes some issues with Dirk Zimochs module system which
|
|
allows to load support modules through the require command. Most importantly,
|
|
reuire does not know about python and its modules at all.
|
|
|
|
|
|
The good news is that it can be made to work but requires a few manual steps.
|
|
|
|
1) Build the pyDevSup extension in the normal EPICS way.
|
|
|
|
2) This generates a pythonXX/$(EPICS_ARCH)/devsup directory. Copy this directory to
|
|
a safe place.
|
|
|
|
3) Build the module using the GNUMakefile as normal and install it
|
|
|
|
4) Copy the saved devsup directory in some place into pyDevSup's module hierarchy.
|
|
For example: /ioc/modules/pyDevSup/koennecke/R3.14.12/lib/devsup
|
|
|
|
5) In order to successfuly load pyDevSup with require the directory underneath
|
|
where ypu placed pydevsup needs to be on the python path. For example:
|
|
/ioc/modules/pyDevSup/koennecke/R3.14.12/lib/
|
|
|
|
With this, one can at least run the testmodule.cmd script and it workd at least
|
|
for me.
|
|
|
|
Please use the module branch, I had to hack the initialisation of pyDevSup to make
|
|
it work as a module.
|
|
|