octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: finally actually using gnulib


From: John W. Eaton
Subject: Re: finally actually using gnulib
Date: Sat, 14 Nov 2009 14:28:45 -0500

On 14-Nov-2009, Benjamin Lindner wrote:

| Hmm, apparently git is not available for windows, only for cygwin.
| At least git's homepage does not have any info on native windows
| ports, nor does a quick google-search.
| 
| Yes there is http://code.google.com/p/msysgit/
| but what you get there is something very closely mingled with a
| own separate msys installation, so you cannot use it from within an
| msys session for building octave. It's also not clear if this port
| is even usable with a standard msys installation from mingw.org.
| According to the changelogs, they patched or extended msys so no,
| obviously it will not work with a standard msys installation.
| 
| Not what I was looking for.
| 
| Glancing at your diff I seems one now also requires rsync. Am I right?
| Guess what - also not available for windows, except cygwin.
| 
| Aren't there releases or snapshots of gnulib available?
| I must check out from the development sources?
| 
| How is getting gnulib for an octave build done?
| Can I do it once separately, store it locally somewhere on my machine?

Yes, you can do this.  The bootstrap script accepts the argument

 --gnulib-srcdir=DIRNAME  Specify the local directory where gnulib
                          sources reside.  Use this if you already
                          have gnulib sources on your machine, and
                          do not want to waste your bandwidth downloading
                          them again.

You can also use this argument to speed up subsequent autogen.sh runs
even if you use git for the initial checkout.

The --copy argument may also help if you can't create symbolic links.

The autogen.sh script doesn't process any arguments itself and instead
passes all arguments to the bootstrap script.  So you should be able
to

  * Get a copy of gnulib on your system.  If you download them with
    git (say with Cygwin), but don't want to or can't use git when you
    run autogen.sh, then remove or rename the .git directory in the
    gnulib source tree.  Otherwise, it looks like the bootstrip script
    will try to use git to update the gnulib sources.

  * Run ./autogen.sh --copy --gnulib-srcdir=/location/of/gnulib

The advantage of using git is that you immediately and automatically
get updates from the gnulib source tree as soon as they are
available.

If you absolutely cannot find a way to use git to download the gnulib
sources, then I suppose we could make a tar file available somewhere
and keep it up to date.

As far as I can tell, rsync is only used for downloading gettext
translation (.po) files, and since we are not (yet) using gettext, I
guess the rsync problem can be deferred for a while longer.

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]