On Sun, Jul 1, 2012, at 12:07 AM, Дилян Палаузов wrote:
Hello,
is it possible to define in doc/install-compile.html the minimum
versions of the tools, a developer needs in order to re-generate all
source files need for the compilation of cyrus-imapd?
The needed tools are autoconf,
On Mon, Jul 2, 2012, at 11:15 AM, Bron Gondwana wrote:
And the makefiles we ship with release tarballs better bloody work
everywhere or the panda will be sad.
Good point. Once we get the dist: target sorted out in the new build
system, we should set up a Jenkins job which builds a dist
Hello,
Speaking of which...Dilyan, what is the status of the dist: target?
The only problem I am aware of is that make distclean does not clean
the files generated by perl, and make cannot create /xversion.h, as
there is no v2.5 tag and the distance v2.5..HEAD cannot be measured (and
Hello,
to my opinion there are two things:
1. What do people cloning from git need in order to build the package
2. What tools versions do developers need, when they change a e.g. lex file.
About people cloning from git, if we want to make their life easier, we
can version-manage the
Can we stick to flex instead of lex? In any case, flex 2.5.35 supports
%option reentrant noyyget_FUNCTIO and noyyset_FUNCTION, which options are
not supported by lex on ci.cyrusimap.org . noyyget_ and noyyset_ permit to
exclude some unneeded functions from sieve/addr-lex.c and
Hello,
is it possible to define in doc/install-compile.html the minimum
versions of the tools, a developer needs in order to re-generate all
source files need for the compilation of cyrus-imapd?
The needed tools are autoconf, automake, bison, (f)lex, gperf, libtool
and possibly compile_et .
