Building tools requirements - Revision history

Peter gummer: /* High level requirement */

2006-10-27T22:30:46Z

‎High level requirement

Neallester at 20:34, 27 October 2006

2006-10-27T20:34:58Z

Manus at 20:18, 27 October 2006

2006-10-27T20:18:26Z

Manus at 18:14, 27 October 2006

2006-10-27T18:14:58Z

Manus at 17:57, 27 October 2006

2006-10-27T17:57:44Z

Manus at 17:57, 27 October 2006

2006-10-27T17:57:30Z

New page

Here is a short requirements list for a graphical tool to perform automatic builds of code (Eiffel, C, ...), of documentation and anything else that needs to be build to perform a delivery of EiffelStudio. It has to be graphical because it is easier to see dependencies and will help people who do not know the format used for those scripts to modify those scripts.

==High level requirement==
* Look at other existing tools (e.g. VisualBuild)

@@ Line 5: / Line 5: @@
 * Look at other existing tools that provides a GUI front-end (e.g. [http://www.kinook.com/VisBuildPro/ VisualBuildPro] which is a commercial product) to get the best out of them. Another option is to have a syntax aware editor with project specific autocomplete capabilities.
 * Command line tool so that it can be launched as a cron job.
-* Multi platform.
+* Multi-platform.
-* Notion of tasks and dependencies between tasks. That way, internally it can build a graph and can optimize the build process depending on the number of CPU you have on your machine.
+* Notion of tasks and dependencies between tasks. That way, internally it can build a graph and can optimize the build process depending on the number of CPUs you have on your machine.
-* Pre-build tasks for Source control management (CVS and SVN), for file system manipulation.
+* Pre-build tasks for Source control management (CVS and SVN), or for file system manipulation.
 * Easy to create new tasks that can be reused by other projects.
-* Tasks are platform dependent so if running on windows, the unix tasks should not be ran.
+* Tasks are platform dependent so if running on Windows, the Unix tasks should not be run.
 * Launch task remotely on remote machine which has no binaries yet (that is to say the build tool needs to be compiled first and then the script launched). The remote access to the machine can be done using ssh/rsh.
 * Failure handling: when a task fails, the build should continue until all other tasks that do not depend on the failed task have completed or failed. Then a summary should be presented and the user can after fixing the issue or the task restart the building process for that task and all the other tasks that depended on it. This feature is necessary to make the creation of new build process for very large system debuggable.

@@ Line 3: / Line 3: @@
 ==High level requirement==
-* Look at other existing tools that provides a GUI front-end (e.g. [http://www.kinook.com/VisBuildPro/ VisualBuildPro] which is a commercial product) to get the best out of them.
+* Look at other existing tools that provides a GUI front-end (e.g. [http://www.kinook.com/VisBuildPro/ VisualBuildPro] which is a commercial product) to get the best out of them. Another option is to have a syntax aware editor with project specific autocomplete capabilities.
 * Command line tool so that it can be launched as a cron job.
 * Multi platform.

@@ Line 3: / Line 3: @@
 ==High level requirement==
-* Look at other existing tools that provides a GUI front-end (e.g. [http://www.kinook.com/VisBuildPro/ VisualBuildPro] which is a commercial product)
+* Look at other existing tools that provides a GUI front-end (e.g. [http://www.kinook.com/VisBuildPro/ VisualBuildPro] which is a commercial product) to get the best out of them.
-* Command line tool so that it can be launched easily.
+* Command line tool so that it can be launched as a cron job.
-* Notion of tasks and dependencies between tasks. That way, internally it can build a graph an optimize the build process depending on the number of CPU you have on your machine.
+* Multi platform.
 * Pre-build tasks for Source control management (CVS and SVN), for file system manipulation.
 * Easy to create new tasks that can be reused by other projects.

← Older revision		Revision as of 18:14, 27 October 2006
Line 3:		Line 3:

	==High level requirement==		==High level requirement==
−	* Look at other existing tools (e.g. ~~VisualBuild~~)	+	* Look at other existing tools that provides a GUI front-end (e.g. [http://www.kinook.com/VisBuildPro/ VisualBuildPro] which is a commercial product)
		+	* Command line tool so that it can be launched easily.
		+	* Notion of tasks and dependencies between tasks. That way, internally it can build a graph an optimize the build process depending on the number of CPU you have on your machine.
		+	* Pre-build tasks for Source control management (CVS and SVN), for file system manipulation.
		+	* Easy to create new tasks that can be reused by other projects.

@@ Line 1: / Line 1: @@
 Here is a short requirements list for a graphical tool to perform automatic builds of code (Eiffel, C, ...), of documentation and anything else that needs to be build to perform a delivery of EiffelStudio. It has to be graphical because it is easier to see dependencies and will help people who do not know the format used for those scripts to modify those scripts.
 ==High level requirement==
 * Look at other existing tools (e.g. VisualBuild)