EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024 
<== Date ==> <== Thread ==>
Subject: Re: make puzzle
From: "Johnson, Andrew N. via Core-talk" <core-talk at aps.anl.gov>
To: Michael Davidsaver <mdavidsaver at gmail.com>
Cc: EPICS core-talk <core-talk at aps.anl.gov>
Date: Mon, 9 Nov 2020 17:50:30 +0000


On Nov 8, 2020, at 12:29 PM, Michael Davidsaver <mdavidsaver at gmail.com> wrote:

On 11/6/20 4:00 PM, Johnson, Andrew N. wrote:
Why might you want to use NO + NO?

I had no idea that you considered this to be a valid combination.
At least I can understand why I was confused.

…

The setting YES+YES is probably less useful (build lib.so files but link binaries statically – it ought to work, but seems fairly pointless).

As it happens, this is the combination I've long used (and recommended) where supported.
Since I consider the two settings mostly orthogonal on *nix, it makes sense to me for
shared libraries to always be built.  Then individual applications are left with the
choice of whether to link support modules statically.

Note that on macOS (Darwin) you can’t link executables statically at all, Apple don’t provide some necessary file(s) such as crt.o for that, so setting STATIC_BUILD=YES always fails. The closest you can get to an application built statically is thus to set SHARED_LIBRARIES=NO which at least pulls all of the EPICS code into the final executables.

(imo, the example of non-PIC assembly is a bit of a reach these days)

Probably true, that was just the first reason that came to mind; there are others for why one might want to avoid building a shared library.

- Andrew

-- 
Complexity comes for free, simplicity you have to work for.

Replies:
Re: make puzzle Ralph Lange via Core-talk
References:
make puzzle Michael Davidsaver via Core-talk
Re: make puzzle Johnson, Andrew N. via Core-talk
Re: make puzzle Michael Davidsaver via Core-talk
Navigate by Date:
Prev: Re: make puzzle Michael Davidsaver via Core-talk
Next: Re: make puzzle Ralph Lange via Core-talk
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: make puzzle Michael Davidsaver via Core-talk
Next: Re: make puzzle Ralph Lange via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024 
ANJ, 09 Nov 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·