seems to work fine I resolved my cmake error by identifying some linux specific includes which windows did not know what to do with (things relating to CPACK). This however did not resolve the errors I got when I tried to build, answering my question as to whether the two were related. The problem when I was building is that QT is not properly set up to build on this system (the environmental variables for libraries ect. were not set). This had not been a problem before building on this machine as previously using qmake it had used the microsoft visual compiler. So to resolve my error I ran my cmake manually outside of QT then opened the solution file in Visual C++.
I hope this helps . A web search for "return code 0xc0000135" turned up the information that this means nmake cannot find the compiler. Which means that you did not start nmake in a Visual Studio command shell. If you want to use a standard command shell you have to call vcvarsall.bat or similar in the VC directory of you Visual Studio installation. If it still does not work, check the INCLUDE and LIB environment variables. They should contain ...\VC\INCLUDE and %ProgramFiles%\Microsoft SDKs\Windows\v6.0A\include and the corresponding LIB dirs.
this will help The headers boost/test/unit_test.hpp and boost/test/included/unit_test.hpp contains same functionality but for different use: boost/test/unit_test.hpp only declares the functions which are defined in the library file, boost/test/included/unit_test.hpp defines the functions, thus including the library file is not needed.
To fix this issue This exact error has been discussed in this thread in the Qt forum. It links to an unofficial patch which can be found here. For future reference, the contents of the patch are listed below:
may help you . The problem has nothing to do with long filenames. @Sebastian does not have ias installed. He should not be using ias in any case. You need nasm if you want OpenSSL to take advantage of assembly language optimizations.