On 11/5/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> * NightStrike wrote on Mon, Nov 05, 2007 at 06:01:26AM CET:
> >
> > lib32dir=$(prefix)/lib32
> > lib64dir=$(prefix)/lib64
> >
> > lib32_LIBRARIES = libuuid.a
> > libuuid_a_SOURCES = lib32/uuid.c
> >
> > lib64_LIBRARIES = libuuid.a
> > libuuid
* NightStrike wrote on Mon, Nov 05, 2007 at 06:01:26AM CET:
>
> lib32dir=$(prefix)/lib32
> lib64dir=$(prefix)/lib64
>
> lib32_LIBRARIES = libuuid.a
> libuuid_a_SOURCES = lib32/uuid.c
>
> lib64_LIBRARIES = libuuid.a
> libuuid_a_SOURCES = lib64/uuid.c
Not sure why you don't write
lib32_LIBRARIE
On 11/4/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
>
> Please learn about `subdir-objects', that helps. It's indexed in the
> manual.
Ok, that has actually helped in multiple ways. I am now using that
option, and it's good. That gets me past one hurdle. Now I am left
with the following:
F
* NightStrike wrote on Sun, Nov 04, 2007 at 08:14:32PM CET:
> On 11/4/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> > info Automake 'Libtool Issues'
[...]
> > info Automake 'Conditional Sources'
> I was following those sections almost. I missed that part about
> having to add in a bogus _C
On Nov 4, 2007, at 7:59 PM, Jason Curl wrote:
I've implemented the following:
-8< Makefile.am
man_MANS = \
libmofo.3 \
convertstring.3
On 11/4/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> > > On Nov 4, 2007, at 7:47 PM, NightStrike wrote:
> > > > AM_CONDITIONAL(WITH32, test x$WITH_32 != x)
> > > >
> > > > And I put this in Makefile.am:
> > > >
> > > > if WITH32
> > > > crtdir=$(prefix)/lib32
> > > > uuidsrc = lib32/uuid.c
> > On Nov 4, 2007, at 7:47 PM, NightStrike wrote:
> > > AM_CONDITIONAL(WITH32, test x$WITH_32 != x)
> > >
> > > And I put this in Makefile.am:
> > >
> > > if WITH32
> > > crtdir=$(prefix)/lib32
> > > uuidsrc = lib32/uuid.c
> > > else
> > > crtdir=$(prefix)/$(target)/lib
> > > uuidsrc = lib
On 11/4/07, Benoit SIGOURE <[EMAIL PROTECTED]> wrote:
> On Nov 4, 2007, at 7:47 PM, NightStrike wrote:
>
> > I am trying to figure out how to do conditional sources. Basically,
> > here is the setup:
> >
> > lib/uuid.c
> > lib32/uuid.c
> >
> > If I pass --with-m32 to configure, I want to use the s
Benoit SIGOURE wrote:
On Nov 4, 2007, at 2:40 PM, Jason Curl wrote:
So let's assume I've got a command on my build environment
groff -Tascii -mandoc myman.3 | col -b > mycat.3
I might even extend this to generate HTML instead of ASCII.
Later I'd be implementing a Perl script to convert what
On 11/4/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> * NightStrike wrote on Sun, Nov 04, 2007 at 07:28:27PM CET:
> > There are variables like AM_CFLAGS and AM_LDFLAGS. Is there an
> > AM_DLLTOOLFLAGS variable that can be used to pass common parameters to
> > dlltool?
>
> No, but also Automake
On Nov 4, 2007, at 7:47 PM, NightStrike wrote:
I am trying to figure out how to do conditional sources. Basically,
here is the setup:
lib/uuid.c
lib32/uuid.c
If I pass --with-m32 to configure, I want to use the second source.
If I don't, then I want to use the first. I put this in configure.
On 11/4/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> * NightStrike wrote on Sun, Nov 04, 2007 at 07:26:51PM CET:
> > Is there a difference between using AC_PROG_LIBTOOL and
> > AM_PROG_LIBTOOL? I see both defined in the manual as synonymous, but
> > I may not be looking at the right place in t
I am trying to figure out how to do conditional sources. Basically,
here is the setup:
lib/uuid.c
lib32/uuid.c
If I pass --with-m32 to configure, I want to use the second source.
If I don't, then I want to use the first. I put this in configure.ac:
AC_ARG_WITH(m32,
[ --with-m32 Compile lib3
* NightStrike wrote on Sun, Nov 04, 2007 at 07:28:27PM CET:
> There are variables like AM_CFLAGS and AM_LDFLAGS. Is there an
> AM_DLLTOOLFLAGS variable that can be used to pass common parameters to
> dlltool?
No, but also Automake provides no automatic rule generation in which
DLLTOOL is ever use
* NightStrike wrote on Sun, Nov 04, 2007 at 07:26:51PM CET:
> Is there a difference between using AC_PROG_LIBTOOL and
> AM_PROG_LIBTOOL? I see both defined in the manual as synonymous, but
> I may not be looking at the right place in the manual.
AM_PROG_LIBTOOL is an older name for AC_PROG_LIBTOO
There are variables like AM_CFLAGS and AM_LDFLAGS. Is there an
AM_DLLTOOLFLAGS variable that can be used to pass common parameters to
dlltool?
Is there a difference between using AC_PROG_LIBTOOL and
AM_PROG_LIBTOOL? I see both defined in the manual as synonymous, but
I may not be looking at the right place in the manual.
On Nov 4, 2007, at 2:40 PM, Jason Curl wrote:
So let's assume I've got a command on my build environment
groff -Tascii -mandoc myman.3 | col -b > mycat.3
I might even extend this to generate HTML instead of ASCII.
Later I'd be implementing a Perl script to convert what is in code
comments t
Bob Proulx wrote:
Jason Curl wrote:
Continuing with my efforts of making a library designed for Linux a bit
usable for colleagues on Windows I'd like to figure out how to install
"cat" pages, i.e. conversions of "man" pages.
Hmm... Would it make more sense to set up 'man' on ms-windo
19 matches
Mail list logo
