AW: Linking dynamic AND static with the same lt-libraries

Dear all, thanks for yours replies, I've just forgotten, that I have to repeat some libs in the list. This was one of the reasons to use automake/libtool instead of our old linkerscripts. Kind Regards Thomas Roesner -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTE

Re: release and test targets

Ralf Corsepius wrote: > Baurzhan Ismagulov wrote: > > release: > > $(MAKE) CFLAGS=-O2 prefix=/usr sysconfdir=/etc localstatedir=/var > > You are miss interpreting automake's tasks. Packaging is not of > automake's business. The above technique really has nothing to do with automake and jus

Re: Using Automake with shell scripts

You don't have PROGRAMS, you have SCRIPTS. H

Re: Linking dynamic AND static with the same lt-libraries

On Mon, Dec 12, 2005 at 09:28:54AM +0100, Roesner Thomas wrote: > "does not work" means, that the linker can find all refered symbols in > the dynamic scenario, but that there are some unresolved symbols in > the static scenario. As Ralf said, it's most probably the library order, I'd also suggest

Using Automake with shell scripts

I am maintaining a project, GNU Songanizer, which basically consists of a shell script. I am using autoconf/automake to generate the Makefiles by the help of the configure script to maintain GNU compatibility. Hence during installation there is nothing to be compiled. Only the script (ie. bin/songa

Re: what happens to EXTRA_DIST during distcheck?

> "Ed" == Ed Hartnett <[EMAIL PROTECTED]> writes: Ed> In my top level makefile I have an EXTRA_DIST: Ed> # These files get added to the distribution. Ed> EXTRA_DIST = README COPYRIGHT RELEASE_NOTES Ed> But looking at the _build directory created during make distcheck, I Ed> do not see any of

what happens to EXTRA_DIST during distcheck?

Howdy all! In my top level makefile I have an EXTRA_DIST: # These files get added to the distribution. EXTRA_DIST = README COPYRIGHT RELEASE_NOTES But looking at the _build directory created during make distcheck, I do not see any of these files: /shecky/netcdf-3/netcdf-4.0-alpha11/_build:

Re: AM_CFLAGS not included in translation unit compilation

Hi Mike, * Mike Mattie wrote on Sat, Dec 10, 2005 at 07:24:35PM CET: > On 12/8/05, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > * Mike Mattie wrote on Fri, Dec 09, 2005 at 12:59:33AM CET: > > > > > > In a recent project I noticed that the individual compilation units do > > > not include AM_CFLA

Re: Tools under Windows

--- Howard Chu <[EMAIL PROTECTED]> wrote: > Keith MARSHALL wrote: > > BRM wrote: > >> I´ve been playing around with it a bit today, > mostly > >> MSYS, and have thus far only had one issue with > it - > >> cl won´t compile the program because of bad > parameters > >> being passed to it (since MSYS

Re: Linking dynamic AND static with the same lt-libraries

* Roesner Thomas wrote on Mon, Dec 12, 2005 at 09:28:54AM CET: > > > On Fri, Dec 09, 2005 at 04:25:42PM +0100, Roesner Thomas wrote: > > > The point is, that I want to build all programs with shared libraries, > > > but one with static libraries, wich are based on the same sourcecode > > > than th

Re: Tools under Windows

Keith MARSHALL wrote: BRM wrote: I´ve been playing around with it a bit today, mostly MSYS, and have thus far only had one issue with it - cl won´t compile the program because of bad parameters being passed to it (since MSYS uses // instead of /). (Not sure if that´s an issue for you guys, mingw

Re: Tools under Windows

BRM wrote: > I´ve been playing around with it a bit today, mostly > MSYS, and have thus far only had one issue with it - > cl won´t compile the program because of bad parameters > being passed to it (since MSYS uses // instead of /). > (Not sure if that´s an issue for you guys, mingw-msys, > or the

Re: Tools under Windows

Howard Chu wrote, quoting BRM: >> I´m taking a look at Msys/MingW now. Its worked best >> so far - though a script is failing. I got it to run >> by running the VC build environment (e.g. vcvars.bat) >> and then running the msys environment (msys.bat) to >> enter into the msys shell. >> >> Thanks f

Re: shared library from smaller pieces

Hi Vlad, * Vlad Skvortsov wrote on Fri, Dec 09, 2005 at 11:46:46PM CET: > > Ok, I believe I have to explain more here. My product is deemed to be > self-contained: no dependencies on external shared libraries, nothing. I > build all my [C] applications static. However, recently a need has > ari

Linking dynamic AND static with the same lt-libraries

Dear Baurzhan, "does not work" means, that the linker can find all refered symbols in the dynamic scenario, but that there are some unresolved symbols in the static scenario. Looking in subdir/.libs/mylib.a shows the required symbols in the text area of the library. Kind Regards Thomas Roesn