gtgt Or The Life After

In 2000, I had released the Gnu Tem­plate Gen­er­a­tion Tools that instan­ti­ate a set of sources which were read­i­ly pre­pared for being devel­oped, com­piled, and installed with the GNU ‘Autoconf/Automake’ devel­op­ment envi­ron­ment. A few years lat­er they were passed — by new lan­guages, tech­niques, and tools. But now we have revi­tal­ized gtgt for spe­cial rea­sons of open source com­pli­ance:

What it is:

gtgt — spo­ken: git­ty-git­ty — is a set of scripts, which ini­tial­ize a c/c++ project in a way, that it can direct­ly be man­aged by the GNU Auto­tools — although one can nev­er­the­less them under the terms of any oth­er open or closed source license. How do you use the tools is explained in the gtgt-FAQ, which is part of every gtgt pack­age. The Gnu Tem­plate Gen­er­a­tion Tools have been revi­tal­ized for enabling us to cre­ate test data, that — under the lead­er­ship of the Open Chain Too­long Work­ing Group — become part of a Test-Dri­ven Open Source Com­pli­ance Automa­tion.

Where you can get it:

gtgt can be down­loaded from Github — by cloning the repos­i­to­ry as usu­al­ly, by down­load­ing it as a zip file via the GitHub tools, or by down­load­ing it from the gtgt ‑release-branch.

How do you use it:

The usage of gtgt is described in an FAQ.

What you may do with gtgt:

gtgt is dis­trib­uted under the terms of the GPL‑3.0. But its out­put — the cre­at­ed code and the instan­ti­at­ed project direc­to­ry includ­ing some spe­cif­ic gtgt-scripts may be dis­trib­uted under any oth­er open- or closed-source-license. The out­put is not a deriv­a­tive work of gtgt, even if it has been derived from gtgt by c&p.

Leave a Comment

Your email address will not be published. Required fields are marked *

To top