| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
With the current patch, slibtool respects --dry-run by turning the
various modes (compile, link, install, execute) into no-ops. For at
least the compile and install mode, it should be possible to output
complete information about the steps that would be performed under
default operation conditions, however that is not yet implemented.
|
|
|
|
|
|
|
|
|
|
|
|
The idea was nice, the functionality was helpful for development, yet the
resulting layout and overall appearance were rather awful. Regardless of
the effort that was put into this sophisticated flavor of the usage
screen generator, and despite it's utility for debugging, it is now
being replaced with a simpler, two-field-only variant.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This patch adds functionality to slbt_output_exec that colors/annotates output
if outputting to a terminal, or annotation is explicitly enabled.
Currently annotated output includes emboldening "slibtool:" and giving it a
magenta, emboldening and coloring the step (compile, link, install) green, and
then annotating the "-o <output>" argument.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
