plumo Posted May 5, 2011 Report Share Posted May 5, 2011 (edited) 1>------ Build started: Project: simulation2, Configuration: Debug Win32 ------1> Selection.cpp1>..\..\..\source\simulation2\helpers\Selection.cpp(24): fatal error C1083: Cannot open include file: 'simulation2/components/ICmpIdentity.h': No such file or directory2>------ Build started: Project: test, Configuration: Debug Win32 ------3>------ Build started: Project: pyrogenesis, Configuration: Debug Win32 ------3>C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(990,5): warning MSB8012: TargetPath(C:\Users\Bastijn\ps\build\workspaces\vc2008\../../../binaries/system\pyrogenesis.exe) does not match the Linker's OutputFile property value (C:\Users\Bastijn\ps\binaries\system\pyrogenesis_dbg.exe). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).3>C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(992,5): warning MSB8012: TargetName(pyrogenesis) does not match the Linker's OutputFile property value (pyrogenesis_dbg). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).3>LINK : fatal error LNK1104: cannot open file 'C:\Users\Bastijn\ps\build\workspaces\vc2008\obj\simulation2_Debug\Selection.obj'2>C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(990,5): warning MSB8012: TargetPath(C:\Users\Bastijn\ps\build\workspaces\vc2008\../../../binaries/system\test.exe) does not match the Linker's OutputFile property value (C:\Users\Bastijn\ps\binaries\system\test_dbg.exe). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).2>C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(992,5): warning MSB8012: TargetName(test) does not match the Linker's OutputFile property value (test_dbg). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).2>LINK : fatal error LNK1104: cannot open file 'C:\Users\Bastijn\ps\build\workspaces\vc2008\obj\simulation2_Debug\Selection.obj'========== Build: 0 succeeded, 3 failed, 11 up-to-date, 0 skipped ========== Edited May 5, 2011 by plumo Quote Link to comment Share on other sites More sharing options...
fcxSanya Posted May 5, 2011 Report Share Posted May 5, 2011 1>..\..\..\source\simulation2\helpers\Selection.cpp(24): fatal error C1083: Cannot open include file: 'simulation2/components/ICmpIdentity.h': No such file or directoryAre you tried to run 'svn update' after 'svn checkout' ? Sometime checkout breaks in the middle of process so some files may be missing. Quote Link to comment Share on other sites More sharing options...
janwas Posted May 5, 2011 Report Share Posted May 5, 2011 I'm seeing this as well after a successful update - it looks like Ben just forgot to SVN add the file (an easy omission to make; after all, it works on the local machine ). Hopefully he'll see this thread soon. Quote Link to comment Share on other sites More sharing options...
k776 Posted May 5, 2011 Report Share Posted May 5, 2011 Two files were missing. The issue is known, and will be fixed shortly. By the time you read this, they'll have been committed.Edit: Done! Quote Link to comment Share on other sites More sharing options...
janwas Posted May 5, 2011 Report Share Posted May 5, 2011 Let's not rush things, guys I'm seeing tons of in-game error messages when loading death canyon on Windows with a debug build fresh from SVN. From interestinglog.html:ERROR: JavaScript error: simulation/components/interfaces/Identity.js line 1 Error: Registering interface with already-registered name ()@simulation/components/interfaces/Identity.js:1ERROR: CXeromyces: Parse error: in_memory_buffer:1: Element choice is empty[...]ERROR: RelaxNGValidator: Failed to compile schemaERROR: Can't find component type AIInterfaceERROR: Invalid component id 0[...]ERROR: GUI page 'page_session.xml': Failed to call init() functionERROR: JavaScript error: gui/session/session.js line 73 TypeError: g_Players[Engine.GetPlayerID()] is undefined init([object Object],(void 0))@gui/session/session.js:73 reallyStartGame()@gui/loading/loading.js:99ERROR: JavaScript error: gui/session/session.js line 191 TypeError: simState is undefined checkPlayerState()@gui/session/session.js:191 onTick()@gui/session/session.js:153 __eventhandler91 (tick)([object Object])@sn tick:0There is also an error reported by the self-test:TypeError: global["IID_" + name] is read-only ("Identity")@simulation/components/tests/setup.js:16 ()@simulation/components/interfaces/Identity.js:1 ()@simulation/components/tests/test_UnitAI.js:6Other self-test issues (mostly related to mixing path separators) are fixed by the attached patch, which I'd rather not commit until the other things are sorted out.fix_test_and_refactor_status.patch Quote Link to comment Share on other sites More sharing options...
Ykkrosh Posted May 6, 2011 Report Share Posted May 6, 2011 simulation/components/interfaces/Identity.js doesn't exist (since r9443), so you've probably got an inconsistent SVN state if it's complaining about that. (That will lead to all the other errors - at some point in the future we should probably be better about aborting the game load on fatal errors instead of carrying on blindly and exploding.)The "global["IID_" + name] is read-only" test failure is caused by the SpiderMonkey binary on Windows being slightly out of date; it'd be nice to recompile some time but the bug is harmless in practice (and I can't recompile myself since I currently have no working Windows hardware). Quote Link to comment Share on other sites More sharing options...
janwas Posted May 6, 2011 Report Share Posted May 6, 2011 Ah, thanks for looking into this. I did double-check everything was up to date, as reported by SVN.Looks like the SVN state was indeed garbled, since it now works after a full checkout.The previously mentioned Windows fixes are now in. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.