windows compilation failed

Discussion and help for Compilation problems and platform portability.

Moderator: coordinators

Re: windows compilation failed

Postby rendermagic » Thu Apr 05, 2012 4:29 pm

So, I did a grep on the directory, and everything looks in order:

Code: Select all
./deps/x64/boost_1_43_0/libs/filesystem/test/msvc/common.vsprops:       Version="8.00"
./deps/x64/boost_1_43_0/libs/system/test/system_msvc/common.vsprops:    Version="8.00"
./deps/x64/Python-2.7.1/PC/VS8.0/debug.vsprops: Version="8.00"
./deps/x64/Python-2.7.1/PC/VS8.0/pginstrument.vsprops:  Version="8.00"
./deps/x64/Python-2.7.1/PC/VS8.0/pgupdate.vsprops:      Version="8.00"
./deps/x64/Python-2.7.1/PC/VS8.0/pyd.vsprops:   Version="8.00"
./deps/x64/Python-2.7.1/PC/VS8.0/pyd_d.vsprops: Version="8.00"
./deps/x64/Python-2.7.1/PC/VS8.0/pyproject.vsprops:     Version="8.00"
./deps/x64/Python-2.7.1/PC/VS8.0/release.vsprops:       Version="8.00"
./deps/x64/Python-2.7.1/PC/VS8.0/sqlite3.vsprops:       Version="8.00"
./deps/x64/Python-2.7.1/PC/VS8.0/x64.vsprops:   Version="8.00"
./deps/x64/Python-2.7.1/PCbuild/debug.vsprops:  Version="8.00"
./deps/x64/Python-2.7.1/PCbuild/pginstrument.vsprops:   Version="8.00"
./deps/x64/Python-2.7.1/PCbuild/pgupdate.vsprops:       Version="8.00"
./deps/x64/Python-2.7.1/PCbuild/pyd.vsprops:    Version="8.00"
./deps/x64/Python-2.7.1/PCbuild/pyd_d.vsprops:  Version="8.00"
./deps/x64/Python-2.7.1/PCbuild/pyproject.vsprops:      Version="8.00"
./deps/x64/Python-2.7.1/PCbuild/release.vsprops:        Version="8.00"
./deps/x64/Python-2.7.1/PCbuild/sqlite3.vsprops:        Version="8.00"
./deps/x64/Python-2.7.1/PCbuild/x64.vsprops:    Version="8.00"
./deps/x64/Python-3.2/PC/VS8.0/debug.vsprops:   Version="8.00"
./deps/x64/Python-3.2/PC/VS8.0/pginstrument.vsprops:    Version="8.00"
./deps/x64/Python-3.2/PC/VS8.0/pgupdate.vsprops:        Version="8.00"
./deps/x64/Python-3.2/PC/VS8.0/pyd.vsprops:     Version="8.00"
./deps/x64/Python-3.2/PC/VS8.0/pyd_d.vsprops:   Version="8.00"
./deps/x64/Python-3.2/PC/VS8.0/pyproject.vsprops:       Version="8.00"
./deps/x64/Python-3.2/PC/VS8.0/release.vsprops: Version="8.00"
./deps/x64/Python-3.2/PC/VS8.0/sqlite3.vsprops: Version="8.00"
./deps/x64/Python-3.2/PC/VS8.0/x64.vsprops:     Version="8.00"
./deps/x64/Python-3.2/PCbuild/debug.vsprops:    Version="8.00"
./deps/x64/Python-3.2/PCbuild/pginstrument.vsprops:     Version="8.00"
./deps/x64/Python-3.2/PCbuild/pgupdate.vsprops: Version="8.00"
./deps/x64/Python-3.2/PCbuild/pyd.vsprops:      Version="8.00"
./deps/x64/Python-3.2/PCbuild/pyd_d.vsprops:    Version="8.00"
./deps/x64/Python-3.2/PCbuild/pyproject.vsprops:        Version="8.00"
./deps/x64/Python-3.2/PCbuild/release.vsprops:  Version="8.00"
./deps/x64/Python-3.2/PCbuild/sqlite3.vsprops:  Version="8.00"
./deps/x64/Python-3.2/PCbuild/x64.vsprops:      Version="8.00"
./deps/x86/boost_1_43_0/libs/filesystem/test/msvc/common.vsprops:       Version="8.00"
./deps/x86/boost_1_43_0/libs/system/test/system_msvc/common.vsprops:    Version="8.00"
./deps/x86/Python-2.7.1/PC/VS8.0/debug.vsprops: Version="8.00"
./deps/x86/Python-2.7.1/PC/VS8.0/pginstrument.vsprops:  Version="8.00"
./deps/x86/Python-2.7.1/PC/VS8.0/pgupdate.vsprops:      Version="8.00"
./deps/x86/Python-2.7.1/PC/VS8.0/pyd.vsprops:   Version="8.00"
./deps/x86/Python-2.7.1/PC/VS8.0/pyd_d.vsprops: Version="8.00"
./deps/x86/Python-2.7.1/PC/VS8.0/pyproject.vsprops:     Version="8.00"
./deps/x86/Python-2.7.1/PC/VS8.0/release.vsprops:       Version="8.00"
./deps/x86/Python-2.7.1/PC/VS8.0/sqlite3.vsprops:       Version="8.00"
./deps/x86/Python-2.7.1/PC/VS8.0/x64.vsprops:   Version="8.00"
./deps/x86/Python-2.7.1/PCbuild/debug.vsprops:  Version="8.00"
./deps/x86/Python-2.7.1/PCbuild/pginstrument.vsprops:   Version="8.00"
./deps/x86/Python-2.7.1/PCbuild/pgupdate.vsprops:       Version="8.00"
./deps/x86/Python-2.7.1/PCbuild/pyd.vsprops:    Version="8.00"
./deps/x86/Python-2.7.1/PCbuild/pyd_d.vsprops:  Version="8.00"
./deps/x86/Python-2.7.1/PCbuild/pyproject.vsprops:      Version="8.00"
./deps/x86/Python-2.7.1/PCbuild/release.vsprops:        Version="8.00"
./deps/x86/Python-2.7.1/PCbuild/sqlite3.vsprops:        Version="8.00"
./deps/x86/Python-2.7.1/PCbuild/x64.vsprops:    Version="8.00"
./deps/x86/Python-3.2/PC/VS8.0/debug.vsprops:   Version="8.00"
./deps/x86/Python-3.2/PC/VS8.0/pginstrument.vsprops:    Version="8.00"
./deps/x86/Python-3.2/PC/VS8.0/pgupdate.vsprops:        Version="8.00"
./deps/x86/Python-3.2/PC/VS8.0/pyd.vsprops:     Version="8.00"
./deps/x86/Python-3.2/PC/VS8.0/pyd_d.vsprops:   Version="8.00"
./deps/x86/Python-3.2/PC/VS8.0/pyproject.vsprops:       Version="8.00"
./deps/x86/Python-3.2/PC/VS8.0/release.vsprops: Version="8.00"
./deps/x86/Python-3.2/PC/VS8.0/sqlite3.vsprops: Version="8.00"
./deps/x86/Python-3.2/PC/VS8.0/x64.vsprops:     Version="8.00"
./deps/x86/Python-3.2/PCbuild/debug.vsprops:    Version="8.00"
./deps/x86/Python-3.2/PCbuild/pginstrument.vsprops:     Version="8.00"
./deps/x86/Python-3.2/PCbuild/pgupdate.vsprops: Version="8.00"
./deps/x86/Python-3.2/PCbuild/pyd.vsprops:      Version="8.00"
./deps/x86/Python-3.2/PCbuild/pyd_d.vsprops:    Version="8.00"
./deps/x86/Python-3.2/PCbuild/pyproject.vsprops:        Version="8.00"
./deps/x86/Python-3.2/PCbuild/release.vsprops:  Version="8.00"
./deps/x86/Python-3.2/PCbuild/sqlite3.vsprops:  Version="8.00"
./deps/x86/Python-3.2/PCbuild/x64.vsprops:      Version="8.00"
./windows/Projects/properties/32bit-Debug.vsprops:      Version="8.00"
./windows/Projects/properties/32bit-Debug.vsprops:      OutputDirectory="$(PlatformName)\$(SSE_Version)\$(ConfigurationName)"
./windows/Projects/properties/32bit-Debug.vsprops:      IntermediateDirectory="BuildTemp\$(ProjectName)\$(SSE_Version)\$(ConfigurationName)"
./windows/Projects/properties/32bit-Debug.vsprops:              Name="SSE_Version"
./windows/Projects/properties/32bit-Release.vsprops:    Version="8.00"
./windows/Projects/properties/32bit-Release.vsprops:    OutputDirectory="$(PlatformName)\$(SSE_Version)\$(ConfigurationName)"
./windows/Projects/properties/32bit-Release.vsprops:    IntermediateDirectory="BuildTemp\$(ProjectName)\$(SSE_Version)\$(ConfigurationName)"
./windows/Projects/properties/32bit-Release.vsprops:            Name="SSE_Version"
./windows/Projects/properties/32bit-Variables.vsprops:  Version="8.00"
./windows/Projects/properties/32bit-Variables.vsprops:          Value="$(ProjectDir)\..\luxrays\$(PlatformName)\$(SSE_Version)\$(ConfigurationName)"
./windows/Projects/properties/64bit-Debug.vsprops:      Version="8.00"
./windows/Projects/properties/64bit-Release.vsprops:    Version="8.00"
./windows/Projects/properties/64bit-Variables.vsprops:  Version="8.00"
./windows/Projects/properties/LibLuxUser.vsprops:       Version="8.00"
./windows/Projects/properties/LuxConsoleApp.vsprops:    Version="8.00"
./windows/Projects/properties/LuxCoreProperties.vsprops:        Version="8.00"
./windows/Projects/properties/LuxRaysProperties.vsprops:        Version="8.00"
./windows/Projects/properties/LuxRaysUser.vsprops:      Version="8.00"
./windows/Projects/properties/NoOpenCL.vsprops: Version="8.00"
./windows/Projects/properties/Python2.vsprops:  Version="8.00"
./windows/Projects/properties/Python3.vsprops:  Version="8.00"
./windows/Projects/properties/QtGUI.vsprops:    Version="8.00"
./windows/Projects/properties/SSE1.vsprops:     Version="8.00"
./windows/Projects/properties/SSE1.vsprops:             Name="SSE_Version"
./windows/Projects/properties/SSE2.vsprops:     Version="8.00"
./windows/Projects/properties/SSE2.vsprops:             Name="SSE_Version"
./windows/support/LuxFreeImage.vsprops: Version="8.00"


