Difference between revisions of "Building tools requirements"
| Line 3: | Line 3: | ||
==High level requirement== | ==High level requirement== | ||
| − | * Look at other existing tools (e.g. | + | * 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. | ||
Revision as of 09:14, 27 October 2006
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 that provides a GUI front-end (e.g. 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.
