Experimental Physics and
Industrial Control System

Andrew Johnson <[email protected]> · Fri, 31 Oct 2014 18:07:38 -0500

Hi Peter,

On 10/31/2014 01:16 PM, Heesterman, Peter J wrote:
> My install process has been to delete my pre-existing 'base' directory,
> copy your download in its place, and then recover my non-downloaded
> files (i.e., principally my VS project files) over the top, from my
> source control server.

That seems perfectly reasonable.

> I have carefully compared - windiff - my install directory with your
> raw download directory.
> 
> Changed files are:
> 
> Due only to the patch you sent me earlier:
> .\src\libcom\flex\makefile
> .\src\libcom\flex\rules

I don't now believe those changes should be necessary, but they won't
cause any harm.

> For the reasons previously discussed:
> .\src\libcom\misc\epicstypes.h

Accepted.

> .\src\std\softioc\base.dbd

The 3.15.0.2 version of base.dbd does include menuGlobal.dbd, so I don't
follow what you've done there but it wouldn't explain the build issue at
all anyway.

> I have customised Win32.bat - I believe correctly - to suit my build environment and paths,  and have retained my version.
> It has not changed from my builds prior to this download.
> 
>>> Make -v
> I note that it says
> 	This program built for i386-pc-mingw32
> 
> I'm using GnuWin32, not mingw, for my build.

That's probably the same as mine then, which is the GnuWin32 version:

> D:\epics\mirror-3.15>make -v
> GNU Make 3.81
> Copyright (C) 2006  Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.
> There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
> PARTICULAR PURPOSE.
> 
> This program built for i386-pc-mingw32

> Does this make sense?

It doesn't sound like you're doing anything wrong, but I don't
understand why your build behaves so differently to everybody else's.
You shouldn't have to copy files into the .\include directory by hand,
that's a standard functionality that the build system performs.

The only thing I can think is that it might be something to do with your
VS project files or build, although that seems unlikely. I'm a bit
stumped at this point.

Could you run 'make distclean' at the top of the Base tree and then log
the output from 'make' and send me the result to look at. The distclean
will delete all of the build and install files, including anything that
you've copied by hand, so I can see exactly what you get from a clean build.

- Andrew

-- 
People everywhere confuse what they read in newspapers with news.
-- A. J. Liebling

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System