I've temporarily resorted to using VS2008 Express, but it seems the Express version doesn't break on uncaught exceptions, which seems to happen a lot.

Code: Select all
First-chance exception at 0x76d3fc56 in luxconsole.exe: Microsoft C++ exception: boost::exception_detail::clone_impl<boost::exception_detail::bad_alloc_> at memory location 0x0012fea8..
First-chance exception at 0x76d3fc56 in luxconsole.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000..
Render Magic
----------------
i7 950 - Not OC'd
24G DDR3 RAM
2 GTX 580s
rendermagic
Developer
 
Posts: 141
Joined: Wed Mar 23, 2011 2:32 pm
Location: Leading edge of a photon (California USA)

Re: windows compilation failed

Postby zsolnai » Fri Apr 06, 2012 8:52 am

Hi there everyone,

some (mostly CMake-related) issues I have encountered:

Code: Select all
1>------ Build started: Project: luxShared, Configuration: Release Win32 ------
1>Compiling...
1>cl : Command line warning D9002 : ignoring unknown option '/favor:blend'
1>cl : Command line warning D9002 : ignoring unknown option '/favor:blend'
1>cl : Command line warning D9002 : ignoring unknown option '/favor:blend'
1>cl : Command line warning D9002 : ignoring unknown option '/favor:blend'

