Hello,
What is the correct way to include a library to an EPICS app?
What I've been doing so far:
1. I precompile the library (so I've got an .a or *.so file),
2. Copy the header file into $(TOP)/include/
3. Then add my library to $(TOP)/helloapp/src/Makefile
hello_LIB += my_library
4. cd $(TOP)
5. make
6. Copy libmy_library.so to $(TOP)/lib/$(EPICS_HOST_ARCH)/
7. Hi!
Now, I don't like the process of manually creating these folders, which upon next make uninstall clean will be deleted.
What I wanted is to specify the path to libmy_library.so in the RELEASE file, and simply include it in the src/Makefile. As far as I understand, it's neither an EPICS module, nor a support app. Otherwise, it would be pretty much straightforward.
What if my library is installed via make install (header file and *.so are copied to /usr/local/) or is a standard linux lib? Is there a difference if I use shared vs. static lib?
What about the architecture (x86 vs x86_64)?
--
Best regards,
Pavel Maslov, MS
Controls Engineer at Pulsed power Lab
Efremov Institute for Electro-Physical Apparatus
St. Petersburg, Russia
Mobile: +7 (951) 672 22 19
Landline: +7 (812) 461 01 01