Ticket #884 (closed enhancement: invalid)

Opened 2 years ago

Last modified 22 months ago

A few nifty shell scripts for synching/building

Reported by: jamesb192 Owned by: bonefish
Priority: normal Milestone: R1
Component: Build System Version: R1 development
Cc: Blocked By:
Platform: All Blocking:

Description

The script sink accepts a sing parameter. a number will check out the selected revision number, while 'latest' will pull the latest version. the script set accepts a single parameter (the architechture to set up) and creates a seperate generated dir for each compiler/architecture pair. the script buildit accepts two paramters the first is the architechture to build for and the second is a version string to append to the output filenames.

Attachments

buildit (1.2 kB) - added by jamesb192 2 years ago.
the buildit script
sink (209 bytes) - added by jamesb192 2 years ago.
The sycnchronization script
set (1.3 kB) - added by jamesb192 2 years ago.
The build tools builder script
scrip.tar (10.0 kB) - added by jamesb192 2 years ago.
added () to make it work better. expand into a directory and run ./init

Change History

Changed 2 years ago by jamesb192

the buildit script

Changed 2 years ago by jamesb192

  • attachment sink added

The sycnchronization script

Changed 2 years ago by jamesb192

  • attachment set added

The build tools builder script

Changed 2 years ago by jamesb192

Oops, I forgot to mention that the scripts create automatic build logs and inject them into HTML files, it uses two HTML fragment 'head' and 'tail' which are prepended and appended respectively. the logs/html files are not intuitively named.

Changed 2 years ago by jamesb192

added () to make it work better. expand into a directory and run ./init

Changed 22 months ago by bonefish

  • status changed from new to closed
  • resolution set to invalid

I don't the scripts are *that* helpful. Most developers and enthusiastic testers have their own strategy to update and build the tree and others use the pre-built images anyway. I, for instance, have several generated subdirectories (generated-gcc2, generated-gcc4, generated-ppc) around (there's no need for symlinks, the build system supports arbitrarily named output directories anyway). Moreover splitting up stdout and stderr is not very helpful.

Note: See TracTickets for help on using tickets.