Opened 18 years ago
Closed 18 years ago
#884 closed enhancement (invalid)
A few nifty shell scripts for synching/building
Reported by: | jamesb192 | Owned by: | bonefish |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Build System | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
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 (4)
Change History (6)
by , 18 years ago
comment:1 by , 18 years ago
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.
by , 18 years ago
added () to make it work better. expand into a directory and run ./init
comment:2 by , 18 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
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.
the buildit script