On 2004.07.22, Andrew Piskorski <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 22, 2004 at 04:59:25PM -0400, Dossy Shiobara wrote:
> > I've managed to produce binary builds of AOLserver on Win32 using only
> > the "free" Microsoft Visual C++ Toolkit 2003 (and associated SDKs)!
> >
> > I built Tcl 8.4.6 and AOLserver 4.1.0 (CVS HEAD) and AOLserver 4.0.7. I
>
> And this is using some form of makefile-like programmatic build
> process from the command-line? If so, this is This is excellent!
In a sense, yes. The build is driven by a single Tcl script. So, as
long as you have Tcl built (which you must, if you plan on building
AOLserver) then you've got everything you need.
> I already have the old MS Visual C++ 6.0 compiler, but the "project
> files" for its GUI build environment are just horrid to work with.
I haven't tested with the commercial MSVC++ 6.0, only the new Microsoft
Visual C++ Toolkit 2003 compiler.
> Are the Windows makefiles (or whatever) and build instructions in CVS
> yet?
The build script is in CVS HEAD (win32/build.tcl) but there are NO
instructions yet. Expect to see a "How to build AOLserver on Win32"
page on the wiki, soon. :-)
The short explanation:
C:\> vcvars32.bat
C:\> cd \path\to\aolserver\source
C:\...> tclsh win32\build.tcl
... build output scrolls by ...
C:\...> tclsh win32\build.tcl install
... installation output scrolls by ...
C:\...> cd installed
C:\...\installed> bin\nsd.exe -ft sample-config.tcl
At this point, you should be up and running!
NOTES:
1. vcvars32.bat (or whatever it's called) ensures that cl.exe and
link.exe are in your PATH, that INCLUDE and LIB variables are set
to the appropriate location where VC++'s include and libraries
live.
2. The build.tcl script currently assumes that Tcl was built in
..\tcl_core-8-4-6 (relative to the top of the AOLserver source
directory) and when you built Tcl, you did a "nmake -f
makefile.vc install INSTALLDIR=installed" so that Tcl was
installed into ..\tcl_core-8-4-6\win\installed. That's just how
my build environment is set up -- I plan to enhance the build.tcl
script to let you pass in the path to the Tcl install from the
command line, but for now it's hard-coded in.
3. Also, sample-config.tcl from CVS HEAD will work, but the one in
the aolserver_v40_bp branch will NOT -- I didn't backport the
"fix" to the script yet.
4. I use Cygwin "cvs" to check the code out of CVS, then start a
regular DOS "cmd.exe" shell to do the actual build.
OK, I guess I could just cut-and-paste this up onto the wiki now. :-)
How to build AOLserver on Win32
http://panoptic.com/wiki/aolserver/1332
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
