Library paths are hard coded at link time. For that reason, on some platforms
Libtool relinks binaries during install. Because prefix et. al. can be set
at make time, stripping has to be done on the installed binary because it may
not exist until then.
So strip before install would not be
So strip before install would not be portable.
Drat.
Thank you all for the ideas and explanations.
- Rhys
I'm tempted to believe the DESTDIR feature could be useful here with
something like
make install-strip DESTDIR=`pwd`/tmp
and then copy files under 'tmp' into your final destination.
This idea should cover what I need to do for a development/testing
situation. Thank you.
- Rhys
On Tue, May 7, 2013 at 5:12 PM, Rhys Ulerich rhys.uler...@gmail.com wrote:
I gather that 'make install-strip' installs and then strips binaries.
Is there some variant that reverses the order? If not, any
recommendations for how to write one in an Automake-compliant manner?
My unstripped
On 05/08/2013 02:12 AM, Rhys Ulerich wrote:
I gather that 'make install-strip' installs and then strips binaries.
Is there some variant that reverses the order? If not, any
recommendations for how to write one in an Automake-compliant manner?
Hi Rhys,
I'm tempted to believe the DESTDIR
I gather that 'make install-strip' installs and then strips binaries.
Is there some variant that reverses the order? If not, any
recommendations for how to write one in an Automake-compliant manner?
My unstripped binaries are absurdly large and my installation
directory is NFS-mounted. So I get
