Re: Windows 10 LNK1181 error on xml2.lib

["Hu, Yong via Tech-talk" <tech-talk at aps.anl.gov>]

Historically and ironically, it seems more troublesome to build EPICS stuff on Windows than on Linux. I saw similar errors quite a while ago.

My colleague, Jakub Wlodek, developed scripts to automate the builds of EPICS base, areaDetector, and other support modules on Windows. Try this: https://github.com/huyong1979/windows-epics-config

Cheers,
Yong

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Freddie Akeroyd - STFC UKRI via Tech-talk <tech-talk at aps.anl.gov>
Date: Wednesday, December 6, 2023 at 7:45 AM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: RE: Windows 10 LNK1181 error on xml2.lib

Does your ioc CONFIG_SITE  include $(AREA_DETECTOR)/configure/CONFIG_SITE ?

 

Freddie

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Freddie Akeroyd - STFC UKRI via Tech-talk
Sent: 06 December 2023 12:35
To: tech-talk at aps.anl.gov
Subject: RE: Windows 10 LNK1181 error on xml2.lib

 

Hi,

 

• the “link” command even points to ADSupport/lib/linux-x86_64

 

I assume you mean ADSupport/lib/windows-x64 ?  And Xml2.lib exists in this location?

 

Regards,

 

Freddie

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Ralph Lange via Tech-talk
Sent: 06 December 2023 08:59
To: EPICS Tech Talk <tech-talk at aps.anl.gov>
Subject: Re: Windows 10 LNK1181 error on xml2.lib

 

On Wed, 6 Dec 2023 at 06:40, Abdalla Ahmad via Tech-talk <tech-talk at aps.anl.gov> wrote:

[...], the “link” command even points to ADSupport/lib/linux-x86_64, and the windows PATH variable points to the same location but still I get the same LNK1181 issue.

 

Keep in mind that Windows DLLs are in the "bin" install location, while statically linked libraries and the DLL stub libraries are under "lib". Under Windows, PATH needs to point to the DLLs, i.e. should contain the "bin" location.

 

~Ralph