Re: Removal of the autotools-based build system
Dimitri <[email protected]>
| Newsgroups | gmane.comp.db.mysql.devel,gmane.comp.db.mysql.packagers |
|---|---|
| Message-ID | <[email protected]> |
BTW, CMake is not always installed by default on all systems, so it'll be fine to print a clear error message on configure/make that CMake is missing and stop.. - Currently it's not a case, and you may meet many errors on compiling before to discover there is no CMake on your system.. Rgds, -Dimitri On 11/5/10, Davi Arnaut <[email protected]> wrote: > On 11/5/10 6:55 PM, Kristian Nielsen wrote: >>> > There is a ./configure emulation already, but its not perfect and I'm >>> > inclined to remove it. Package related scripts should definitely be >>> > made aware of cmake in order to fully exploit it. Also, otherwise, we >>> > would need to keep updating the emulation script. Another point is >>> > that with cmake there was also a change of install layout, so >>> > intervention will be necessary in any case. >>> > >>> > What do you think? Keep or remove? >> I'm not sure. Personally I don't see much need to keep the emulation layer >> around. As you say, other changes will be needed anyway, so better just >> spend >> the effort on the native CMake. >> >> I think the main usefulness of the emulation layer is having done it, to >> check >> that everyting in the old system has a counterpart in the new (to >> reasonable >> degree ...), and showing how to map between them. >> >> It might be useful to convert the emulation layer into a documentation >> file >> describing for each old autoconf option how (and if) the same effect is >> obtained with CMake. > > Agree. I've added your remark to the task. > > Regards, > > Davi > > -- > MySQL Internals Mailing List > For list archives: http://lists.mysql.com/internals > To unsubscribe: > http://lists.mysql.com/[email protected] > > -- MySQL Internals Mailing List For list archives: http://lists.mysql.com/internals To unsubscribe: http://lists.mysql.com/[email protected]