The POSIX-compatible Glasgow source code should build on Linux and Mac without trouble, but not before someone creates project build files for those platforms. The Glasgow code builds on Windows using a library called libunistd that provides POSIX Windows compatibity. Glasgow for WinXP is built using VC++ project files.
What Work is Needed to Build Glasgow on Linux Using autoconf?
The Glasgow autoconf files get outdated every time I make changes on the Windows side. For someone who is an expert in autoconf it may be no big deal, but that's not me. Linux build environment tools suck. Having wasted many frustrating hours on it in the past, don't expect me to help with autoconf. I don't have that kind of time to waste. If somebody else wants to take charge of supporting Glasgow autoconf, that's fine.
Choices in Linux build environments, in the order in which I would attempt:
I'm hoping someone else will pick up the Glasgow Linux build environment as a personal project, but I will get to it eventually if nobody else does. FYI, copies of cons and pmk sources exist in CinePaint CVS. No need to track down.
What About the Macintosh?
Who would like to create an Xcode project?
What's the Glasgow Code Layout?
The layout of Glasgow is that the app subdirectory builds to the executable. The other subdirectories build to static libs (that link with cinepaint app), except for subdirectories of the plug-ins folder that build to dynamic libs. The plug-ins link to the plug-ins lib, the utility lib, plus any relevant 3rd-party lib (e.g., TIFF). The 3rd party sources exist in CinePaint CVS. You don't need to download any external source code. To be neat, project files created should be in a separate subdirectory (like the VC++ project files in vcpp7 subdirectory).
What's Coming Next?
The img_img command-line tool with support for PPM, SGI, DPX and OpenEXR.