On Wed, 2006-10-04 at 21:33 -0700, Andre Stechert wrote:
> On Oct 4, 2006, at 8:55 PM, Ryan McDougall wrote:
>
> > However the problem remains that Im at a bit of a loss how to ship a
> > shared .SO library easily. If I build on my machine (or a set of
> > supported build
(including
> embedding references to your prefix in the appropriate places) and then
> at the last minute, it will take the files it was going to install
> and "destdir" them
> at /tmp/staging. Then you can simply tar/gz the files at /tmp/
> staging and ship
> those t
Hello,
First of all, Im only looking for serious answers, and I dont want to
start any flamewars, so Ill start out by saying that quite likely the
only problem here is my lack of knowledge of autotools, and the other
the issues involved. Please correct me at any point you disagree with.
After s
Hello,
I am porting a proprietary (yes I know, but it pays the bills) windows
application to linux using autotools. So far I have gotten automake to
do what I want up until the install/build stage.
I wish to provide our end-users with a tarball that includes a
dynamically linkable library, and t
On Thu, 2006-09-28 at 13:06 +0200, Ralf Wildenhues wrote:
> Hello Ryan,
>
> * Ryan McDougall wrote on Thu, Sep 28, 2006 at 11:30:32AM CEST:
> > On Thu, 2006-09-28 at 18:23 +0900, Ryan McDougall wrote:
> > >
> > > How can I either
> > > 1. Express
On Thu, 2006-09-28 at 18:23 +0900, Ryan McDougall wrote:
> On Fri, 2006-09-22 at 04:34 +0200, Ralf Wildenhues wrote:
> > * Ryan McDougall wrote on Fri, Sep 22, 2006 at 02:54:21AM CEST:
> > > On Thu, 2006-09-21 at 13:32 +0200, Ralf Wildenhues wrote:
> > > > * Ryan
On Fri, 2006-09-22 at 04:34 +0200, Ralf Wildenhues wrote:
> * Ryan McDougall wrote on Fri, Sep 22, 2006 at 02:54:21AM CEST:
> > On Thu, 2006-09-21 at 13:32 +0200, Ralf Wildenhues wrote:
> > > * Ryan McDougall wrote on Thu, Sep 21, 2006 at 11:40:37AM CEST:
> > > 2)
On Fri, 2006-09-22 at 04:34 +0200, Ralf Wildenhues wrote:
> > >
> > > You should keep in mind that the convenience archives will end up in
> > > total (i.e., all their symbols, not just needed ones) in the resulting
> > > module.
> >
> > This is a good point, thank you. Do you have any more info
On Thu, 2006-09-21 at 13:32 +0200, Ralf Wildenhues wrote:
>
> The second approach will enable you to
> make libA.la
>
> in the toplevel directory. Otherwise, there is nothing that prevents
> you from adding your own targets a la
> A:
> cd src/A && $(MAKE) $(AM_MAKEFLAGS) libA.la
>
On Thu, 2006-09-21 at 13:32 +0200, Ralf Wildenhues wrote:
> Hello Ryan,
>
> * Ryan McDougall wrote on Thu, Sep 21, 2006 at 11:40:37AM CEST:
> >
> > Im porting a large code-base from windows to linux, and attempting to
> > use autotools to do so. The code in SVN is
Hello,
I apologize if this has been answered somewhere. Ive read the book and
searched the archives.
My situation is this:
Im porting a large code-base from windows to linux, and attempting to
use autotools to do so. The code in SVN is essentially one big tree of
somewhat related modules -- le
11 matches
Mail list logo
