[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: stdint generation
From: |
Bruno Haible |
Subject: |
Re: stdint generation |
Date: |
Mon, 15 Oct 2007 22:28:32 +0200 |
User-agent: |
KMail/1.5.4 |
Sam Steingold wrote:
> > gnulib-tool --import --source-base=src/gllib --m4-base=src/glm4 \
> > --aux-dir=src/build-aux --no-changelog \
> > stdint stdbool ...
>
> do I need to do this before each release?
It's a good idea to do it, say, two weeks before a release, and then watch
the bug-gnulib mailing to see whether the files you have imported may be
broken. (It happens that we have broken files in the gnulib repository for
a short time, but it's usually cleaned up within a day or two.) In other
words, do the "gnulib-tool --import" before the release testing, not
between release testing and releasing.
> > This will create a Makefile.am in src/gllib; therefore get familiar with
> > automake, and recurse from src into src/gllib before building src itself.
>
> how will automake play with your makemake?
> I will need to pre-generate woe32 Makefiles, right?
Ah, right, these old msvc/nmake Makefiles. automake does not support them.
Therefore you need to decide: Either drop the support for msvc/nmake (and
rely on mingw and gcc for building the Woe32 port). Or don't use automake,
and translate the gnulib-tool generated Makefile.am manually to a Makefile.in
and Makefile.msvc or to a piece of makemake.
For GNU gettext and GNU libiconv, I got rid of the Makefile.msvc, Makefile.os2,
Makefile.vms, at the same time when I started using gnulib-tool.
> actually, this makes sense for msvc: one has make but not shell.
But on msvc you also don't have 'sed'. So you have to run the 'sed' command
as part of "make dist", and ship pre-built stdint.h, stdbool.h, unistd.h, ...
files for this platform.
Bruno