Experimental Physics and
Industrial Control System

"Heesterman, Peter J" <[email protected]> · Wed, 27 May 2015 14:35:47 +0000

Hi Mark,

I am using 4-26, which I believe to be the most recent release.

Cheers,

Peter.

-----Original Message-----
From: Mark Rivers [mailto:[email protected]] 
Sent: 27 May 2015 15:32
To: Heesterman, Peter J; EPICS Tech Talk
Subject: RE: Motor R6-9 build issues on Windows

What version of asyn are you using?  I did some cleanup of asyn not too long ago to fix such problems.

Mark

________________________________________
From: Heesterman, Peter J [[email protected]]
Sent: Wednesday, May 27, 2015 9:02 AM
To: Mark Rivers; EPICS Tech Talk
Subject: RE: Motor R6-9 build issues on Windows

Hi Mark,

Actually, the issues that need to be addressed first, are in Asyn.

Where the header files of a module (such as Asyn, in this case) import from another module (such as Com, in this case), but also in turn export to other modules (such as Motor, in this case), it is pretty essential to manipulate the epicsExportSharedSymbol define so that the importing headers each import, and the exporting headers each export.

See my attached header files from the Asyn module, which I believe are doing so correctly.

You'll see that epicsExportSharedSymbol is turned off before #including headers from the EPICS base.
Then the value of the define is cached, and restored, before being applied the definitions of (this) header.

This is quite well expressed in the comments of shareLib.h.

There are also some build issues in the Motor project that need to be looked at.

Cheers,

Peter.

-----Original Message-----
From: Mark Rivers [mailto:[email protected]]
Sent: 27 May 2015 12:05
To: Heesterman, Peter J; EPICS Tech Talk
Subject: RE: Motor R6-9 build issues on Windows

Hi Peter,

I fixed the problem with phytronAxisMotor back in March and committed to SVN.

I fixed many problems with NewportSrc on May 6 to get it to build on Cygwin, which is also much more sensitive to the correct name decorations than the Visual Studio release compiler.  I committed those fixes to SVN as well.  I have not tried building the win32-x86-debug arch, but my fixes for Cygwin may well have fixed those problems.

Can you try checking out the SVN trunk from /https://subversion.xray.aps.anl.gov/synApps/motor/trunk/  and see if there are still problems?

Mark

________________________________
From: [email protected] [[email protected]] on behalf of Heesterman, Peter J [[email protected]]
Sent: Wednesday, May 27, 2015 5:52 AM
To: EPICS Tech Talk
Subject: Motor R6-9 build issues on Windows

Hi,

I would like to highlight some build issues, on Windows, with the R6-9 release of the Motor project.

I am building with the following library versions:

a.       Base 3.15.1

b.      Seq 2.1.15

c.       Ipac 2-10

d.      Asyn 4-26

Trivial issue: phytronAxisMotor.cpp #includes unistd.h – which is not a header file under Windows.
Fix: The file isn’t required, as far as I can see, and can be removed.

Non-trivial issue: A release-x86 build completes normally, but  a debug-x86 build fails with numerous DLL linker warnings and errors (see attached).
I’m not sure I understand why a debug build is so much more sensitive to these problems, than is a release build.

I would be able to address many of the build issues.

Thanks,

Peter.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System