<sadowsky.o.phd@gmail.com> writes:
> I obtained the SVN version of the ImageVis3D source according to the
> instructions on your web site, and I am trying to build it.
>
> My work environment is Windows 7/x64 with a Visual Studio 8 (that's
> what I got).  Th Solution/Project files included in the SVN are

> incompatible with VS 8, so I can't open them.

You cannot use VS8.  You must use VS 2008 *with* the feature pack
installed.  2010 support is on our todo list.

2008 express should be fine, as long as the feature pack is installed.
2010 will work 'out of the box' once we get around to it.

> I therefore installed the Qt SDK 4.7 on the system.  This is NOT the
> Qt source, but I figured I shouldn't have to go that far in order to
> build ImageVis3D.

You do have to go that far.  We have some guesses how to get it going
otherwise, but we say we don't support the SDK because it's a very
different Qt configuration and, well, we can't support everything.

> I open the Qt Command Prompt and run qmake.  I get a bunch of
> messages, some of them similar to the following.
>
> ***
> WARNING: Unable to generate output for:
> E:/ImageVis3D/ExtractDebugInfo/Makefile.Debug [TEMPLATE vcapp]
> ***
>
> It doesn't appear as though the build was completed.  I afterwards
> run nmake / gmake, and get error message such as:

qmake does not build the software, only the makefiles.  So, yes, the
build is not completed, but it hasn't been attempted either ;)

ExtractDebugInfo is worthless for a user anyway; you might consider
just removing it from the toplevel .pro.

> ***
> cd Tuvok\ && gmake -f Makefile
> gmake[1]: Entering directory `E:/ImageVis3D/Tuvok'
> gmake -f Makefile.Debug
> gmake[2]: Entering directory `E:/ImageVis3D/Tuvok'
> gmake[2]: Makefile.Debug: No such file or directory
> gmake[2]: *** No rule to make target `Makefile.Debug'.        Stop.
> gmake[2]: Leaving directory `E:/ImageVis3D/Tuvok'
> gmake[1]: *** [debug] Error 2
> gmake[1]: Leaving directory `E:/ImageVis3D/Tuvok'
> gmake: *** [sub-Tuvok-make_default-ordered] Error 2
> ***
>
> Essentially, the build fails in this environment.  Could you explain
> why?  If the Qt source version is needed, then also please explain
> why.

The SDK installs the libraries with different names.  This is basically
impossible to support in a solution file, because if you use 'name1',
it'll fail with static linking, and if you use 'name2' it'll fail when
someone has a dynamic Qt.  We standardized on static linking, at least
on windows.

Secondly, qmake is broken on windows.  See bug 452 in their BTS.  We
had a plethora of issues getting the qmake-generated makefiles to even
build 10-line Qt programs on that platform at first.  I fixed those
maybe 6 months back by fiddling with our .pro's considerably, but 452
is still a blocker for us.  Hence building through any other method
than via the solution files is unsupported.

That said, I would appreciate you reporting to this list how you got it
working if you do so via a different path.

Also, if you fix Qt's 452 I'll gladly jump in and make sure qmake-based
building works on Windows; it's something I want for the regression
testing system anyway.

-tom