Re: Still can not successful compile/run epicsV4CPP from github

["Heinz P. Junkes" <junkes@fhi-berlin.mpg.de>]

Ok, can now build my RTEMS-V4 IOC.

I had forgotten to include pvAccessCA - lib

This works now :

IOCCryvisil_LIBS += pvaSrv pvDatabase pvAccess pvAccessCA nt pvData

Sorry for bothering, Heinz


On 08/23/2017 02:52 PM, Andrew Johnson wrote:
> On 08/23/2017 03:33 PM, Heinz P. Junkes wrote:
> > works with
> >
> > make
> > make runtests
> >
> > ends up with see at the end of this mail.
> >
> > Is this related to the build system? I am still fighting with similar
> > issues when I try to compile the stuff for RTEMS.
> >
> > Heinz
> >
> >
> > output make runtests in exampleCPP:
> The master branch of exampleCPP doesn't seem to have been completely
> updated yet since the recent major updates; the APS Jenkins builds of
> exampleCPP are still failing for windows-x64-static and rtems builds so
> your experience is probably to be expected right now — see the red rows in
>    https://jenkins.aps.anl.gov/view/EPICS%20V4/
>
> In general you shouldn't be too concerned about the exampleCPP module at
> this stage, it tends to trail the other modules anyway since it's there
> to show how to use the APIs and features of the V4 stuff, not to provide
> additional functionality itself.
>
> - Andrew
>
> PS to all especially Michael: APS Jenkins should be accessible again,
> please let me know if you see any more problems with it.