Menu

Tree [r86] /
 History

HTTPS access


File Date Author Commit
 arttool 2009-01-03 evildave [r85] Bring some old tools back from the dead.
 clientserver 2009-01-02 evildave [r84] Update a few comments.
 guify 2009-01-03 evildave [r86] Fix a release-mode compiler warning.
 releases 2006-05-21 evildave [r1] Get repository moved from CVS to SVN after SF's...
 squat 2009-01-03 evildave [r85] Bring some old tools back from the dead.
 Cleaner.bat 2007-11-18 evildave [r10] Add standard Makefile build to squat, 'upgrade'...
 Everything.sln 2007-12-03 evildave [r19] A little more collateral damage.
 README.txt 2007-12-17 evildave [r49] Add s'more build instructions
 makefile 2009-01-03 evildave [r85] Bring some old tools back from the dead.

Read Me

The code has been built by gcc under Ubuntu (Feisty) Linux, MinGW and the free 
Visual C++ 2005 & 2008 Express Editions.  It used to be maintained under 
Visual C/C++ 6 and Visual Studio.Net 2002, but my install media got munched, 
and that's just too many targets to bother with for the moment.

There are GNU Make and MS NMake scripts available.  

The vcproj files are the 2008 edition versions, and are only Makefile Project 
wrappers.

To build a debug version from the command line...

MingW: make
Linux: make
Visual Studio tools: nmake /f nmake.mak

The GNU Makefile detects OS=Windows_NT in the environment to make a Windows 
build.

You can set a CFG=release or CFG=debug, and the top-level project makes also 
accept targets of debug, release, clean, all.


Visual C++ build instructions for art tools

Some of the imaging tools are built with ImageMagick 6.2.0-8 
Some of the imaging tools are built with SDL for preview modes

ImageMagick can be had from http://imagemagick.org/ 

Extract the ImageMagick source archive to sf/ImageMagick.

Build and run sf/ImageMagick/VisualMagick/configure

Select 'static multithreaded DLL runtimes'
Uncheck 'Generate Visual Studio 7 format' (unless you're using .NET)

Open the project it made in sf/ImageMagick/VisualMagick, and build that

SDL is a little more simple for VC.
Simply grab a VC6 build (with libs/includes), then put it in sf/SDL
Optionally, you could build it for yourself.

I will add these libraries to version control to be properly LGPL license 
complient... once I settle on precisely how it should all fit together. 

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.