X-Git-Url: http://www.git.cypherpunks.ru/?a=blobdiff_plain;f=doc%2Fbuilding.texi;h=fee272e1bde547d554f2148452cd544f1e80f0c9;hb=c12d6ee76fc66031756602976831f97624fc28f2;hp=30376dce8a449b9fa0b65e3155d91772b9c2ffe9;hpb=9fbc648a2821d9a6e0de6352d9adb40f98f1723a;p=nncp.git diff --git a/doc/building.texi b/doc/building.texi index 30376dc..fee272e 100644 --- a/doc/building.texi +++ b/doc/building.texi @@ -17,21 +17,33 @@ $ gpg --verify nncp-@value{VERSION}.tar.xz.sig nncp-@value{VERSION}.tar.xz $ xz --decompress --stdout nncp-@value{VERSION}.tar.xz | tar xf - $ cd nncp-@value{VERSION} $ redo all -# look for bin/nncp-* binaries (and possibly hjson-cli one) @end example +After that you should get various @command{bin/nncp-*} binaries and +@command{bin/hjson-cli} command (only for your convenience, not +necessary installation). For example, documentation for +@command{nncp-bundle} command can be get with +@command{info doc/nncp.info -n nncp-bundle}. + It uses @url{http://cr.yp.to/redo.html, redo} build system for that -examples. You can use either dozen of various implementations, or at -least minimalistic POSIX shell @command{contrib/do} (just replace +examples. You can use one of its various implementations, or at least +minimalistic POSIX shell @command{contrib/do} (just replace @command{redo} with @command{contrib/do} in the example above) included in tarball. Following ones are tested to work with: @url{http://www.goredo.cypherpunks.ru/, goredo} (NNCP's author creation), @url{https://redo.readthedocs.io/, apenwarr/redo} (@code{contrib/do} is -from that project), @url{https://github.com/leahneukirchen/redo-c, redo-c}. +from that project), @url{https://github.com/leahneukirchen/redo-c, redo-c}, +@url{https://github.com/gotroyb127/baredo, baredo}. -There is @command{install} target respecting @env{DESTDIR}. It will +There is @command{install} target respecting @env{$DESTDIR}. It will install binaries and info-documentation: @example # PREFIX=/usr/local redo install @end example + +NNCP depends on @code{github.com/fsnotify/fsnotify} library, that is +solely relies on OS-specific mechanisms. There is possibility that you +have either broken or unsupported ones. You can still build NNCP with +@code{-tags nofsnotify} build option, to skip @code{fsnotify} library +usage at all.