Difference between revisions of "Build tool"

(Overview)
Line 12: Line 12:
 
This will lead to a better overall build infrastructure, automated (nightly) builds, and things alike. We work on our own branch of the sourcecode, but will sync it from time to time with the EiffelStudio SVN trunk.
 
This will lead to a better overall build infrastructure, automated (nightly) builds, and things alike. We work on our own branch of the sourcecode, but will sync it from time to time with the EiffelStudio SVN trunk.
  
Other side-products of the effort are:
+
Other goals of the effort include:
  
* Transition of EiffelStudio from GOBO 3.4 to a more current GOBO release
+
* Transition of EiffelStudio from GOBO 3.4 to a more current GOBO release.
* Extension of geant tasks
+
* Extension of geant tasks as seen necessary.
 +
* Minimization of foreign software tools required for the compilation.
 +
** Specially to get rid of the dependency on Cygwin on Windows.
 +
* Production a one-click-and-go script for easy installation and compilation.
  
== Goals ==
+
We aim to have a compact build process by using only Eiffel related tools (mainly geant scripts).
We aim to have a compact build process by using only Eiffel related tools (mainly geant scripts) and thus minimizing the needed (alien) tools to get an EiffelStudio compilation going.
+
  
== Steps ==
+
== Current Status ==
* produce a one-click-and-go script for easy installation
+
* get rid of windows dependency for bash
+
* remove script-only tools like finish_freezing, Makefile.sh, etc.
+
  
== Done ==
+
There are already a number of GEANT scripts available in the 'scripts' directory. These scripts cover compilation of EiffelStudio, the runtime and the libraries. An existing GOBO installation will be used if available. The setup checker script checks for major problems in the setup.
  
* first draft of geant scripts to build c-libraries
+
== Todo ==
* first draft of setup-checker tool
+
  
== Milestones ==
 
 
== Todo ==
 
 
* makefile/batchfile for getting the installation started (for users unexperienced with gobo/geant)
 
* makefile/batchfile for getting the installation started (for users unexperienced with gobo/geant)
 
* expand setup-checker
 
* expand setup-checker
 
** find more dependencies on windows
 
** find more dependencies on windows
 
* automatical use of existing gobo-installations
 
* automatical use of existing gobo-installations
 +
* full migration of the tree to current GOBO
 +
* building a delivery
  
 +
== Team ==
  
== Team ==
+
* [[User:schoelle]]
 +
* [[User:sanakan]]
 +
* [[User:trosim]]
 +
* [[User:jfiat]]

Revision as of 13:43, 18 January 2007


Overview

The whole build process of EiffelStudio is rather tedious at the moment. This project aims to simplify this by various means:

  • Tight integration of GOBO geant into the build process
  • Setup checker - a script that checks that the current development environment is correctly setup for the development on EiffelStudio
  • Fully automated build scripts that enable the compilation of the runtime, libraries and EiffelStudio with a single command
  • Automatic generation of an Eiffel delivery from a successful compilation, including all necessary tools

This will lead to a better overall build infrastructure, automated (nightly) builds, and things alike. We work on our own branch of the sourcecode, but will sync it from time to time with the EiffelStudio SVN trunk.

Other goals of the effort include:

  • Transition of EiffelStudio from GOBO 3.4 to a more current GOBO release.
  • Extension of geant tasks as seen necessary.
  • Minimization of foreign software tools required for the compilation.
    • Specially to get rid of the dependency on Cygwin on Windows.
  • Production a one-click-and-go script for easy installation and compilation.

We aim to have a compact build process by using only Eiffel related tools (mainly geant scripts).

Current Status

There are already a number of GEANT scripts available in the 'scripts' directory. These scripts cover compilation of EiffelStudio, the runtime and the libraries. An existing GOBO installation will be used if available. The setup checker script checks for major problems in the setup.

Todo

  • makefile/batchfile for getting the installation started (for users unexperienced with gobo/geant)
  • expand setup-checker
    • find more dependencies on windows
  • automatical use of existing gobo-installations
  • full migration of the tree to current GOBO
  • building a delivery

Team