Changes between Version 43 and Version 44 of BuildAndDeploymentEnvironment

Timestamp:

Jan 17, 2012, 8:20:53 PM (12 years ago)

Author:

Yves

Comment:

--

BuildAndDeploymentEnvironment

@@ -145 +145 @@
 
 == 1. Change how the game handles default search paths ==
-Each OS should have its default behaviour that should make sense for that OS.
+Each OS should have its default behaviour that should make sense for that OS (see the table above).
 For Windows and Linux that's already quite good, but OSX requires improvements.
 
-It should by default work for two different situations. 
+It should be distinguished between three different situations. 
 
- 1. The current situation where the pyrogenesis binary is in 0ad/binaries/system, data is in 0ad/binaries/data etc... 
+ 1. The current situation in development where the pyrogenesis binary is in 0ad/binaries/system, data is in 0ad/binaries/data etc... 
  1. The situation when everything is in a bundle and the directories are organized as described in "Where to place which files?" in this article.
+ 1. Special situations where the users wants to use customized directories. It should be sufficient to solve this with preprocessor directives because if anyone want's to change it, it's either an advanced user or package maker anyway and generally there should be no need to change it. Each defined location in the table above should be customizable with one dedicated preprocessor directive. 
 
-In addition to that, all the paths should be customizable with parameters or environment variables (what's better?).
 
 == 2. Adjust the build-system and documentation for a separate library directory  ==
+Unassigned
+
+This task involves:
+ 1. Changing the repository structure as listed above
+ 1. Check if the libraries are present and up-to-date in update-workspaces.sh as described above.
+ 1. Adjusting premake4.lua, extern_libs4.lua, update-workspaces.sh and whatever else might be needed to support these changes
+ 1. Update all affected documentation
+
+Affected documentation: 
+ * BuildInstructions
+ * ... what else?
 
 == 3. Prepare the libraries for each platform ==
+Assigned: historic_bruno? [http://trac.wildfiregames.com/ticket/1112 #1112]
+
 Either include precompiled libraries or integrate the source-code into our build-scripts (called from update-workspaces.sh).
 It depends on the platform and probably on the library if the source or a precompiled version should be included.
 
 == 4. Write a script to create the bundle from the prebuilt libraries, the game-executables and the data ==
+Assigned: Yves has started creating such a script
+ * The script must support the new repository structure
+ * It should minimize maintenance effort
 
 == 5. Check CMake as an alternative in the future or work on improved XCode support for Premake ==
+Assigned: Juicyfruit works on an integration of CMake: [http://trac.wildfiregames.com/ticket/1104 #1104]
 
+== 6. Create a plain binary instead of a broken app-bundle ==
+Assigned: Yves [http://trac.wildfiregames.com/ticket/947 #947]
+
+The normal build-process should create a normal binary in 0a/binaries/system instead of a broken app bundle.
 ----