diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..cde41de --- /dev/null +++ b/.gitignore @@ -0,0 +1,13 @@ +QtC- +bin/ +lib/ +doc/ +include/ +db/ +dbd/ +documentation/html +documentation/*.tag +envPaths +configure/*.local +!configure/ExampleRELEASE.local +**/O.* diff --git a/Doxyfile b/Doxyfile index c853574..c4702f8 100644 --- a/Doxyfile +++ b/Doxyfile @@ -908,7 +908,8 @@ HTML_STYLESHEET = # files. In the HTML_STYLESHEET file, use the file name only. Also note that # the files will be copied as-is; there are no commands or markers available. -HTML_EXTRA_FILES = +HTML_EXTRA_FILES = documentation/pvAccessOverview.html +HTML_EXTRA_FILES = documentation/pvaOverview.html # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. # Doxygen will adjust the colors in the style sheet and background images diff --git a/Makefile b/Makefile index c005d8f..f5e3f4a 100644 --- a/Makefile +++ b/Makefile @@ -2,16 +2,25 @@ TOP = . include $(TOP)/configure/CONFIG +DIRS := $(DIRS) $(filter-out $(DIRS), configure) +DIRS := $(DIRS) $(filter-out $(DIRS), src) +DIRS := $(DIRS) $(filter-out $(DIRS), pvaSrc) +DIRS := $(DIRS) $(filter-out $(DIRS), pvtoolsSrc) +DIRS := $(DIRS) $(filter-out $(DIRS), testApp) +DIRS := $(DIRS) $(filter-out $(DIRS), pvaExample) +DIRS := $(DIRS) $(filter-out $(DIRS), pvaTest) -DIRS := configure +EMBEDDED_TOPS := $(EMBEDDED_TOPS) $(filter-out $(EMBEDDED_TOPS), pvaExample) +EMBEDDED_TOPS := $(EMBEDDED_TOPS) $(filter-out $(EMBEDDED_TOPS), pvaTest) -DIRS += src -src_DEPEND_DIRS = configure +define DIR_template + $(1)_DEPEND_DIRS = configure +endef +$(foreach dir, $(filter-out configure,$(DIRS)),$(eval $(call DIR_template,$(dir)))) -DIRS += pvtoolsSrc -pvtoolsSrc_DEPEND_DIRS = src - -DIRS += testApp -testApp_DEPEND_DIRS = src +define EMB_template + $(1)_DEPEND_DIRS = src pvaSrc +endef +$(foreach dir, $(EMBEDDED_TOPS),$(eval $(call EMB_template,$(dir)))) include $(TOP)/configure/RULES_TOP diff --git a/configure/ExampleRELEASE.local b/configure/ExampleRELEASE.local new file mode 100644 index 0000000..403d72f --- /dev/null +++ b/configure/ExampleRELEASE.local @@ -0,0 +1,7 @@ +EPICS_BASE=/home/install/epics/base + +EPICS4_DIR=/home/epicsv4 +PVCOMMON=${EPICS4_DIR}/pvCommonCPP +PVDATA=${EPICS4_DIR}/pvDataCPP + + diff --git a/documentation/pvAccessCPP.html b/documentation/pvAccessCPP.html index 1a66012..78b5a3c 100644 --- a/documentation/pvAccessCPP.html +++ b/documentation/pvAccessCPP.html @@ -38,7 +38,7 @@
pvAccessCPP is the C++ implementation of pvAccess, which is one of a related -set of products: +
pvAccessCPP is the C++ implementation of pvAccess, +which is network support for transporting structured data as defined by pvData. +
++pvAccess is one of a related +set of products: relatedDocumentsV4.html
+This is the 09-July-2011 version of the C++ implementation of pvAccess. The -code is a complete implementation of pvAccess as currently defined. This -overview is NOT written.
+This is the 05-June-2011 version of the C++ implementation of pvAccess. The +code is a complete implementation of pvAccess.
This product is available via an open source -license
+This document describes the pvAccess Application Program Interface (API). +The reader is assumed to have a basic understanding of EPICS V4 as described in:
+ +EPICS V4 Developer's Guide + +The pvAccess API is callback based and uses Status to report problem to the +client, which means that it can be complex to use. +If your primary interest is client access then, instead of reading this document, +read:
+ +EPICS pva + +If your primary interest is implementing pvAccess services then, +before reading this documement read:
+ +pvDatabaseCPP + -This overview for pvAccessCPP. Doxygen documentation is available at doxygenDoc
-THIS IS NOT WRITTEN For now please consult pvAccessJava.html. -In addition look at the Doxygen documentation for this project.
+ + +This product is available via an +open source license + +
++A user overview is available via +pvAccessOverview.html + +
++Doxygen documentation is available at +doxygenDoc + + +
Matej decide what else should go in this document
pvAccessCPP is the C++ implementation of pvAccess, +which is network support for transporting structured data as defined by pvData. +
++pvAccess is one of a related +set of products: +relatedDocumentsV4.html +
+ + + +This is the 05-June-2011 version of the C++ implementation of pvAccess. The +code is a complete implementation of pvAccess.
+ +This document describes the pvAccess Application Program Interface (API). +The reader is assumed to have a basic understanding of EPICS V4 as described in:
+ +EPICS V4 Developer's Guide + +The pvAccess API is callback based and uses Status to report problem to the +client, which means that it can be complex to use. +If your primary interest is client access then, instead of reading this document, +read:
+ +EPICS pva + +If your primary interest is implementing pvAccess services then, +before reading this documement read:
+ +pvDatabaseCPP + + + + + +This product is available via an +open source license + +
++A user overview is available via +pvAccessOverview.html + +
++Doxygen documentation is available at +doxygenDoc + + +
Matej decide what else should go in this document
+ +diff --git a/documentation/pvAccessCPP_20150505.html b/documentation/pvAccessCPP_20150505.html new file mode 100644 index 0000000..78b5a3c --- /dev/null +++ b/documentation/pvAccessCPP_20150505.html @@ -0,0 +1,136 @@ + + + +
+ +
+ + + + + + + +
+