OpenVSP 3.2.1 CMake Error on Windows7

[Mike Henson]

I'm attempting to build VSP 3.2.1 on Windows7 for the first time and encountered an error with CMake.  I have installed the dependencies given in the build instructions.

Is the CPPTest code missing from the repo, or am I making an error with CMake?

The CMake echoes are given below...

Thanks

C:\Users\hensomc\Documents\VSP\OpenVSP-1\build>"C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" ..\src

-- Building for: NMake Makefiles

-- The C compiler identification is MSVC

-- The CXX compiler identification is MSVC

-- Check for CL compiler version

-- Check for CL compiler version - 1600

-- Check if this is a free VC compiler

-- Check if this is a free VC compiler - no

-- Check CL platform

-- Check CL platform - 32 bit

-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe

-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe -- works

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - done

-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe

-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe -- works

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

-- Found Doxygen: C:/Program Files/doxygen/bin/doxygen.exe

CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:70 (MESSAGE):

  Could NOT find CPPTest (missing: CPPTEST_INCLUDE_DIRS CPPTEST_LIBRARIES

  CPPTEST_LIBRARY_DIRS)

Call Stack (most recent call first):

  cmake/FindCPPTest.cmake:24 (find_package_handle_standard_args)

  external/CMakeLists.txt:6 (FIND_PACKAGE)

-- Configuring incomplete, errors occurred!

[Rob McDonald]

Mike,

If you followed the extensive *.pdf file of directions, those are very
out of date and only relate to v2.

It is generally easiest to obtain the various dependencies from the
SuperProject, or the Libraries subproject.

It looks like you have jumped right to the VSP subproject.

Did you manually build and install all the dependencies, or did you
build the Libraries subproject?

If you built the Libraries subproject, then you need to point the VSP
subproject to where that is i.e. you need to set a -DVSP_LIBRARY_PATH
when running cmake ../src

Rob

> --
> You received this message because you are subscribed to the Google Groups
> "OpenVSP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to openvsp+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Mike Henson]

Rob - thanks for quick reply.  I'm using the directions posted on your OpenVSP Git Repo.  I also cloned the repo from that same location.

I downloaded and installed: VS 2010 Express C++, CMake 2.8, SWIG, Python, Doxygen

I created a build directory, moved to it and ran cmake.  I've tried using ..\SuperProject, ..\Libraries and ..\src as the argument to cmake, all produce errors.  I'm guessing that I am not using cmake properly.  Do I need to edit the cmakelist.txt files, or define cmake properties?

For example, if I try to build the SuperProject in a VS2010 command prompt shell:

C:\Users\hensomc\Documents\VSP\OpenVSP-1\build>"C:\Program Files (x86)\CMake 2.8\bin\cmake.exe"  ..\SuperProject

-- Building for: NMake Makefiles

-- The C compiler identification is MSVC

-- The CXX compiler identification is MSVC

-- Check for CL compiler version

-- Check for CL compiler version - 1600

-- Check if this is a free VC compiler

-- Check if this is a free VC compiler - no

-- Check CL platform

-- Check CL platform - 32 bit

-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe

-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe -- works

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - done

-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe

-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe -- works

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:710 (message):

  error: no download info for 'Libraries' -- please specify existing

  SOURCE_DIR or one of URL, CVS_REPOSITORY and CVS_MODULE, SVN_REPOSITORY or

  DOWNLOAD_COMMAND

Call Stack (most recent call first):

  C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:941 (_ep_add_download_command)

  CMakeLists.txt:10 (ExternalProject_Add)

CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:710 (message):

  error: no download info for 'OpenVSP' -- please specify existing SOURCE_DIR

  or one of URL, CVS_REPOSITORY and CVS_MODULE, SVN_REPOSITORY or

  DOWNLOAD_COMMAND

Call Stack (most recent call first):

  C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:941 (_ep_add_download_command)

  CMakeLists.txt:32 (ExternalProject_Add)

Once the build files are configured using CMake, is it possible to run the build process from the command line using nmake or other (without having to pre-load the VS IDE)?

Thanks,

Mike

[Rob McDonald]

I don't know Mike.

It looks like the SuperProject is unable to kick off the subprojects
(Libraries and then OpenVSP) It complains that it can't find
SOURCE_DIR, but that is explicitly defined...

https://github.com/ramcdona/OpenVSP/blob/master/SuperProject/CMakeLists.txt

I've only run CMake on Windows through the GUI -- this is dumb, but
you might try running cmake with a ../Libraries instead of a
..\Libraries... It seems like everything else cmake uses /
everywhere.

I believe it will be possible to build via nmake once configured, but
I haven't ever tried it. When I build on Windows, I go through the
MSVC IDE.

Rob

[Mike Henson]

Rob,

Thanks for suggestion.  The CMake gui cleaned things up.  Building the SuperProject in VS2010 - the IDE build process is not picking up the default C++ include files in $(VCInstallDir).  It defaulted to a QT include path that does not exist.  I see references to QT in the CMake files.  Does this sound right?

I reset the Include value to: $(VCInstallDir)include;"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Include", but still not finding files like "math.h, io.h, ..."

Have you encountered this before?

Mike

