Experimental Physics and
Industrial Control System

Mark Rivers <[email protected]> · Thu, 24 Sep 2015 18:58:17 +0000

These problems were with which version of Visual Studio and which version of EPICS base?

Mark

-----Original Message-----
From: Kevin Peterson [mailto:[email protected]] 
Sent: Thursday, September 24, 2015 1:55 PM
To: Mark Rivers; J. Lewis Muir; Mark S. Engbretson; [email protected]
Subject: Re: Unable to build support modules on Windows, with base 3.15.2

I believe I get the following link error when building seq-2-2-1
(included with synApps_5_8) and seq-2-2-2 when building for win32-x86:

link -nologo  /LTCG /incremental:no /opt:ref /release
-out:snc.exe        lexer.obj snl.obj main.obj node.obj var_types.obj
analysis.obj gen_code
.obj gen_ss_code.obj gen_tables.obj sym_table.obj builtin.obj
type_check.obj     ..\\..\\..\\lib\\win32-x86\\seq.lib
..\\..\\..\\lib\\win32-x86\\pv.lib  D:\\ep
ics\\base-3.14.12.5\\lib\\win32-x86\\ca.lib
D:\\epics\\base-3.14.12.5\\lib\\win32-x86\\Com.lib
var_types.obj : error LNK2001: unresolved external symbol
__imp__prim_type_name
gen_tables.obj : error LNK2001: unresolved external symbol
__imp__prim_type_tag_name
snc.exe : fatal error LNK1120: 2 unresolved externals
make[4]: *** [snc.exe] Error 1120
make[4]: Leaving directory
`D:/epics/synApps_5_8/support/seq-2-2-2/src/snc/O.win32-x86'
make[3]: *** [install.win32-x86] Error 2
make[3]: Leaving directory `D:/epics/synApps_5_8/support/seq-2-2-2/src/snc'
make[2]: *** [snc.install] Error 2
make[2]: Leaving directory `D:/epics/synApps_5_8/support/seq-2-2-2/src'
make[1]: *** [src.install] Error 2
make[1]: Leaving directory `D:/epics/synApps_5_8/support/seq-2-2-2'
make: *** [D:/epics/synApps_5_8/support/seq-2-2-2.install] Error 2

alive-1-0 doesn't build for Windows unless you add the following libs to
its src/Makefile.  The alive svn repo contains a similar fix, but it
assumes ws2_64 is available, which it wasn't on my system.

+alive_SYS_LIBS_WIN32 += ws2_32
+alive_SYS_LIBS_WIN32 += Advapi32

The version of ADCore included in synApps_5_8 fails to link
out-of-the-box for win32-x86:

link /nologo /subsystem:windows /dll /LTCG /incremental:no /opt:ref
/release        /implib:NeXus.lib /out:NeXus.dll          napi.obj
napi5.obj napiu.obj nxdat
aset.obj nxio.obj nxstack.obj nxxml.obj stptok.obj
D:\\epics\\synApps_5_8\\support\\areaDetector-R2-0\\ADBinaries-R2-2\\lib\\win32-x86\\libhdf5.lib
 D:\\ep
ics\\synApps_5_8\\support\\areaDetector-R2-0\\ADBinaries-R2-2\\lib\\win32-x86\\libszip.lib
 D:\\epics\\synApps_5_8\\support\\areaDetector-R2-0\\ADBinaries-R2-2\
\lib\\win32-x86\\libzlib.lib
LIBCMT.lib(timeset.obj) : error LNK2005: ___daylight already defined in
MSVCRT.lib(MSVCR100.dll)
LIBCMT.lib(timeset.obj) : error LNK2005: ___timezone already defined in
MSVCRT.lib(MSVCR100.dll)
LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of other
libs; use /NODEFAULTLIB:library
NeXus.dll : fatal error LNK1169: one or more multiply defined symbols found
make[5]: *** [NeXus.dll] Error 1169
make[5]: Leaving directory
`D:/epics/synApps_5_8/support/areaDetector-R2-0/ADCore-R2-2/ADApp/nexusSrc/O.win32-x86'
make[4]: *** [install.win32-x86] Error 2
make[4]: Leaving directory
`D:/epics/synApps_5_8/support/areaDetector-R2-0/ADCore-R2-2/ADApp/nexusSrc'
make[3]: *** [nexusSrc.install] Error 2
make[3]: Leaving directory
`D:/epics/synApps_5_8/support/areaDetector-R2-0/ADCore-R2-2/ADApp'
make[2]: *** [ADApp.install] Error 2
make[2]: Leaving directory
`D:/epics/synApps_5_8/support/areaDetector-R2-0/ADCore-R2-2'
make[1]: ***
[D:/epics/synApps_5_8/support/areaDetector-R2-0/ADCore-R2-2.install] Error 2
make[1]: Leaving directory `D:/epics/synApps_5_8/support/areaDetector-R2-0'
make: *** [D:/epics/synApps_5_8/support/areaDetector-R2-0.install] Error 2

Those are the few errors that I copied into a text file before I gave up
trying to build synApps_5_8 for its areaDetector support.

Kevin

On 9/24/15 1:35 PM, Mark Rivers wrote:
>> Many of the problems seem to be caused by Makefiles that unconditionally build
>> code that doesn't work on Windows, and therefore are a problem for all
>> versions of Visual Studio.
> 
> I build all of synApps, including the sequencer on Windows, and don't have those problems.  What modules specifically did you have trouble with?
> 
> Mark
> 
> 
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Peterson
> Sent: Thursday, September 24, 2015 1:33 PM
> To: J. Lewis Muir; Mark S. Engbretson; [email protected]
> Subject: Re: Unable to build support modules on Windows, with base 3.15.2
> 
> On 9/24/15 10:45 AM, J. Lewis Muir wrote:
>>> If you succeed at building base, you'll encounter more problems when
>>> you try to build other EPICS modules.
>>
>> Which problems are these?  If a certain compiler does not build
>> EPICS software correctly, it would be good to note that compiler as
>> unsupported on Andrew's page.
> 
> I have not had a chance to document all of the problems I encountered
> trying to build synApps_5_8 with Visual Studio Community 2015.  Many of
> the problems seem to be caused by Makefiles that unconditionally build
> code that doesn't work on Windows, and therefore are a problem for all
> versions of Visual Studio.
> 
> The sequencer is one module that is difficult to build on Windows, but
> those problems have already been discussed here.
> 
> Kevin
> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System