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 p
> 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
Hi,
I would like to compile both a program and a library from the same
source file. This is what I have inside src/Makefile.am:
lib_LTLIBRARIES = libex.la
libex_la_SOURCES = src/ex.c
include_HEADERS = src/ex.h
AM_CPPFLAGS += -DSTANDALONE
bin_PROGRAMS = ex
ex_SOURCES = src/ex.c src/ex.h
I would
On 2013-05-13 14:49 +0200, Cojocaru Alexandru wrote:
> Hi,
> I would like to compile both a program and a library from the same
> source file. This is what I have inside src/Makefile.am:
>
> lib_LTLIBRARIES = libex.la
> libex_la_SOURCES = src/ex.c
> include_HEADERS = src/ex.h
>
> AM_CPPFLAGS += -
Given all the rationales given by Russ and Micheal, I think we should
drop the idea of having "smart dependencies" for the moment being (I
suggested that because, in my ignorance of Java, I thought they would
be easy to implement).
Instead, let's start implementing something *correct*, in line wit
On Mon, 13 May 2013 13:40:37 -0400
Nick Bowler wrote:
> On 2013-05-13 14:49 +0200, Cojocaru Alexandru wrote:
> > Hi,
> > I would like to compile both a program and a library from the same
> > source file. This is what I have inside src/Makefile.am:
> >
> > lib_LTLIBRARIES = libex.la
> > libex_la
