Windows

Ingredients

To follow the instructions in this document you will need

1. InnoSetup
2. The latest EUPHORIA package that can translate the sources you want to release
3. UPX (Executable compressor utility)
4. Mercurial
5. Either
   1. Prebuilt binaries of the tip of EUPHORIA and a prebuilt euphoria.pdf file of the tip of EUPHORIA.
   2. Watcom C and GNU MinGW C and PDFLatex or a prebuilt euphoria.pdf of the tip of EUPHORIA

Steps

Let EUDIR be your existing production path of 4.0.0 and CODIR be your checkout trunk path of the 4.0 branch. CODIR must contain no local changes. Use 'hg status' and ensure there is no output. Make sure that 'hg outgoing' produces no output.

1. Change directory to EUDIR\source and run configure --eubin EUDIR\bin --build ..\build --align4 --noassert --release
2. Copy EUDIR\bin\*.exe, *.a, *.lib to CODIR\bin. This step gives us the tools we cannot make without other sources.
3. Run WATCOM 'wmake' in CODIR\source to make new binaries 'wmake all'
4. Run 'wmake test' to ensure the tests work
5. Run wmake all htmldocs pdflatex to create the documentation.
6. Use MinGW Shell to configure again.
7. Run './configure --eubin EUDIR/bin --build ../build --align4 --noassert --release'
8. Run 'make library' to create the MinGW library files
9. Copy CODIR\build\*.exe, *.a and *.lib to CODIR\bin
10. Use build.bat in packaging/win32 to do several tasks with one command. You must have UPX.exe (Ultimate Packer for Executables) and ISCC.exe (Inno Setup) parent directories in the PATH environment variable for this to work.
    1. compress the EXE files with UPX in your bin directory
    2. Make a pristine copy of the latest files according to your repository in CODIR/packaging/win32
    3. Run the ISS file to create package.
11. Create euphoria-4.x.y.exe with 'build.bat euphoria.iss'
12. Create euphoria-ow-4.x.y.exe with 'build.bat euphoria-ow.iss'

Tests

Create tickets as you see problems come up or write them in a document if you are testing offline. Look at the ChangeLog in CODIR\docs\release. The Change Log should tell you what has been fixed. Try these things out and make sure they really are fixed.

To really test this package you should:

1. Uninstall your production EUPHORIA or use a computer that doesn't have it.
2. Ensure that there are no stray environment variables, registry keys left laying around from the install. If they are please eliminate them.
3. Install your package into the clean machine to an unconventional location try 'EUFORIA' or 'C:\YOU4EEAH' or paths with spaces 'C:\E U P H O R I A'. The EUPHORIA with WATCOM installer should refuse to allow you to install to a Path with spaces on account of WATCOM not working correctly with that configuration. The EUPHORIA only package will allow you to install and once installed Euphoria should run correctly when installed to a place with or without spaces.
4. Use your start menu and open the items that are there. Make sure they open what they are supposed to.
5. Use Explorer to run the demos. See how they react to your environment.
6. Run some of your EUPHORIA programs and third party programs.
7. Check the documentation:
   1. can you open the PDF documentation?
   2. can you open the local HTML documentation? Does the Javascript search Engine work?
      1. Can you search for 'find_all' and will it give you the two options? Does clicking on them take you to their definitions?
   3. Can you open the online documentation?
   4. Can you open the other online resources?
8. Run the UNIT tests
9. Uninstall. Check if there is anything left over from the install. Does it clean the environment or configuration files? Does it remove its Registry keys it created? Does it remove itself from the PATH? These are what a well behaving uninstaller should do.