Chapter 2: Developing Custom Applications

Example UNIX makefile

On the UNIX platforms, you can use supported compilers and make utilities of your choice. The concept of building the custom application library is the same; compile your code and link against e-Biz Impact libraries. The following is a sample makefile for HP that contains commands to build both a client and server type library:

# Compiler informationCPP_COMPILER = /opt/aCC/bin/aCCC_COMPILER = /usr/bin/cc# Compiling optionsDAPORTABLE = +DAportable +Z -OHPOPTION = -D__HPACC_USING_MULTIPLIES_IN_FUNCTIONALDOPTIONS = -D_REENTRANT -DNDEBUG -DRWSTD_MULTI_THREAD=1

     -D_THREAD_SAFE=1 -DINFR_THREAD_POSIX -DINFR_COMPILER_ACC=0x0315# Compile path informationHEADERPATH = -I/home/ims53/includeIMPACTPATH = $(HEADERPATH)/IMPACTINFRPATH = $(HEADERPATH)/INFRCFGPATH = $(HEADERPATH)/CFGNDOPATH = $(HEADERPATH)/NDO# Linking optionsLINKOPTION = -b -Wl,+s# Linking path informationLIBPATH = -L/home/ims53/binacquisition.sl: CustomAcquirePlugin.o: CustomAcquirePluginImpl.o acquisition.o        $(CPP_COMPILER) $(LINKOPTION) $(LIBPATH) $(DAPORTABLE) $(HPOPTION) $(HEADERPATH) $(IMPACTPATH) $(INFRPATH) $(NDOPATH) $(CFGPATH) $(DOPTIONS) acquisition.o CustomAcquirePlugin.o CustomAcquirePluginImpl.o -linfr21 -lims53bus -lims53utils -o acquisition.sldelivery.sl: CustomServerPlugin.o CustomServerPluginImpl.o delivery.o        $(CPP_COMPILER) $(LINKOPTION) $(LIBPATH) $(DAPORTABLE) $(HPOPTION) $(HEADERPATH) $(IMPACTPATH) $(INFRPATH) $(NDOPATH) $(CFGPATH) $(DOPTIONS)

delivery.o CustomServerPlugin.o CustomServerPluginImpl.o -linfr21 -lims53bus -lims53utils -o delivery.slCustomAcquirePlugin.o:  CustomAcquirePlugin.cpp CustomAcquirePlugin.h CustomAcquirePluginDef.h        $(CPP_COMPILER) $(DAPORTABLE) $(HPOPTION) $(HEADERPATH) $(IMPACTPATH) $(INFRPATH) $(NDOPATH) $(CFGPATH) $(DOPTIONS) -c CustomAcquirePlugin.cpp -o

CustomAcquirePlugin.o

CustomServerPlugin.o:   CustomServerPlugin.cpp CustomServerPlugin.h        $(CPP_COMPILER) $(DAPORTABLE) $(HPOPTION) $(HEADERPATH) $(IMPACTPATH) $(INFRPATH) $(NDOPATH) $(CFGPATH) $(DOPTIONS) -c CustomServerPlugin.cpp -o CustomServerPlugin.oCustomAcquirePluginImpl.o:      CustomAcquirePluginImpl.cpp CustomAcquirePluginImpl.h CustomAcquirePluginDef.h        $(CPP_COMPILER) $(DAPORTABLE) $(HPOPTION) $(HEADERPATH) $(IMPACTPATH) $(INFRPATH) $(NDOPATH) $(CFGPATH) $(DOPTIONS) -c CustomAcquirePluginImpl.cpp 
-o CustomAcquirePluginImpl.oCustomServerPluginImpl.o:       CustomServerPluginImpl.cpp CustomServerPluginImpl.h        $(CPP_COMPILER) $(DAPORTABLE) $(HPOPTION) $(HEADERPATH) $(IMPACTPATH) $(INFRPATH) $(NDOPATH) $(CFGPATH) $(DOPTIONS) -c CustomServerPluginImpl.cpp 
-o CustomServerPluginImpl.oacquisition.o:  acquisition.c        $(C_COMPILER) $(DAPORTABLE) $(HPOPTION) $(HEADERPATH) $(IMPACTPATH) $(INFRPATH) $(NDOPATH) $(CFGPATH) $(DOPTIONS) -c acquisition.c -o acquisition.odelivery.o:     delivery.c        $(C_COMPILER) $(DAPORTABLE) $(HPOPTION) $(HEADERPATH) $(IMPACTPATH) $(INFRPATH) $(NDOPATH) $(CFGPATH) $(DOPTIONS) -c delivery.c -o delivery.oclean:        rm -f core *.o *~

In the preceding makefile, path information for e-Biz Impact libraries, header files, and link options are specified at the beginning. You can specify different path information, compile, and link options for the build process to suit your needs; for example, you might include your own code in the application and link against your own libraries.

View this book as PDF