From: White, G. <gr...@sl...> - 2012-03-28 10:22:13
|
Hi Dirk, did you add yourself to the epics-pvdata-devel list? If not, follow the Subscription instructions on the page https://sourceforge.net/apps/trac/sourceforge/wiki/Mailing%20lists Can I add you as an Observer of EPICS V4? Please send me your sourceforge id, and I'll add you as a member of the team, with observer status [1] Cheers Greg [1] http://epics-pvdata.sourceforge.net/charter.html#part On 28 Mar 2012, at 11:13, Matej Sekoranja wrote: > Thanks Dirk for trying to compile on VxWorks. I agree on renaming version.h/cpp. > Can you provide a patch so that I can integrate it. You can even > commit it to the repository, if you wish. > > > Thanks again, > Matej > > On Tue, Mar 27, 2012 at 5:47 PM, Dirk Zimoch <dir...@ps...> wrote: >> Dirk Zimoch wrote: >>> I found a fix: >>> >>> In CONFIG_SITE I find this in order to install into the pv subdirectory: >>> >>> INSTALL_INCLUDE = $(INSTALL_LOCATION)/include/pv >>> USR_INCLUDES += -I $(INSTALL_LOCATION)/include >>> >>> Unfortunately, the EPICS build system adds this location and all source >>> locations to the include search path. Here we neither need it nor want >>> it. I added the following two lines to CONFIG_SITE to clean the search >>> path: >>> >>> INSTALL_INCLUDES = >>> SRC_INCLUDES = >> >> ... and change #include <logger.h> to #include <pv/logger.h> everywhere. >> >>> >>> Dirk >>> >>> >>> Dirk Zimoch wrote: >>>> Hi >>>> >>>> pvData contains a header file called "version.h". This conflicts with >>>> the vxWorks header file "version.h" and makes compilation on vxWorks >>>> impossible. >>>> >>>> Even though the include file is installed to a pv subrirectory and >>>> only used with a "qualified name" like #include <pv/version.h>, It is >>>> found by vxWorks which looks for its own <version.h>. >>>> >>>> Why that? The EPICS make rules set up the search path like this: >>>> >>>> -I. -I../O.Common -I. -I.. -I../../pvAccessApp//ca >>>> -I../../pvAccessApp//utils -I../../pvAccessApp//client >>>> -I../../pvAccessApp//factory -I../../pvAccessApp//remote >>>> -I../../pvAccessApp//remoteClient -I../../pvAccessApp//server >>>> -I../../include/pv/os/vxWorks -I../../include/pv >>>> -I/afs/psi.ch/user/z/zimoch/cvs/EPICSv4-1.0-BETA/pvDataCPP/include >>>> -I/usr/local/epics/base/include/os/vxWorks >>>> -I/usr/local/epics/base/include -I ../../include >>>> -I/afs/psi.ch/group/8431/dirk/boost_1_49_0 >>>> -I/afs/psi.ch/project/vxworks/WindRiverGPP3.7/vxworks-6.7/target/h >>>> -I/afs/psi.ch/project/vxworks/WindRiverGPP3.7/vxworks-6.7/target/h/wrn/coreip >>>> >>>> >>>> First of all, the vxWorks include paths come last. >>>> Second, ../../include/pv is used, not only ../../include. >>>> This makes the qualified #include <pv/version.h> pointless. >>>> >>>> >>>> So either the EPICS make rules have to be modified not to set up the >>>> include path like this, or we need qualified file names like pvVersion.h >>>> >>>> Dirk >>>> >>> >>> >> >> >> ------------------------------------------------------------------------------ >> This SF email is sponsosred by: >> Try Windows Azure free for 90 days Click Here >> http://p.sf.net/sfu/sfd2d-msazure > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure |