rsions of automake
autoconf so that the hard copy of the one on my system will work on
their's?
What is the official solution to this problem?
Thank You.
--
Paul Elliott 1(512)837-1096
[EMAIL PROTECTED]PMB 181, 11900 Metric Blvd Suite J
http://ww
contents of the ../other/src/
directory
so I can not create any Autotools control files there or any object files there.
To me, that directory is read only.
Is there a way to do this conveniently in automake? An implicit rule perhaps?
Thank You.
--
Paul Elliott 1
(astrosrc)/swetest.c
>
> swetest_LDADD = \
>
> libswe.la
After making this change I get a lot of messages of the form:
linker input file unused because linking not done
--sample error message.
> CC libswe_la-swecl.lo
>
> gcc: ../astrodienst/src: linker inpu
autotools files caused it,
and how to supress it. Can anyone help?
On Wednesday, July 20, 2011 01:34:11 AM Paul Elliott wrote:
> On Saturday, June 25, 2011 03:47:56 PM you wrote:
> > Hi Paul,
> >
> > you may try:
> >
> > DIR = $(top_srcdir)/../other/src
>
On Wednesday, July 20, 2011 01:34:11 AM Paul Elliott wrote:
> On Saturday, June 25, 2011 03:47:56 PM you wrote:
> > Hi Paul,
> >
> > you may try:
> >
> > DIR = $(top_srcdir)/../other/src
> >
> > to refer to that directory.
>
> I have moved al
Makefile.am to create documentation.
> .pdf.doc:
> unoconv --listener &
#some times first unoconv does not work. not repeatable.
> unoconv --stdout -f pdf $< > $@ ||{sleep2 ;unoconv --stdout -f pdf
> $< > $@ }
>
> .html.doc:
> unoconv --listener &
> unoconv -
Here is an extract from my Makefile.am
> %.pdf : %.doc
>
> unoconv --listener &
> sleep 4
> unoconv --stdout -f pdf $< > $@ || sleep 2 ;unoconv --stdout -f pdf
> $<
>> $@
>
> %.html : %.doc
>
> unoconv --listener &
> sleep 4
> unoconv --stdout -
egal concept in the concept of a Makefile.am? You would probably have
to insure that you were in the same shell as the one that started the
listener.
What is the official, recommended way of handling unoconv listeners in a
automake file?
Thank You.
--
Paul Elliott
ments as the default port: 2002.
>
> Finally, unless you're using a new enough 'unoconv', the '&&' chaining
> won't actually short-circuit the invocations of the 'unoconv -f ...'
> invocations. This is due to an error propagation bug in unconv
#x27;t be able to get your program into debian:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts
--
Paul Elliott 1(512)837-1096
pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com/pme/
og_SOURCES?
Is there a canonical way to do this?
--
Paul Elliott 1(512)837-1096
pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117
t find the answer.
--
Paul Elliott 1(512)837-1096
[EMAIL PROTECTED]PMB 181, 11900 Metric Blvd Suite J
http://www.io.com/~pelliott/pme/ Austin TX 78758-3117
pgpVkvrTdJiYr.pgp
Description: PGP signature
Excuse me if this is a faq but I can not easily find the asnwer.
I have a Makefile.am that creates and installs a man page myprog.1
It says
man1_MANS = myprog.1
The source is myprog.1. How do I make it create and install a compressed
man page version myprog.1.gz?
Thank You.
--
Paul
ving them changes the interface that the library gives to the rest of
> the world and should not be undertaken lightly.
How do I create a Makefile.am for a shared library so that make install will
not install the .la file but will install the .so?
--
Paul Elliott
On Monday, March 21, 2011 12:51:11 pm Nick Bowler wrote:
> On 2011-03-21 10:52 -0500, Paul Elliott wrote:
> > According to the Fedora Packaging:Guidelines
> > http://fedoraproject.org/wiki/Packaging/Guidelines
>
> > .la files should not be installed:
> This is a task fo
On Monday, March 21, 2011 02:13:24 pm Paul Elliott wrote:
> It seems dumb to have make install install a file only to have the distro
> remove it, is there anyway to tell make install not to install it?
I guess I should not do it that way because somebody might want to use the
auto*tools
author's source or change or rename any files.
How do I tell auto*tools to treat this file as a .h file? That is, do not try
to
compile this file itself, and do include it in the files to be distributed.
Thank You
--
Paul Elliott 1(512)837-1096
On Tuesday, March 22, 2011 01:54:33 am Paul Elliott wrote:
> I have a c library that currently uses an old style Makefile that I want to
> convert to auto*tools.
>
> One .c file is used as a .h file. That is, it is included by another .c
> file and it should not be itself compiled.
specify
distribution directories for documentation.
Thank You.
--
Paul Elliott 1(512)837-1096
pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117
signature.asc
Description: This is
19 matches
Mail list logo
