WarpIN basically consists of two parts:
  1. The "back end" (BE), which is portable and consists of a single C++ class called WIArchive, making it annoyingly easy to use. The back end resides in the wiarchive subdirectory and was written by Jens B„ckman. First of all, include ../wiarchive/wiarchive.h in your source. To define an archive called arc, you code WIArchive arc; and you're off. Calling functions is really easy too; to open an archive called Test, you use arc.open ("Test");. If you run into some problem, the source should be pretty well commented out. It's maybe even easier to read than this.

  2. The "front end" (FE) has everything that's operating-system specific. This is developed by me, Ulrich M”ller. There are actually two "front-ends" right now:

    1. WIC.EXE, the "WarpIN Archive Creator", which currently is too dumb to do much except for packing files in the current directory into an .WPI archive. Note that a .WIS script file (the installation profile) must exist of the same filestem. A sample profile script is included (TEST.WIS). So you can go with wic -a test 1 * and the current (WarpIN) directory will be copied to the archive TEST.WPI. Note that the profile will then also be in the archive so that the installer (below) will find it.

      WIC.EXE currently can only handle files in the current directory.

    2. WARPIN.EXE is the real installer. You best create a program object for it and associate it with .WPI files. You can then double-click on the archive which you have just created and the installer will analyze the script in the archive and do what it's told to there.