...If the
captured script were executed in dry-run mode the output should be the same as the input.
A typical use is to determine what a complicated script, like libtool, will end up doing in the particular situation where it is used.
There is a scheme to determine which commands are dry-run (not all should be) and what to do when the behaviour of the script would depend on the output of commands that were never run.
Code so far posted is quite immature.
AutoTool4D(autotool for d language) is a project that demo how to use autool(autoconf,automake and libtool) to compile d language, it also demo how to using libiconv and gettext to write I18N/L10N program in d language and so on.
When writting portable C++ CORBA code one finds that each ORB vendor has its own set of libraries, include files, caracteristics, etc. This project's goal is both:
1. to provide a set of autoconf/automake/libtool macros to support as many ORBs (C & C++)
The bootstrapper program is designed to work along with autoconf, automake and libtool. It will scan a project's configure.in and generate a custom made bootstrap script which will then be used to create a configure script. It will also be able to clean
Compliant and Reliable File Transfers Backed by Top Security Certifications
Cerberus FTP Server delivers SOC 2 Type II certified security and FIPS 140-2 validated encryption.
Stop relying on non-certified, legacy file transfer tools that creak under the weight of modern security demands. Get full audit trails, advanced access controls and more supported by an award-winning team of experts. Start your free 25-day trial today.
The GPTK Project provides a base project using GNU configure, automake, libtool, etc. It can and is used to incubate new projects that desire to use these GNU tools. Basicly unpack the tar, change, run the prep.sh script, and you are ready to work.