Automake Support for cyrus-imapd 2.5

Дилян Палаузов dilyan.palauzov at aegee.org
Mon Apr 16 18:35:14 EDT 2012


Hello,

>> With the exception of perl and CUnit, I it works fine and permits
>> building in a directory, different from the source directory.  All
>> dependencies are moved to a single Makefile.am (except CUnit and Perl).
>>    The point with CUnit is, that I did not manage to get it running on my
>> system, so I left it as is.  The Makefile's generated from Makefile.PL
>> do not permit compiling perl files in a directory, different from the
>> source directory.
>
> I wonder if we can change from Makefile.PL to one of the more modern
> Perl build systems...

https://bugzilla.cyrusimap.org/show_bug.cgi?id=3678 it was suggested to 
generate Makefile.PL from Makefile.PL.in at configure time and then 
create Makefile from Makefile.PL at build time, without passing plenty 
of variables.  I uploaded now this concept.

>> "make dist" shall build .tar.bz2 including all files.  However I have
>> copied the dist-target from the old Makefile.in, removed all
>> Makefile.dist files.  The one who make tarballs/snapshots shall consider
>> if it is wiser to use the Automake system to make tarballs, or the
>> system used so far (with git).  So or so, the xversion.h file needs to
>> be generated by git.
>
> So long as it can be done easily, I don't much care.

> Can configure.ac -> ./configure please be made in charge of xversion.h?

The best approach would be, if some hooks (post-checkout) are used at 
checkout, that fill accordingly
   AC_INIT([cyrus-imapd], [2.5], 
[http://bugzilla.cyrusimap.org],,[http://www.cyrusimap.org])
and xversion.h on checkout.

Със здраве
   Дилян


More information about the Cyrus-devel mailing list