Experimental Physics and
Industrial Control System

Hi Pavel,

 

Here are the answers for 2 scenarios, which I was just working on today.  In my case I want to have the TIFF library available in my EPICS areaDetector package.

 

For Linux I could just require users to install the libtiff package as they would any other package.  In that case I can just to “include <tiff.h>” in my EPICS application and the system will find the file, and I can add the following to my application Makefile.  This answers your question about installing to /usr/local, Linux will find it there.

 

PROD_SYS_LIBS_Linux    += tiff jpeg z

 

But in the case of Windows I could not find a pre-built TIFF library for 64-bit Windows on the Web.  So I decided that for Windows the TIFF library should be built from source code as part of my application.  This way others who want to use my application are guaranteed to have the required library without having to mess around building it themselves.

 

Here is what I did

 

-          Created a tiffSrc directory in my application

-          Copied the latest TIFF source code from /tiff-4.0.3/libtiff into tiffSrc

-          Re-write the Makefile to use EPICS build system

-          tif_stream.cxx renamed to tif_stream.cpp for EPICS compatibility

-          tif_confix.vc.h copied to tif_config.h

-          tiffconf.vc.h copied to tiffconf.h

 

The following is tiffSrc/Makefile (with some source files deleted for brevity):

#########################################

TOP=../../..

include $(TOP)/configure/CONFIG

#----------------------------------------

#  ADD MACRO DEFINITIONS AFTER THIS LINE

#=============================

 

INC_WIN32 += tiff.h tiffio.h tiffvers.h tiffconf.h

 

LIBRARY_IOC_WIN32 = tiff

 

LIB_SRCS += tif_aux.c

LIB_SRCS += tif_close.c

LIB_SRCS += tif_codec.c

LIB_SRCS += tif_color.c

LIB_SRCS += tif_compress.c

…

LIB_SRCS += tif_strip.c

LIB_SRCS += tif_thunder.c

LIB_SRCS += tif_tile.c

LIB_SRCS += tif_version.c

LIB_SRCS += tif_warning.c

LIB_SRCS += tif_write.c

LIB_SRCS += tif_zip.c

LIB_SRCS += tif_win32.c

       

include $(TOP)/configure/RULES

#----------------------------------------

#  ADD RULES AFTER THIS LINE

#########################################

 

So this avoids the problem you were talking about.  The library is now part of the EPICS build system, nothing gets lost when you do “make clean uninstall”.  It installs the required header files into myApp/include/os/WIN32 where they will not get in the way of files of the same name on other EPICS archs.

 

What I can’t answer, but hopefully Janet Anderson can, is how you tell EPICS to look for a library in a location other than the standard Linux search path for include files and libraries.

 

Mark