Well it is about time that I start doing some automated building for my projects aswell..

When I release software my process with other processors have been (And it will be the same with STM32 projects):
- Automatically create a version (headerfile etc) that will be part of the final .elf image so that it can be extracted in the field
- Automatically check in new version file into version repository
- Automatially tag correct versions of sourcefiles and projects in repository
- Update a clean directory to the tagged versions of the source.
- Do automatic build of applications
- Create any needed installers, modify binary if needed and move release to designated release spot.
- Create a report about build settings, size etc.

All this is automatically done in order to avoid forgetting something.
Now I need to do the same with RIDE. I realise that I could manually create gnu makefiles, but this would inevitably cause errors, when a project is changed in Ride, but by mistake not updated in the makefile.
Then I could create a tool to parse the rprj and rapp files and automatically create suitable makefiles from that. Apart from the work involved, there is a risk that you guys decide to alter the rprj and rapp file structure and then I need to play catch up or stay at an older version of ride..

However I would not mind just to use Ride from the command line to execute my builds. Is there a way to do this or would you please consider making this possible?

Any other way to handle the release of several applications automatically would be appriciated.

Shameless - BUMP
I would still like to hear if Raisonance plan on adding any form of automated build functions to RIDE? So that we can make it a part of an automatic release script.
If not I need to make a tool to parse and build from rapp files, because I really want it in order or reliably be able to create releases with 100% trackability..

A good and (IMO) relative simple option would be to implement a simple command line interface to ride.exe - All I need is the possibility to do something like:
"ride7.exe -build testproject.rapp"
from within a batch file and return an errorlevel on failed builds and either a logfile or commandline output of build log during the build.

BR
Henrik

In the coming version of Ride7, the building process could be automated using Ride7 jcript player.

The user will be able to write jscript files calling directly the projectmanager functionalities like opening project files, building them, debugging them.

Behnaz

Hope that can solve my issues with getting a release process in order then, before I am forced to do it by creating my own .rapp parser.

It need to be able to work together with our version control (cvs/svn) and other external tools? Or at the very least generate a form of makefile that a another maketool will accept (i like gnu make)

BR
Henrik

The scripting facilities in Ride7 will be for automating Ride7 commands (build, debug, etc)

If you want to use Ride7 to generate makefiles in spite of running the make tools you can already do it with modifying the tools ".config" files.

For example in GCC.config you can find the different steps for building the gcc command line. You can modify these steps to generate any kind of makefile you need , or launch any application you want.

Best regards,
Behnaz