and

Code: Select all
1>------ Build started: Project: luxShared, Configuration: Release Win32 ------
1>Compiling...
1>cl : Command line error D8021 : invalid numeric argument '/MP;'


In the C/C++ command line window in VS2k8, you can see these at the end: /Zm1000 /Oy- /Zc:forScope /favor:blend /Qfast_transcendentals /MP";"

The last 3 characters (";") have to be removed in order to make the build compile, and it also appears in every subproject. I have no idea about what /favor:blend is though, nor does the compiler, but thankfully you can get away with a warning. :)

I am using:
d:\util\cmake\bin>cmake --version
cmake version 2.8.7

+ LuxRender Win32 NoOpenCL

Also a strange crash screenshot is attached below (my OS lang is .hu, but you're expected to be familiar with the sight of the window). I haven't seen cl.exe crash a lot before. :)
Yesterday's build was fine (04.05), this window is from today's (04.06), the CMake issues appeared in every version.
Attachments
crash.png
zsolnai
Developer
 
Posts: 239
Joined: Sun May 22, 2011 6:17 pm

Re: windows compilation failed

Postby rendermagic » Fri Apr 06, 2012 4:53 pm

If anyone is curious about the boost exceptions, the solution can be found here:
https://svn.boost.org/trac/boost/changeset/61938. The Boost ticket was https://svn.boost.org/trac/boost/ticket/4210.
Render Magic
----------------
i7 950 - Not OC'd
24G DDR3 RAM
2 GTX 580s
rendermagic
Developer
 
Posts: 141
Joined: Wed Mar 23, 2011 2:32 pm
Location: Leading edge of a photon (California USA)

Re: windows compilation failed

Postby Chawl » Wed May 16, 2012 11:38 am

Here is what d9350524e62c says to me on VS2008 SP1 W7 64bit.

