Experimental Physics and
Industrial Control System

Dirk Zimoch <[email protected]> · Wed, 30 Jul 2014 11:24:19 +0200

Amit,

From your original mail, I thought that it was the Windows build

because I found the error directly after a call to 'cl', the Windows

compiler that uses WIN32 include path and very much looks like a Windows

build.

cl /nologo /EHsc /GR -c               /nologo /D__STDC__=0 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE   /Ox /GL   /W3 /w44355       /MT -DEPICS_DLL_NO /TP   -I. -I..\\O.Common -I. -I..\\..\\..\\src\\libCom\\osi\\os\\WIN32 -I..\\..\\..\\src\\libCom\\osi\\os\\default -I.. -I..\\..\\..\\src\\libCom\\bucketLib -I..\\..\\..\\src\\libCom\\ring -I..\\..\\..\\src\\libCom\\calc -I..\\..\\..\\src\\libCom\\cvtFast -I..\\..\\..\\src\\libCom\\cppStd -I..\\..\\..\\src\\libCom\\cxxTemplates -I..\\..\\..\\src\\libCom\\dbmf -I..\\..\\..\\src\\libCom\\ellLib -I..\\..\\..\\src\\libCom\\env -I..\\..\\..\\src\\libCom\\error -I..\\..\\..\\src\\libCom\\fdmgr -I..\\..\\..\\src\\libCom\\freeList -I..\\..\\..\\src\\libCom\\gpHash -I..\\..\\..\\src\\libCom\\iocsh -I..\\..\\..\\src\\libCom\\logClient -I..\\..\\..\\src\\libCom\\macLib -I..\\..\\..\\src\\libCom\\misc -I..\\..\\..\\src\\libCom\\osi -I..\\..\\..\\src\\libCom\\taskwd -I..\\..\\..\\src\\libCom\\timer -I..\\..\\..\\src\\libCom\\t

sDefs -IC
:\EPICS\base-3-14-12-4\\include\\os\\WIN32 -IC:\EPICS\base-3-14-12-4\\include        ..\\..\\..\\src\\libCom\\ring\\epicsRingPointer.cpp

epicsRingPointer.cpp

..\..\..\src\libCom\ring\epicsRingPointer.h(93) : error C2664: 'delete' : cannot convert parameter 1 from 'void *volatile * ' to 'void *'

        Conversion loses qualifiers

        ..\..\..\src\libCom\ring\epicsRingPointer.cpp(82) : while compiling class-template member function '__thiscall epicsRingPointer<void>::~epicsRingPointer<void>(void)'

make[3]: Leaving directory `C:/EPICS/base-3-14-12-4/src/libCom/O.win32-x86'

Do you call make with the -j option for parallel builds? In that case

the output may be confusing and it can be hard to set error messages and

commands into relation.

To make things clearer try first to build for the Windows host only and

after that for vxWorks.

If compiling for Windows alone works it is probably a vxWorks compiler

problem.

Concerning the error popup: This is probably a vxWorks cross tools

thing, too. WindRiver is more and more annoying with each new version

and calling the cross tools from make instead of their own environment

is more and more complicated. I think this tool want to check if you

have the proper vxWorks licenses installed. It seems you have to set a

PATH to the lmapi.dll in a config file. I guess all previous attempts to

compile vxWorks 6.9 have been made from Linux, not from Windows. So

setups for Windows may be missing in the config files.

On 30.07.2014 09:08, Amit Chauhan wrote:

Dear Mark,

This is further to our trials of compiling EPICS for 'VxWorks 6.9'

We ran the 'make' from Visual Studio (2010) Command Prompt.

I am attaching following with this mail:

(1) CONFIG_SITE.Common.vxWorksCommon  : This is the only file we have
modified.

(2) make_output.txt : output of the make process (with error message
appended at the bottom )

(3) errMsg.jpg : This is a pop-up message we encountered 42 times  towards
the end of 'make' . We had to press 'OK' everytime to proceed.

During this trial no changes were made related to the ringPointer.

We would just like to add that when we are buidling EPICS base 3.14.12.4
with Visual Studio 2010 for 'Windows' as target, we are not encountering any
errors.

It is just that when we select 'vxWorks' as target the problems arise.

Regards,

Amit Chauhan
RRCAT, Indore

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System