[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Cron-bug] libcron static libs

From: Ryan M. Golbeck
Subject: Re: [Cron-bug] libcron static libs
Date: Wed, 30 Jan 2002 12:14:24 -0500
User-agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.1 (i386-debian-linux-gnu)

Jeff Bailey <address@hidden> writes:

> You've asked for different, and slightly confusing things, so I've
> done what I think is the Right Thing.  I'll change it if you want
> something different.

It was early. :)

> I think the static libraries are already installed - The default for
>libtool is to create them and install them.  I don't see this as a
>bad thing.

No, it's a good thing for sure.

> I have fiddled with src/test/ such that the libcron
>library is linked in - I don't quite understand the static/dynamic
>concern, so I just let automake do what it thinks is the Right Thing.
>I have set the program to be built, not installed, and called when
>you run `make check'.

Awesome, that's exactly what I wanted.

> I also fixed two srcdir != builddir nits.

This was just a temporary hack because the actual installation of
libcron isn't setup properly anyway.  libcron.h and other to-be 
installed headers are no NOINST.

> Lastly, I changed the name of your build file.  In the case where
>the source file to BINARY is just BINARY.c, you don't need to specify
>a sources line.  Given that your testsuites will probably be one
>sourcefile per test, I have altered the binary name to allow this to
>happen.  It makes for an easier to read

Cool.  Didn't know this.

> Hope this helps.  Gotta run to work.  I will probably be on email
>sporadically throughout the day.

Perfect, exactly what I wanted, thanks.


Ryan Golbeck <address@hidden>
Computer Science, University Of Waterloo
GPG: 1024D/78916B84 -- 1B1B 2A87 3F00 A7FB 40F3  526D 36CF BA44 7891 6B84

reply via email to

[Prev in Thread] Current Thread [Next in Thread]