[Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Mark de Wever
At the beginning of the 1.5 development cycle some developers wanted to get rid of autotools and it was decided to test with scons and cmake. Scons and cmake were added to trunk and since that time we have three build systems. The 1.7 development cycle looms at the horizon and the build system

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Eric S. Raymond
Mark de Wever ko...@xs4all.nl: I like to propose to drop autotools support and make scons and cmake the default build systems for 1.7. I'm certainly in favor of dropping autotools. I started the push to get rid of it, and it's no less of a nasty hairball than it was then. I haven't noticed

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Nils Kneuper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Guillaume Melquiond schrieb: On 2009/2/22, Mark de Wever wrote: Which leaves the question who still uses autotools and want to keep using that. I still use it; and I intend to keep using it as long as it works. 1. If it was broken, I

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Mark de Wever
On Sun, Feb 22, 2009 at 08:44:55AM -0500, Eric S. Raymond wrote: Mark de Wever ko...@xs4all.nl: I haven't noticed anyone liking cmake except Ivanovic and you. I hear quite some people dislike scons, who still use it... but that's why I drew the conclusion we won't reach an agreement about

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Mark de Wever
On Sun, Feb 22, 2009 at 06:06:37PM +0300, Sergey Popov wrote: На Sun, 22 Feb 2009 15:47:54 +0100 Mark de Wever ko...@xs4all.nl записано: You can glob all headers and add them to your project, but then you can't control to which subproject they belong. I see no easy way for a tool to

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Guillaume Melquiond
On 2009/2/22, Nils Kneuper wrote: The point is *really* simple: To generate a tarball that works for endusers when using autotools, autotools have to be used to generate it, or there is no plan configure file. No way to just use svn export and be done. Why not? Both cmake and scons require

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Mark de Wever
On Sun, Feb 22, 2009 at 03:14:23PM +0100, Guillaume Melquiond wrote: On 2009/2/22, Mark de Wever wrote: Which leaves the question who still uses autotools and want to keep using that. I still use it; and I intend to keep using it as long as it works. 1. If it was broken, I wouldn't

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Sergey Popov
На Sun, 22 Feb 2009 16:49:08 +0100 Mark de Wever ko...@xs4all.nl записано: You don't want a header included by two subprojects to show up twice (at least I wouldn't want that). Then to which project it should go? :) ___ Wesnoth-dev mailing list

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Mark de Wever
On Sun, Feb 22, 2009 at 07:08:32PM +0300, Sergey Popov wrote: На Sun, 22 Feb 2009 16:49:08 +0100 Mark de Wever ko...@xs4all.nl записано: You don't want a header included by two subprojects to show up twice (at least I wouldn't want that). Then to which project it should go? :) Easy

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Nils Kneuper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Guillaume Melquiond schrieb: On 2009/2/22, Nils Kneuper wrote: The point is *really* simple: To generate a tarball that works for endusers when using autotools, autotools have to be used to generate it, or there is no plan configure file. No

[Wesnoth-dev] possible security problems (eg with current python implementation)

2009-02-22 Thread Nils Kneuper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everybody! dfranke lately spotted several possible security issues in our code. That is of those findings, so far two led us to the conclusion serious enough for official reporting so that Rhonda submitted two new CVE for us: 1) CVE-2009-0366 was

Re: [Wesnoth-dev] possible security problems (eg with current python implementation)

2009-02-22 Thread allefant
On Sun, Feb 22, 2009 at 6:08 PM, Nils Kneuper crazy-ivano...@gmx.net wrote: Long mail cut short: What about 1.6? Should we got for 1) or for 2)? Or does anyone of you have even a better idea what we should do? Personally I vote for 2) since PythonAI is not really used and it would reduce

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Guillaume Melquiond
On 2009/2/22, Nils Kneuper wrote: The basic reason is that when autotools are used, users *expect* to find configure files and do not expect to run ./autogen.sh first. When using scons or cmake to build users know that they have to install it separately. Even more important (to me) is that

Re: [Wesnoth-dev] possible security problems (eg with current python implementation)

2009-02-22 Thread jeremy rosen
just a quick note : the bugs reported are private i.e only registered devs can view them, however, this mailing list is not. So please avoid discussing the vulnerabilites themselves here this might be obvious to everybody, but it's better repeated OK, I would also vote for 2, my main argument

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Alexander Neundorf
Hi, On Sunday 22 February 2009, Sergey Popov wrote: На Sun, 22 Feb 2009 14:28:03 +0100 Mark de Wever ko...@xs4all.nl записано: Cmake also supports to make project files for MSVC and CodeBlocks, it would be nice to get some feedback on how good these project files are. If we can make

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Alexander Neundorf
On Sunday 22 February 2009, Mark de Wever wrote: ... * Cmake; mog implemented the cmake build system and went MIA afterwards, which means cmake has no real maintainer. It seems to work mostly but is in need of some love. At FOSDEM there were at least two Wesnoth developers who really

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Sergey Popov
На Sun, 22 Feb 2009 19:57:29 +0100 Alexander Neundorf neund...@kde.org wrote: There shouldn't be useless targets. Which ones do you consider useless ? none of which are Debug or Release, It is still based on Makefiles, and the makefiles are one-configuration only. To get release and

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Mark de Wever
On Sun, Feb 22, 2009 at 07:59:55PM +0100, Alexander Neundorf wrote: On Sunday 22 February 2009, Mark de Wever wrote: ... * Cmake; mog implemented the cmake build system and went MIA afterwards, which means cmake has no real maintainer. It seems to work mostly but is in need of some

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Alexander Neundorf
On Sunday 22 February 2009, Sergey Popov wrote: На Sun, 22 Feb 2009 19:57:29 +0100 Alexander Neundorf neund...@kde.org wrote: There shouldn't be useless targets. Which ones do you consider useless ? none of which are Debug or Release, It is still based on Makefiles, and the

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Sergey Popov
На Sun, 22 Feb 2009 22:52:55 +0100 Alexander Neundorf neund...@kde.org wrote: Thanks for your contructive attitude. What is wrong with using a DSL for a very specific purpose ? I don't think that cmake's language is a DSL, at least compared to make. It's just yet another scripting language,

Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons)

2009-02-22 Thread Daniel Franke
Mark de Wever ko...@xs4all.nl writes: Looking at irc it seems we have lovers and haters or both cmake and scons. It seems some developers are in love with the Makefile based build system (autotools/cmake) and other dislike the whole Makefile based system. (Scons doesn't use Makefiles) So in

Re: [Wesnoth-dev] possible security problems (eg with current python implementation)

2009-02-22 Thread Daniel Franke
Nils Kneuper crazy-ivano...@gmx.net writes: 1) Limit PythonAI usage to stuff only available in the data/ main tree, nothing from userdata. 2) Completely deactivate Python for the 1.6 series. This means not even allowing it to be compiled into the binary via the build systems. It was I