Hi,
I'm out of town on vacation but I can help address your questions when
I return. We don't build the Windows versions of VMD using Makefiles,
they are compiled using the MSVC/MSVS project files in the subdirectories
of 'msvc'. The configure script does generate a makefile, but the main
thing it accomplishes in the case of Windows is to generate a couple of
machine-dependent header files VMD needs. In principle you can use any
Tcl/FLTK/etc libraries you want, but if you have some experience with
Windows development you will already know that you cannot mix different
C runtime linkage modes with multiple libraries, and that the C runtime
has to be consisent among the libraries you link against. Ihe the past
this issue has forced me to compile not only VMD, but all of its dependencies
from source code so that I could resolve these kinds of issues.
It's more tricky when you have black-box libraries involved also
(e.g. the 3DConnexion SDKs, Haptic libraries, and so on). My advice would
be to start with a minimalistic VMD build first and see how far you get,
gradually turning things on until you have a complete build. I am happy to
give further guidance in 10 days when I return from vacation.

On Mon, Jul 27, 2015 at 10:22:07PM +0200, Ajasja Ljubeti?? wrote:
> Hi!
> Looking at the configure script of the 1.9.2 source distribution, there is
> already a stub for the WIN64 architecture. Although it has not been
> modified and is set to call g++. The Win32 (starting at line 2882) is set
> to also optionally use the MSVC compiler.
> I have a basic question: Can the optional libraries (such TCL/TK/OpenGL)
> be dynamically linked (it seems that they are in the WIN32 binary
> distribution)? In other words can I just download ActiveTCL or a similar
> distribution instead of compiling TCL from source.¬
> Does FTLK have to be build from source in any case?
> Thanks & all the best,
> Ajasja
> ¬
> On 27 July 2015 at 18:16, Hart, David Blaine <[1]dbhart_at_sandia.gov> wrote:
>
> If someone could provide the build-scripts/harness used for the 32-bit
> builds, I‚**d love to run them with the 64-bit compilers and would be
> willing to pass the executable back, but I don‚**t want to start from
> scratch :-)
> David Hart
> Geochemistry Department
> Sandia National Laboratories
> From: <[2]owner-vmd-l_at_ks.uiuc.edu> on behalf of Sam Wallace
> <[3]adelaide_at_samwallace.net>
> Date: Monday, July 27, 2015 at 2:06 AM
> To: "[4]vmd-l_at_ks.uiuc.edu" <[5]vmd-l_at_ks.uiuc.edu>
> Subject: [EXTERNAL] vmd-l: 64 bit windows VMD
> I know this has been brought up in the past.
>
> I'm wondering if there's been any progress towards a 64 bit version for
> use in Windows?
>
> -Sam
>
> References
>
> Visible links
> 1. mailto:dbhart_at_sandia.gov> 2. mailto:owner-vmd-l_at_ks.uiuc.edu> 3. mailto:adelaide_at_samwallace.net> 4. mailto:vmd-l_at_ks.uiuc.edu> 5. mailto:vmd-l_at_ks.uiuc.edu