Changes between Version 17 and Version 18 of BuildAndDeploymentEnvironment


Ignore:
Timestamp:
Jan 15, 2012, 5:03:52 PM (12 years ago)
Author:
Yves
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildAndDeploymentEnvironment

    v17 v18  
    99
    1010
     11----
     12= Overview current design =
    1113
    12 == Overview current design ==
    13 
    14 === update-workspaces.sh / update-workspaces.bat: ===
     14== update-workspaces.sh / update-workspaces.bat: ==
    1515The sh-script on Linux/*nix/OSX runs the compilation of some external dependencies and also premake.
    1616On Windows the batchfile only executes premake because most of the dependencies are precompiled.
    1717
    18 === Premake ===
     18== Premake ==
    1919Premake creates our workspaces (also called solutions or projects) for the different platforms.
    2020Currently we support Makefiles, VisualStudio (2005, 2008, 2010), Xcode3, Codeblocks.
    2121
    22 === Workspaces ===
     22== Workspaces ==
    2323The workspaces are used for building the code on different platform and also for development with different programs (IDE's).
    2424
    25 === Deployment ===
     25== Deployment ==
    2626For (alpha-)releases we make a special deployment for various reasons. The main reason is that we want to make it easier and more convenient for the user.
    2727Everything is precompiled and distributed in appropriate containers for the different operating systems and platforms (e.g. .deb files for debian based linux systems and .exe files for windows etc.).
    2828
    2929
     30----
     31= Future design =
    3032
    31 == Future design ==
    32 
    33 === Overview ===
     33== Overview ==
    3434Some basic design decisions
    3535  * In the first place we stick to Premake. If someone offers a working solution with other tools like CMake, we are open to change that decision.
     
    4242  * We don't use special "subversion tricks" like externals definitions and instead keep separate identical copies of libraries if necessary. Storage isn't a problem and we don't update the libraries often. Other arguments brought up by Philip: "... it'll probably confuse Trac and it'll probably make mirroring/migrating to Git harder".
    4343
    44 === Graphical overview of interaction between different components (future-version) ===
     44== Graphical overview of interaction between different components (future-version) ==
    4545[[Image(http://trac.wildfiregames.com/attachment/wiki/BuildAndDeploymentEnvironment/future-build-environment-overview.png?format=raw)]]
    4646
    47 === Overview of the repository structure ===
     47== Overview of the repository structure ==
    4848
    4949{{{
     
    8787}}}
    8888
    89 === Updateworkspaces ===
     89== Updateworkspaces ==
    9090
    9191Updateworkspaces must check if the library is present and up to date. If not, it should stop and display an error.
     
    9393
    9494
     95----
     96= Macosx packaging =
    9597
    96 == Macosx packaging ==
    97 
    98 === Where to place which files? ===
     98== Where to place which files? ==
    9999||'''Name'''||'''Readonly'''||'''Description'''||'''Path MAC'''||'''Determined by/Set where?'''||
    100100||Game data root||Y||Data-Directory for static game data||[Bundle]/Contents/Resources/data||m_rdata in Paths.cpp||