#4500: Build systems (how to handle)
--------------------+-------------------------------------
Reporter: vexed | Owner:
Type: task | Status: new
Priority: normal | Milestone: unspecified
Component: other | Version: unspecified
Keywords: | Blocked By:
Blocking: | Operating System: All/Non-Specific
--------------------+-------------------------------------
While our primary build system is automake/autohell for both main
development & the CC, I am thinking we need to change some things around.
While we do have other builds systems, like Xcode, and solution files for
VS2013 (which also works in VS2015), and now, apparently we have a
dedicated VS2015 version.
I am not sure I agree with adding lots of extra stuff into Warzone proper
under the 3rdparty directory using git submodules.
That was only meant for things that aren't available for all distros yet,
not for building new dev packages for things the CC don't need.
Right now, it seems only the newer VS2015 build system uses some added
libraries via git submodules.
I think we should rethink how we handle this, I think a better alternative
is to either separate out the other build systems, and stick them in their
own projects, or switch to CMAKE or SCONS (or ...) to make everyone happy.
I can see the Xcode adding more git submodules, and this gets to be
really, really messy.
This is just a ticket to comment on, how we should proceed.
So, if you have input, feel free to speak up. :)
--
Ticket URL: <http://developer.wz2100.net/ticket/4500>
Warzone 2100 Trac <http://developer.wz2100.net/>
The Warzone 2100 Project
------------------------------------------------------------------------------
_______________________________________________
Warzone2100-project mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/warzone2100-project
