Re: stdint generation

[Sam Steingold]

Bruno Haible wrote:
> Sam Steingold wrote:
> > gnulib/gnulib/m4/stdint offers a multi-line sed rule for generating 
> > stdint.h from stdint_.h,
> > why do I need to maintain the sed command by hand?
> > why can't this be done by config.status?
>
> Two answers:
>
> Regarding the integration in GNU clisp: Since 2004, when gnulib took stdint_.h
> from clisp, gnulib has evolved a bit. Nowadays nearly all users of gnulib use
> gnulib-tool to assemble the pieces from various modules into their source
> code hierarchy. The old "merge diffs by hand" approach become too burdensome,
> even for die-hards like Paul and me. Therefore what we recommend now is to
> use gnulib-tool. In the case of clisp it can be like this:
>
>   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?

> 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?

> Creating files is most conveniently done
> in a Makefile, not in config.status. (Because config.status is not invoked
> when doing "make clean", "make dist" or similar, and because expressing file
> names in config.status is harder, since config.status is usually in a different
> directory than the files being built.)

actually, this makes sense for msvc: one has make but not shell.

thanks for your reply.
Sam.