Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
> Suggestions so far are to put this information in the source
> filename. For instance teaching Automake to install
> `pt_BR-foo.1' or `foo.1.pt_BR' as `pt_BR/man1/foo.1',
> with the rewriting issues Josef pointed out.
`foo.1.pt_BR' breaks Emacs
Waldemar Rosenbach <[EMAIL PROTECTED]> writes:
> But what is the best way to deal with the platform depend stuff in the
> interface?
A platform independent interface!
--
Ralph
>>> "Eric" == Eric Siegerman <[EMAIL PROTECTED]> writes:
[...]
Eric> *please* consider making it an extra subdirectory
Eric> level instead of a filename component, as in Josef's
Eric> "xx/man1/foo.1".
Yep, however the question isn't really about _where_ the files
will be installed, but about
On Mon, Sep 02, 2002 at 07:55:53PM +0200, Alexandre Duret-Lutz wrote:
> >>> "Josef" == Josef Spillner <[EMAIL PROTECTED]> writes:
>
> Josef> What is the right way to install man pages with
> Josef> languages different from C (default)?
> Josef> [...]
> Josef> Back in December 2000, someone co
config.h is platform depend, so it shouldn't be installed by make install.
But what is the best way to deal with the platform depend stuff in the
interface?
For example:
#ifdef HAVE_HASHMAP
# include
typedef std::hash_map myTableType;
#else
# include
typedef std::map myTableType;
Autoconf 2.54 is about to be released. This version includes many
bugs fixes, and several new features, listed below. Special attention
was paid to Automake 1.7-Autoconf 2.54 interaction.
Akim, Alexandres, Jim, Paul, and Tom
You may download Autoconf 2.53c immediately from:
ftp://
