From 094535c010320967639e8e86f974d878e80baa72 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=B6rg=20Frings-F=C3=BCrst?=
X.Org X11 libXrandr development package
X.Org X11 libXScrnSaver A.K.A. libxss-dev
- development package
+ development package
Setup JAM:
Argyll makes use of a build system called
+ Makefile will run Jam with the -f flag.
+
Also on Linux and OSX you may have to make sure that certain + environment variables such as HOSTTYPE are exported, so + that other programs can see them.
You may also have to set the appropriate environment variable to
tell the Jambase which compiler you are using.
Something to watch on the Intel versions of OS X 10.4, is that your shell environment variable $MACHTYPE may be incorrect. On @@ -149,22 +154,25 @@ latter SDK to be able to incorporate the necessary function calls to access display and color profiles on Win2K and latter, so this may not work "out of the box".
-I've also successfully compiled using Microsoft VC++ 8.0 and VC++ - 9.0 Express (the free Microsoft compiler) plus the Microsoft - Platform SDK February 2008. To get this to work though, I had to - create my own batch file to setup the SDK environment variables MSSdk etc., because the batch - files provided with the SDK got confused by the presence of VC++6, - and didn't notice that VC++8 or 9 was configured.
+I've also successfully compiled using Microsoft VC++ 8.0, VC++ + 9.0 and VC++ 10.0 Express (the free Microsoft compiler) plus the + Microsoft Platform SDK February 2008. To get this to work though, + I had to create my own batch file to setup the SDK environment + variables MSSdk etc., + because the batch files provided with the SDK got confused by the + presence of VC++6, and didn't notice that VC++8, 9 or 10 was + configured.
Note that for some hard to fathom reason VC++ 9.0 refused to install on my Win2K development machine, so I had to install it on a WinXP machine and then copy the installation back to Win2K, and manually complete the installation. There seems to be no reason for this limitation, since the VC++9 compiler/linker etc. seems quite happy to run on Win2K.
-I haven't attempted to compile for Win64, and currently the
- Jambase isn't setup for cross compilation, nor have I tried to
- setup a native build environment yet on Vista64.
+
I have succeeded in cross compiling for Win64 using
+ x86_64-w64-mingw32-gcc, but currently the Jambase isn't setup for
+ cross compilation and I used a hack to build the native
+ executables with a native compiler before invoking the usual Jam
+ compilation in the cross environment.