Code: Select all
1>renderfarm.cpp
1>C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\include\utility(49) : error C2512: 'lux::RenderFarm::CompiledFile::CompiledFile' : no appropriate default constructor available
1>        C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\include\utility(48) : while compiling class template member function 'std::pair<_Ty1,_Ty2>::pair(void)'
1>        with
1>        [
1>            _Ty1=std::string,
1>            _Ty2=lux::RenderFarm::CompiledFile
1>        ]
1>        ..\..\..\lux\core\renderfarm.cpp(313) : see reference to class template instantiation 'std::pair<_Ty1,_Ty2>' being compiled
1>        with
1>        [
1>            _Ty1=std::string,
1>            _Ty2=lux::RenderFarm::CompiledFile
1>        ]
Chawl
 
Posts: 71
Joined: Fri May 14, 2010 7:52 pm
Location: Ankara, Turkey

Re: windows compilation failed

Postby Lord Crc » Wed May 16, 2012 4:31 pm

Chawl wrote:Here is what d9350524e62c says to me on VS2008 SP1 W7 64bit.


Tip builds just fine here, can you force a rebuild?
May contain traces of nuts.
User avatar
Lord Crc
Developer
 
Posts: 4455
Joined: Sat Nov 17, 2007 2:10 pm

Re: windows compilation failed

Postby Chawl » Thu May 17, 2012 6:10 pm

Lord Crc wrote:
Chawl wrote:Here is what d9350524e62c says to me on VS2008 SP1 W7 64bit.


Tip builds just fine here, can you force a rebuild?


No way, I've got the same error for your (29da2b1979f3) and newest tip (40dcf0043c86).

In fact, last buildable changeset is (27f432d63f66) in my case. All newer ones give the same error.
Chawl
 
Posts: 71
Joined: Fri May 14, 2010 7:52 pm
Location: Ankara, Turkey

Re: windows compilation failed

Postby Lord Crc » Fri May 18, 2012 1:37 am

Chawl wrote:No way, I've got the same error for your (29da2b1979f3) and newest tip (40dcf0043c86).

In fact, last buildable changeset is (27f432d63f66) in my case. All newer ones give the same error.


Weird, I'm building on VS2008 SP1 and I see no such error... yay for consistency :)

Anyway, seems you're not alone.

edit: I've pushed a fix, I hope... can you try it?
May contain traces of nuts.
User avatar
Lord Crc
Developer
 
Posts: 4455
Joined: Sat Nov 17, 2007 2:10 pm

Re: windows compilation failed

Postby Chawl » Fri May 18, 2012 4:33 am

Lord Crc wrote:
Chawl wrote:No way, I've got the same error for your (29da2b1979f3) and newest tip (40dcf0043c86).

In fact, last buildable changeset is (27f432d63f66) in my case. All newer ones give the same error.


Weird, I'm building on VS2008 SP1 and I see no such error... yay for consistency :)

Anyway, seems you're not alone.

edit: I've pushed a fix, I hope... can you try it?

Now the tip (5d471697a05b) is built successfully, thanks :)

But I noted two performance warnings.

Code: Select all
..\..\..\lux\integrators\bidirectional.cpp(1186) : warning C4800: 'u_int' : forcing value to bool 'true' or 'false' (performance warning)

Code: Select all
8>..\..\..\lux\cpp_api\lux_api.cpp(104) : warning C4800: 'int' : forcing value to bool 'true' or 'false' (performance warning)
Chawl
 
Posts: 71
Joined: Fri May 14, 2010 7:52 pm
Location: Ankara, Turkey

Re: windows compilation failed

Postby Lord Crc » Fri May 18, 2012 5:00 am

Chawl wrote:Now the tip (5d471697a05b) is built successfully, thanks :)

But I noted two performance warnings.


Great :) Weird that it worked without problems for both me and Omniflux... do you have SP1 installed for VS2008?

The perf warnings can be ignored, they're not important.
May contain traces of nuts.
User avatar
Lord Crc
Developer
 
Posts: 4455
Joined: Sat Nov 17, 2007 2:10 pm

Re: windows compilation failed

Postby Chawl » Fri May 18, 2012 7:34 am

Lord Crc wrote:
Chawl wrote:Now the tip (5d471697a05b) is built successfully, thanks :)

But I noted two performance warnings.


Great :) Weird that it worked without problems for both me and Omniflux... do you have SP1 installed for VS2008?

The perf warnings can be ignored, they're not important.


Yes, SP1 is installed. Here is my detailed environment info. May be some update updated the semantics :P
Attachments
info.txt
VS info
(2.87 KiB) Downloaded 14 times
Chawl
 
Posts: 71
Joined: Fri May 14, 2010 7:52 pm
Location: Ankara, Turkey

PreviousNext

Return to Compilation & Portability

Who is online

Users browsing this forum: No registered users and 0 guests