Experimental Physics and
| |||||||||||||||
|
On Wed, 17 Apr 2019 at 20:47, Konrad, Martin <[email protected]> wrote: Hi Ralph, I am using gtest/gmock for a C++ Device Support module. At this point I am using the Debian binary packages for gtest and a manual Windows install on my two main development platforms, but I also have a locally compiled version (on Debian) that I can switch to. The main (and probably only) thing that the tap-listener achieves: I can call "make runtests" and the gtest parts work exactly the same as the epicsUnitTest parts, so that CI scripts, CI web display of test results etc. "just work", even for a mixture of epicsUnitTest and gtest. I would include the two small files needed to do that into EPICS Base, so that any module that uses/compiles against EPICS Base could use any combination of epicsUnitTest and gtest. (It would eventually also allow C++ parts of EPICS Base (like the PVA modules) to use gtest, but that's another story not currently in my scope.) For the time being, I would leave provision of gtest to the platform or CI job. Setting GTEST_HOME in CONFIG_SITE.local should be all an EPICS module needs to do. A CI job would build gtest (preferably cached) and provide the GTEST_HOME setting. Cheers, ~Ralph
| ||||||||||||||
ANJ, 18 Apr 2019 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |