Overview

Artifact ID: b21ae9a109cb7169d378f8bcba643776913a0e63
Page Name:chicken-iup-build
Date: 2017-09-21 04:57:51
Original User: jmoon
Next 6843e8ac9dbda9858309510e0ac92a1336e90377
Content

2017 notes on building installer on mingw. Build was tested on Windows 7 VM and Windows 10 physical installation.

* Install OS of choice (It appears that Windows XP is likely no longer an option due to mingw not being able to download packages anymore)

* Install Mingw (mingw-developer-toolkit mingw32-gcc msys-bash)

* Install Inno Setup

* Download / clone chicken-iup fossil

* Get into "msys" (c:/MinGW/msys/1.0/msys, for example)

* Add entry into /etc/fstab, mine looked like follows:

# /etc/fstab -- mount table configuration for MSYS. # Please refer to /etc/fstab.sample for explanatory annotation.

# MSYS-Portable needs this "magic" comment: # MSYSROOT=C:/MinGW/msys/1.0

# Win32_Path Mount_Point #------------------------------------- ----------- C:/MinGW /mingw C:/chicken-iup /chicken-iup C:/Users/IEUser/Downloads/ffcall /ffcall C:/Users/IEUser/Downloads/chicken-iup /ciup

* In msys shell, run make

* Assuming build ran through successfully, open chicken-iup.iss file in Inno Setup. Click "Run". This will create the installer.

* Notes: Remember that Windows uses it's "PATH" variable to load libraries. So chicken-iup/bin and chicken-iup/lib must be in the path. The installer does this, but if you try to test before creating the installer, some of the libraries will not work. You can either set them manually, or run the installer to test it out. Also, a few of the eggs were unable to be the latest version. I'm not sure what exactly they changed, but the latest version of the iup egg was tricky. These may be able to be fixed with some more work, but I didn't get them working.

* Run `csi -R iup -e '(let ([dlg (dialog #:title "Test" (button "Push me!" #:action print))]) (show dlg #:modal? #t))'` to verify the installation works