View Issue Details

IDProjectCategoryView StatusLast Update
0004132Slicer4Core: Building (CMake, Superbuild)public2016-01-26 16:29
Reportermwpowellhtx Assigned Tojcfr  
PriorityhighSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
PlatformWindowsOSWindows 7 x64OS VersionSP1
Product VersionSlicer 4.5.0-1 
Target VersionFixed in VersionSlicer 4.6.0 
Summary0004132: Add support for VS2013
Description

At least; VS2012 is a bare minimum, IMO. VS2010 is a distant memory, and VS2008 is ancient. VS2013 is contemporary, and VS2015 is the current version.

Steps To Reproduce

Will be trying VS2012 build at a minimum. May try VS2013 as well since I work in that most frequently.

TagsNo tags attached.

Activities

jcfr

jcfr

2016-01-21 18:06

administrator   ~0013729

Hi mwpowellhtx,

Thanks for your report.

VS2013 should work. We are also talking about transitioning to VS2013 as the official way. This will be discussed on the developer list.

In the mean time, let us know if you have any problem.

Thanks
Jc

mwpowellhtx

mwpowellhtx

2016-01-22 06:40

reporter   ~0013732

Last edited: 2016-01-22 06:46

View 2 revisions

That was fast. Following the instructions, I installed the latest CMake, I built Qt from the easy build, although I'm not sure whether that included SSL. Do I still need Windows SDK and such?

Edit: because I have VS2015 installed as well, if I accept defaults and build with just "cmake", it defaults to:

$ cmake ./
-- Building for: Visual Studio 14 2015
-- The C compiler identification is MSVC 19.0.23026.0
-- The CXX compiler identification is MSVC 19.0.23026.0
-- Check for working C compiler using: Visual Studio 14 2015
-- Check for working C compiler using: Visual Studio 14 2015 -- works
...

Is there a way to "force" the compiler to use?

mwpowellhtx

mwpowellhtx

2016-01-22 07:09

reporter   ~0013733

Concerning Git interoperability, I must (re-)install Git for Windows with command line integration? I have it installed, but consciously decided to forego that part in favor of Bash only. But for this I expect that I need to run from a Visual Studio Command Prompt for all to go well? Thank you...

mwpowellhtx

mwpowellhtx

2016-01-22 08:10

reporter   ~0013734

Making progress, I think, but it is slow.

I added qmake.exe to a temporary path for purposes of the build. Now I am finding the following errors.

-- Could NOT find Qt4 (missing: QT_MOC_EXECUTABLE QT_RCC_EXECUTABLE QT_UIC_EXECUTABLE) (found version "4.8.7")
CMake Error at CMake/SlicerBlockFindQtAndCheckVersion.cmake:29 (message):
error: Qt 4.7.4 was not found on your system.You probably need to set the QT_QMAKE_EXECUTABLE variable.

Is 4.7.4 a hard requirement? Why wouldn't the "latest" work? As built from the indicated resource, 4.8.7 is the most recent Qt4.

Suggestions?

mwpowellhtx

mwpowellhtx

2016-01-22 08:37

reporter   ~0013735

As far as I know, so far so good. Not building for X11, QWS, or MAC, so I wouldn't expect those.

-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - not found
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - found
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - not found

We do expect OpenGL to be present, AFAIK, so okay there as well:

-- Found OpenGL: opengl32

However this is a problem:

-- Could NOT find Qt4 (missing: QT_MOC_EXECUTABLE QT_RCC_EXECUTABLE QT_UIC_EXECUTABLE) (found version "4.8.7")
CMake Error at CMake/SlicerBlockFindQtAndCheckVersion.cmake:29 (message):
error: Qt 4.7.4 was not found on your system.You probably need to set the QT_QMAKE_EXECUTABLE variable.

How do I identify QT_MOC_EXECUTABLE? QT_RCC_EXECUTABLE? QT_UIC_EXECUTABLE?

mwpowellhtx

mwpowellhtx

2016-01-22 08:51

reporter   ~0013736

There may be CMAKE wrinkles that I need to work out here, I don't know. However, I wonder if the simple answer is the obvious one: that I really need Qt 4.7.4? The latest build helper, though, is building from 4.8.7. I've asked for suggestions on how to signal the expected Qt version for build though.

Issue History

Date Modified Username Field Change
2016-01-21 18:02 mwpowellhtx New Issue
2016-01-21 18:02 mwpowellhtx Status new => assigned
2016-01-21 18:02 mwpowellhtx Assigned To => jcfr
2016-01-21 18:06 jcfr Note Added: 0013729
2016-01-21 18:06 jcfr Status assigned => resolved
2016-01-21 18:06 jcfr Fixed in Version => Slicer 4.6.0
2016-01-21 18:06 jcfr Resolution open => fixed
2016-01-22 06:40 mwpowellhtx Note Added: 0013732
2016-01-22 06:46 mwpowellhtx Note Edited: 0013732 View Revisions
2016-01-22 07:09 mwpowellhtx Note Added: 0013733
2016-01-22 08:10 mwpowellhtx Note Added: 0013734
2016-01-22 08:37 mwpowellhtx Note Added: 0013735
2016-01-22 08:51 mwpowellhtx Note Added: 0013736
2016-01-26 16:29 jcfr Status resolved => closed