compiler manifest wrapper Files

bc2.cmd                 compiler wrapperfor bc++ 5.5.1 and later versions of the compiler.  MAY work with embarcadero compiler, but I have not seen their compiler options.  was supposed to generate both 32 and 64-bit exe's,but I don'tknow what executables or switches you use to do that with the newer borland compilers or embarcadero compilers.
bc31.cmd                sets up compiler environment for old BC++3.1 and adds to path, goes to bin dir
bcc.cmd                 compiler wrapper for BC++ 5.5.1, older version of bc2.cmd,  does the basics, and does not follow the
bcc55.cmd               simply jumps to borland c++ 5.5.1 compiler's include directory.  I used to spend alot of time there.
distall.cmd             calls distbc2.cmd distgp.cmd distgw.cmd distgw2.cmd distgwix.cmd with the parameters c:\u c:\prj which works for my development setup.  you can configure it for yours.
distbc2.cmd             the batch file which copies and overwrites bc2.cmd FROM from first specified directory to the directory tree specified by in 2nd specified dir.
distgp.cmd              the batch file which copies and overwrites gp.cmd FROM from first specified directory to the directory tree specified by in 2nd specified dir.
distgw.cmd              the batch file which copies and overwrites gw.cmd FROM from first specified directory to the directory tree specified by in 2nd specified dir.
distgw2.cmd             the batch file which copies and overwrites gw2.cmd FROM from first specified directory to the directory tree specified by in 2nd specified dir.
distgwix.cmd            the batch file which copies and overwrites gwix.cmd FROM from first specified directory to the directory tree specified by in 2nd specified dir.
gp.bat                  older, less capable version of gp.cmd
gp.cmd                  DJGPP dos compiler wrapper. does not make manifests (DOS doesn't use them).  simplifies the process of making monolithic executables which run with DPMI (it's complicated to make a usable .exe with DJGPP). Remember to use 8.3 filenames (8 characters . then 3 characters), unless you are using LFN driver.  compiler requires windows XP mode or XP to run.  Does not follow the same conventions as the other compiler wrappers, in that you don't specify exe as a separate commandline parameter!  I may change this later to keep them in conformity.
gpl3license.txt         the license for these files
gw.cmd                  older single-output-exe version of gw2.cmd
gw2.cmd                 outputs both 32-bit and 64-bit executables simultaneously, if possible, using mingw, mingw-w64.
gwix.cmd                outputs both 32-bit and 64-bit executables simultaneously with mingw-w64 vityan freebsd/ubuntu compilers (x64 hosted)
install-compilers.cmd   installs (extracts) mingw-w64 compilers from current directory to root
install-djgpp.cmd       automates the process of installing DJGPP dos compiler.
wrapper.cmd             the batch file that packages all this stuff together into a zip file for sourceforge.net.
zap-mingw-w64-compiler.cmd       zaps (deletes) an installed mingw-w64 compiler


things you need to know:

with gw2 and gwix:
%cpp32% or %cpp64% is a 32-bit or 64-bit compiler executable's full path.
%base32%\mingw\include or %base64%\mingw\include is the compiler's include directory.
same goes with lib.
%base32%\mingw\lib or %base64%\mingw\lib is the compiler's libraries directory.
you will probably spend most of your time there.
gw2.cmd and gwix.cmd and bc2.cmd make a 32\dand 64\directory to put their executables and
manifests and compiler error output other stuff into.

gw2.cmd, gw.cmd both copy the appropriate DLL's that they require (the stdc++ library due to the
ABIs) into the 32\ and 64\ directories, except for gw.cmd which uses the current directory for
everything.

gw2.cmd, bc2.cmd, gw.cmd create manifests if you want one: 2 basic kinds, a static generic
windows 9x+ compatible manifest, and a manifest for windows vista/7/8+ in which you can
specify build numbers (gw.cmd) or have build numbers automatically created for you (gw2.cmd
and bc2.cmd) specify version, app name, executionlevel, dependencies, etc.  I have some
things commented out which I am meaning to test.  with a manifest, windows either likes
it or it doesn't.

bc2 is basically a work in progress.


running gw2.cmd or any of the batch files will give you help.