[Rob McDonald]

There should be no reference to QT in the VSP CMake files. Where do
you see that?

I have never had trouble with MSVC finding standard system libraries.

Rob

[Mike Henson]

Rob,

This turned out to be bad environment variable definitions for INCLUDE_PATH and LD_LIBRARY_PATH on my system.  

I am able to get the SuperProject build started and it makes good progress, but getting build errors with FLTK (screen echoes from MSVC attached).  I assumed this is a 32-bit build?

Thanks for your help on this.

Mike

[Rob McDonald]

Glad you caught that. Sorry this has been so difficult.

I suspect I know the next problem you're hitting -- paths too long for CMake.

Using ExternalProject_add ends up building long path hierarchies.
When we use the SuperBuild, it uses two levels of ExternalProject_add
before it gets to FLTK.

So, you can either try placing your build directory as close to a root
path as possible, or you can build the Libraries separate from
OpenVSP.

Rob

[Mike Henson]

Thanks for the tip regarding long path - I was able to get a successful build.

This is my first experience with CMake and I'm stumbling along.

What IDE(s) are being used by the developers?

I will create a new post with some questions I have regarding scripting with subsurfaces.

Thanks again for your help.

Mike

[Rob McDonald]

Very glad you finally got it all sorted. Sorry it was so difficult.

I do most of my development on Eclipse on MacOS -- but I'm not a huge
fan of Eclipse for C++. J.R. is a big Visual Studio user. I'm always
looking for a better answer.

I seem to recall that completing support for subsurfaces through
scripting is on a TODO list someplace... If it was implemented, you
can bet it never made it to the Wiki.

Rob

[Jim Fenbert]

Rob,

I came across this and thought you might be interested based on your comment here.
It's a C++ ide by JetBRAINS called CLION. I've used their java ide "Intellij" and it's pretty good.
The thing that sounded interesting is that it uses CMAKE as it's build system and seems to have it highly integrated.
Here is a link to a video overview: https://www.youtube.com/watch?v=EUZEPa9GtIo
It's not free but I think you would qualify to get it free:

Jim

[Rob McDonald]

Jim,

I've been watching CLion, but since I'm still on OSX 10.8.5, I haven't been able to try it out personally.

Some of my students are using it, but I don't think they've taken the full plunge -- for example, I don't think they're using CLion to build and therefore don't have all the searching and refactoring possibilities available to them.

I am quite intrigued by what it will mean for the IDE to use CMake natively -- could be really cool.

Rob

--

[Jim Fenbert]

Rob,

The video looked interesting but I'm like JR, too invested in Visual Studio. (Except for JAVA).

...

I thought I would take your recommendation and build the libraries and OpenVSP separately, but didn't get far.

I was able to run cmake and build the libraries but I don't understand how to "point" OpenVSP at the libraries.

I built the libraries in a Testlib folder and the tried to pass that path on the cmake command line:

cmake -DVSP_LIBRARY_PATH:STRING="..\Testlib" ..\src (based on googling CMAKEoptions)

but it didn't work. I've tried several variations but can't seem to get cmake to run on ..\src

I think I'm missing something fundamental about CMAKE.

[Rob McDonald]

> The video looked interesting but I'm like JR, too invested in Visual Studio.
> (Except for JAVA).

Yeah, I've been tempted to update OSX just to try it out, but haven't
had time yet..

Other than being able to search for references, I'm a luddite when it
comes to build tools. My favorite debugger is printf() after all.

> I thought I would take your recommendation and build the libraries and
> OpenVSP separately, but didn't get far.
> I was able to run cmake and build the libraries but I don't understand how
> to "point" OpenVSP at the libraries.
> I built the libraries in a Testlib folder and the tried to pass that path on
> the cmake command line:
> cmake -DVSP_LIBRARY_PATH:STRING="..\Testlib" ..\src (based on googling
> CMAKEoptions)
> but it didn't work. I've tried several variations but can't seem to get
> cmake to run on ..\src
> I think I'm missing something fundamental about CMAKE.

I use CMake command line on Mac/Linux, but only use the GUI on Windows.

On Mac, my CMake command includes this:

-DVSP_LIBRARY_PATH=/full/path/to/libraries

On Windows, I add the variable through the GUI.

Rob

[Jim Fenbert]

Rob,

Thanks. I got it working using the command line. Then I tried it again with the :STRING in the definition and that worked too.
I must have had a typo in the path can just kept pasting that on the command line.
Sorry about that, but it's hard to know what is causing the problems until I get it working once.

Jim

[Rob McDonald]

Glad you got it working.

Patches accepted to make the process smoother and documentation clearer (:

I find that the only way to really get a true Debug or Release build
is to tell CMake when I set up the project. That way, it trickles
down to all the libraries, etc. Otherwise, you get a mix of things,
without the ability to run a debugger, but still slow and bloated...

When I set up a machine to build, I generally have at least two
entirely separate build directories, one for debug, one for release.

Rob

[Huy Dinh]

Hi Mike, 

I'm having some very similar issue with what you described. Could you tell me more about how you fixed that INCLUDE_PATH and LD_LIBRARY_PATH bad environment? That might help my situation (cpptest ... not found)

Thank you