Experimental Physics and Industrial Control System

Hi Mark,

On 12/04/2017 05:38 PM, Mark Rivers wrote:
> I am having trouble building for EPICS_HOST_ARCH=windows-x64-static on a
> Linux file server.  Previously when building EPICS base there were no
> RELEASE or RELEASE.local files to worry about.  This is not the case
> with 7.0.1. 

Actually your issue isn't really that you're building for Windows on a
Linux file-system (the file-system itself isn't the problem), as that
you want to share a single installation of Base between both Linux and
Windows, and we obviously haven't thought about that configuration
properly because it just doesn't work at the moment.

> The file modules/RELEASE.local contains
> 
> EPICS_BASE = /usr/local/epics/base-7.0.1
> 
> which is where I put it on Linux.

Right. This file gets created the first time that GNUmake descends into
the modules directory. If you had built this on Windows first the
contents would reflect the path there instead.

> I tried creating a new file in that directory,
> RELEASE.local.windows-x64-static.  It contains:
> 
> EPICS_BASE = H:/epics/base-7.0.1
> 
> which is the correct path for Windows.  However, that file does not seem
> to get included

Right, it won't, we currently only include a single RELEASE.local file.

> It would be very nice if all I need to do is to create
> modules/RELEASE.local.$(EPICS_HOST_ARCH)  to define EPICS_BASE and
> everything else just built out of the box.  As it is now I need to edit
> configure/RELEASE in 9 directories.
> 
> Perhaps I am missing something?

No, we just didn't think of this — you're the only person I know who
uses this particular configuration.

Then on 12/04/2017 at 05:55 PM, Mark Rivers wrote:

> Never mind, I came up with a simple solution.  I edited
> modules/RELEASE.local to pull in architecture-specific version from that
> location:
> 
> EPICS_BASE = /usr/local/epics/base-7.0.1
> -include $(TOP)/../RELEASE.local.$(EPICS_HOST_ARCH)
> 
> That works fine, and involves editing just that file and adding the new
> RELEASE.local.$(EPICS_HOST_ARCH) files.
> 
> This second line might be added when modules/RELEASE.local is created. 
> It would save others having to reinvent what I just did.

I will probably just generate RELEASE.local.<host-arch> and modify our
submodule configure/RELEASE files to pull that in instead. This way the
solution is automatic and you shouldn't have to do anything for it to
work (you will get a RELEASE.local.* file for each host-architecture you
build for).

Do you ever need an architecture-specific CONFIG_SITE.local file to match?

Thanks for the report and suggested fix.

- Andrew


-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon

Replies:

RE: Problem building base-7.0.1 with Windows on a Linux file system Mark Rivers

References:

Problem building base-7.0.1 with Windows on a Linux file system Mark Rivers

Navigate by Date:

Prev: RE: Problem building base-7.0.1 with Windows on a Linux file system Mark Rivers

Next: RE: Problem building base-7.0.1 with Windows on a Linux file system Mark Rivers

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017>  2018  2019  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: RE: Problem building base-7.0.1 with Windows on a Linux file system Mark Rivers

Next: RE: Problem building base-7.0.1 with Windows on a Linux file system Mark Rivers

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017>  2018  2019  2020  2021  2022  2023  2024