build-windows-package.sh

#!/bin/sh
set -ev

# This is how the Windows package for release are built.

# Any existing TECkit-<version> folder and TECkit-<version>.zip will be deleted.

. ./build-windows-common

# metadata
VERSION="2.5.12"
foldername=TECkit-${VERSION}
filename=${foldername}.zip

# remove old folder and zip file
rm -rf $filename $foldername

# create folder for distribution
cp -a $WINDOWS $foldername
cd $foldername

# add files to folder

# runtime
for bit in 32 64
do
    set_compiler $bit

    # The cross-compiler defaults to the Windows threading model
    # which does not require the libwinpthread-1.dll runtime file.
    # This file is needed if the POSIX threading model is specified.
    # On an Ubuntu system see one (or more) of
    # /usr/share/doc/gcc-mingw-w64-i686/README.Debian
    # /usr/share/doc/g++-mingw-w64-i686/README.Debian
    # /usr/share/doc/gcc-mingw-w64-x86-64/README.Debian
    # /usr/share/doc/g++-mingw-w64-x86-64/README.Debian
    # (might be the same contents) for more details.
    # TECkit 2.5.4 and 2.5.6 on Windows did need this file,
    # so presumably used the POSIX threading model.
    for FILE in $RUNTIME libstdc++-6.dll # libwinpthread-1.dll
    do
        cp -p $($HOST-gcc -print-file-name=$FILE) ${bit}-bit
    done
done

# documentation
unix2dos -n ../README README.txt
mkdir Documentation
mv *.1.pdf Documentation
cp -p ../docs/TECkit_Language.pdf Documentation
cp -p ../docs/TECkit_Tools.pdf Documentation
mkdir Developers
cp -p ../docs/Calling_TECkit_from_VB.doc "Developers/Calling TECkit from VB.doc"
cp -p ../docs/Calling_TECkit_from_VB.pdf "Developers/Calling TECkit from VB.pdf"
cp -p ../docs/TECkit_Binary_Format.pdf Developers

# code
mkdir Developers/Public-headers
cp -p ../source/Public-headers/*.h Developers/Public-headers
cp -a ../source/Sample-tools Developers

# create zip file from folder
cd ..
zip -r $filename $foldername