From: saeed (
Date: Thu Mar 06 2014 - 06:37:06 CST

Dear Dr.Stone


I have downloaded TK 8.5.15 and FLTK 1.3
I have successfully compiled these libraries and also copied them inside
VMD\lib folder.
Then I added The TK and FLTK to the configuration options of VMD.
Then I compiled the src again and linked the new files using the previously
mailed makefile with the following changes.

# Turn things into objects
VMD_OBJS = $(VMD_CCPP:.C=.o) $(VMD_CC:.c=.o) $(
INCDIRS = -I../lib/tcl/include -I../lib/tk/include -I../plugins/include
-I../plugins/WIN64/molfile -I../lib/fltk -I.
LIBS = -ltk8.5 -lX11 -ltcl8.5 -lmolfile_plugin -lfltk -lX11 -lm
LIBDIRS = -L../lib/tcl/lib_WIN64 -L../lib/tk/lib_WIN64
-L../plugins/WIN64/molfile -L../lib/fltk/WIN64

# compiler and compiler directives
CC = cl.exe
CCPP = cl.exe
CPPFLAGS = /O2 /nologo /MT /DWIN64 -Dstrcasecmp=strupcmp /EHsc /Wp64


vmd_WIN64: $(VMD_OBJS)
 $(CCPP) $(CPPFLAGS) -c win32vmdstart.c /Fo../WIN64/win32vmdstart.o
 $(CCPP) $(CPPFLAGS) -c Win32Joystick.c /Fo../WIN64/Win32Joystick.o
 $(ECHO) "Linking " $@ "..."; \
 $(CD) ../WIN64 ; \
 if [ ! -r ./ ]; then \
   ln -s ../src/ ./ ; \
 fi; \
 link.exe /nologo Win32Joystick.o win32vmdstart.o $(VMD_OBJS)
/LIBPATH:"..\lib\tcl\include" /LIBPATH:"..\lib\fltk"
/LIBPATH:"..\lib\tk\include" /LIBPATH:"..\plugins\include"
/LIBPATH:"..\plugins\WIN64\molfile" /LIBPATH:. /LIBPATH:"..\src"
"..\lib\fltk\lib\fltk.lib" "..\lib\tcl\lib\tcl85.lib"
"..\plugins\WIN64\molfile\libmolfile_plugin.lib" winmm.lib user32.lib
ws2_32.lib Advapi32.lib Msvcrt.lib ole32.lib gdi32.lib shell32.lib
comdlg32.lib Libcmt.lib /OUT:vmd_WIN64;

And it compiled and linked without any problem.
but when I issue the make install there is no vmd.exe or any executable in
the installation directory so that I could run it in windows.

Please give me a hint that how the vmd.exe should be generated.
because I think I have compiled everything and the make install is
installing the files for a Linux based system (despite of the make
win64.opengl I have used to configure the build). It creates a csh shell
VMD executable not a windows executable.

On Wed, Mar 5, 2014 at 8:03 PM, John Stone <> wrote:

> Hi,
> Compiling VMD on Windows is complicated, and if you've only
> built Tcl, there's a lot more to do before you would have a complete
> build. You need to compile, at a minimum, FLTK, Tcl, and Tk, just to
> be able to run the normal VMD graphical user interfaces. Until you have
> all of the dependencies built, compiling VMD itself isn't going to
> be fruitful. It is usually the compilation of the library dependencies
> that represents the largest amount of work in compiling VMD.
> Cheers,
> John Stone