Re: [Chicken-users] Anyone successfully installed iup on Windows?

[Thomas Chust]

2011/1/25 Matt Welland <address@hidden>:
> [...]
> Your success is good to hear. Can you share some details of how you did
> this?
> [...]

Hello Matt,

well, I did the canonical thing:

 * Install a fresh Windows XP and all available system updates in a
   virtual machine
 * Add C:/Programme/MinGW/bin, C:/Programme/CHICKEN/bin and
   C:/Programme/IUP to the system path
 * Download and unzip mingw-get 0.1 alpha 5 into C:/Programme/MinGW
 * Run `mingw-get install mingw-developer-toolkit mingw32-gcc
   msys-bash` in a Windows shell
 * Download and unzip CHICKEN 4.6.3
 * Run `make PLATFORM=mingw-msys PREFIX=C:/Programme/CHICKEN` and
   `make PLATFORM=mingw-msys PREFIX=C:/Programme/CHICKEN install` in
   an MSYS shell inside the CHICKEN source directory.
 * Download and unzip ffcall 1.10
 * Run `./configure --prefix=C:/Programme/CHICKEN`, `make` and `make
   install` in an MSYS shell in the ffcall source directory
 * Download and unzip IM 3.6.3, CD 5.4.1 and IUP 3.3 into
   C:/Programme/IUP
 * Delete all Lua related files from C:/Programme/IUP and
   C:/Programme/IUP/include — who needs lua if you can have CHICKEN?
   ;-)
 * Checkout the trunk version of the IUP egg from
   https://code.call-cc.org/svn/chicken-eggs/release/4/iup/trunk
 * Run `CSC_OPTIONS='-IC:/Programme/IUP/include -LC:/Programme/IUP'
   chicken-install -D no-library-checks` in an MSYS shell in the IUP
   egg source directory
 * Run `csi -R iup -e '(let ([dlg (dialog #:title "Test" (button "Push
   me!" #:action print))]) (show dlg #:modal? #t))'` to verify the
   installation works

That the IUP egg's setup script reacts to the feature identifier
no-library-checks by replacing all checks using (find-library ...)
with constant #t is a new addition as of today. So yesterday I
actually edited the setup script to that effect, but I just
verified that the feature definition actually works as expected.

Note that you don't have to install ffcall into the same directory
tree as CHICKEN, but I found that convenient and it saved extra
-I... and -L... options in CSC_OPTIONS. Also note that the build
process of ffcall breaks if you try to compile it in a directory whose
absolute path contains any spaces. Some time ago, CHICKEN's build
process also couldn't handle this, though I think it has been fixed by
now. I don't know if anything breaks in case the destination paths
contain spaces, since I'm running a German copy of Windows XP where
the target prefix for program files doesn't contain spaces by
default. But if you have a differently localized version, you might
want to install things under some less canonical prefix without
spaces, just to be safe.

> [...]
> 2. I tried the same changes I had done previously but get the following
> error,
> [...]
> Warning: reference to possibly unbound identifier: pointer-vector-set!
>
> Warning: reference to possibly unbound identifier: make-pointer-vector
>
> Error: module unresolved: iup-base
> [...]

This likely means that your CHICKEN installation is too old. Which is
why I advised you to use the latest snapshot release 4.6.3.

I hope this helps. If you insist, I can also package a binary archive
with all the necessary ingredients, but before you complain that this
build process is complicated, try to get Gtk+ running on Windows and I
think you will change your mind ;-)

Ciao,
Thomas


-- 
When C++ is your hammer, every problem looks like your thumb.