Programming & Scripting

View unanswered posts | View active topics


Post a new topicPost a reply
Previous topic | Next topic 

  Beginner BeginnerMember since: 28.11.2010, 14:18Posts: 39 Likes: 0
 

 Post Topic: Re: Common compiler errors
PostPosted 16.09.2011, 19:22 
I use vs2008 express, i followed every step in the forum or in the documentation, but when i load the project, it loads CryAction and GameDLL but not CryCommon and Game? I try many things but i cant load it. I load CE2 with 2008Vs easy.

Sorry for bad english.

  Trainee TraineeMember since: 02.07.2011, 05:10Posts: 127 Likes: 0
 

 Post Topic: Re: Common compiler errors
PostPosted 17.09.2011, 04:14 
Quote by PYDevelopment:
For the last month, I been trying to compile CryEngine with VS 2010 Express and not having a whole lot of success with VS2010 Express. I reverted back to VS2008 Express, even though I kept VS2010 Express on my machine. CryEngine works far better with VS2008 Express, especially when it works without me banging my head against the wall.

I recommend you to just search google for 'VS 2008 express' and you can download it from Microsoft's site. If you follow the topic's creator instructions at the top and CryDev's Get started, you will enjoy this game engine as you should.


Ya but the only thing is I don't want to download a free version of 2008 when I have the professional version. It should work either way. That would be reinventing the wheel in a way as well as taking up useless space on my HDD.
  Beginner BeginnerMember since: 31.08.2011, 13:36Posts: 55Location: Italy Likes: 0
 

 Post Topic: Re: Common compiler errors
PostPosted 21.09.2011, 13:47 
Hi everyone,

I'm having a problem compiling the Debug x64 config-platform in Visual Studio 2010, I always get this error:

Code:
1>LINK : error LNK2001: unresolved external symbol _DllMainCRTStartup
1>F:\CryEngine3\SDK\Code\Solutions\..\..\Bin64\CryAction.dll : fatal error LNK1120: 1 unresolved externals
1>
1>Build FAILED.


The Debug Win32 compiles just fine, now I really don't know what's going on with x64 build.

Also, AFTER the above compilation error, when I then try to start Editor from bin64, I get these errors:

Image

Image

Then it let me insert my account info but as soon as I try to login, the editor crashes with this:

Code:
Call Stack Trace:
43) function=0x0000000028947928
42) function=0x000000003702FF3E
41) function=0x000000003708C34C
40) function=0x00000000370860CB
39) function=0x000000003708E4A7
38) function=0x000000003708E8D9
37) function=0x000000006C69781B
36) function=0x0000000037093FF0
35) function=0x0000000037074A30
34) function=0x0000000037075BCA
33) function=0x0000000037047327
32) function=0x000000006C44CA41
31) function=0x00000000370507A5
30) function=0x000000006C4454CA
29) function=0x0000000063A5A280
28) function=0x000000006C444F1C
27) function=0x000000006C4430EC
26) function=0x000000006C443499
25) function=0x000000006C440447
24) function=0x0000000076DD8971
23) function=0x0000000076DD72CB
22) function=0x0000000076DD0795
21) function=0x0000000077061225
20) function=0x0000000076DD041A
19) function=0x0000000076DD0397
18) function=0x0000000076DD05D8
17) function=0x0000000076DCA350
16) function=0x000000006C44B824
15) function=0x000000006C443C5F
14) function=0x000000006C44C89C
13) function=0x000000006C44CC54
12) function=0x0000000063A5A5E8
11) function=0x00000000370438D4
10) function=0x000000006C487349
9) function=0x000000006C48778E
8) function=0x000000006C48AB71
7) function=0x000000006C4A1C6B
6) function=0x0000000037022B82
5) function=0x000000006C454E42
4) function=0x000000003776C7C7
3) function=0x0000000076CB652D
2) function=0x000000007703C521
1) function=0x000000007703C521


The only way I can solve this and run again the Editor from bin64, is re-extract the bin64 folder from the fresh FreeSDK package.

I'd really appreciate if you could help me out.
Thanks in advance!


P.S. During these days I did format my pc, and before format I was able to compile Debug x64 just fine, aswell as Debug Win32, but now I have the above problem. I have successfully installed Visual Studio and Windows SDK 7.1, and all the DirectX and VC++ redist packages.
  Trainee TraineeMember since: 13.10.2011, 00:35Posts: 140 Likes: 1
 

 Post Topic: Re: Common compiler errors
PostPosted 13.10.2011, 00:59 
to be continued...


Last edited by wurstburst on 13.10.2011, 02:10, edited 1 time in total.
  Trainee TraineeMember since: 13.10.2011, 00:35Posts: 140 Likes: 1
 

 Post Topic: Re: Common compiler errors
PostPosted 13.10.2011, 01:03 
Quote by xPreatorianx1:
Can someone provide the correct vcxproj please?

Or could someone tell me how to make a solution for Visual Studio 2010 (full edition)? I love college :D.

EDIT: I have around 100 different errors all labeled something similar to this :
Code:
11   IntelliSense: cannot open source file "INetwork.h"   c:\users\prea\downloads\cryengine_v3_3_5_2456_freesdk\cryengine\cryaction\igameobjectsystem.h   10   1   CryAction


So ya I must be doing something wrong :S.


Make sure the CryAction.dll is actually present in the Bin32 and Bin64 folders...
  Trainee TraineeMember since: 13.10.2011, 00:35Posts: 140 Likes: 1
 

 Post Topic: Re: Common compiler errors
PostPosted 13.10.2011, 01:08 
Quote by Dekkerlion:
When I try to build I still get the error with shared_ptr.I have the path <CryEngine 3>\Code\SDKs\boost\boost\ and I have also tried with <CryEngine 3>\Code\SDKs\boost\ and <CryEngine 3>\Code\SDKs\boost\boost\smart_ptr also.I am using Visual Studio 2010 SP1 X64


By "<CryEngine 3>" he meant the actual path to your CryEngine SDK folder...
  Trainee TraineeMember since: 13.10.2011, 00:35Posts: 140 Likes: 1
 

 Post Topic: Re: Common compiler errors
PostPosted 13.10.2011, 01:10 
Quote by PYDevelopment:
For the last month, I been trying to compile CryEngine with VS 2010 Express and not having a whole lot of success with VS2010 Express. I reverted back to VS2008 Express, even though I kept VS2010 Express on my machine. CryEngine works far better with VS2008 Express, especially when it works without me banging my head against the wall.

I recommend you to just search google for 'VS 2008 express' and you can download it from Microsoft's site. If you follow the topic's creator instructions at the top and CryDev's Get started, you will enjoy this game engine as you should.


CryEngine SDK can be compiled on VS2010. It just took me roughly 10 minutes to convert then fix and compile it for Win32 and x64...
  Trainee TraineeMember since: 13.10.2011, 00:35Posts: 140 Likes: 1
 

 Post Topic: Re: Common compiler errors
PostPosted 13.10.2011, 01:28 
In this post http://www.crydev.net/viewtopic.php?f=314&t=73189&start=15 someone posted this linker warning message.

Code:
warning MSB8012: TargetName (GameDll) does not match the properties of output file (CryGame) to Linker . This can lead to improper construction of the project. To fix this, make sure the property values ​​of $ (OutDir), $ (TargetName) and $ (TargetExt) correspond to the value specified in% (Link.OutputFile).


Even though it's just a warning it's not good and needs fixing. To point you into the right direction for VS2010 users. Have a look at the Property Manager and the proprty pages for the compile configuration. In the "Target Name" field exchange "$(ProjectName)" with "CryGame"...
  Beginner BeginnerMember since: 31.08.2011, 13:36Posts: 55Location: Italy Likes: 0
 

 Post Topic: Re: Common compiler errors
PostPosted 17.10.2011, 18:52 
I just wanted to pop up that previous issue is fixed on Free SDK new release, I compile and debug the 64bit version just fine.
  Trainee TraineeMember since: 13.10.2011, 00:35Posts: 140 Likes: 1
 

 Post Topic: Re: Common compiler errors
PostPosted 17.10.2011, 21:12 
The linker warning....

Code:
MSB8012: TargetPath(blah1) does not match the Linker's OutputFile property value (blah2). This may cause your project to build incorrectly. To correct this....


still exist in the 2572 build. See my suggestion above to fix it...
  Beginner BeginnerMember since: 23.09.2011, 17:31Posts: 75 Likes: 0
 

 Post Topic: Re: Common compiler errors
PostPosted 17.10.2011, 21:42 
Dose anyone have problem compiling 2572 build and them starting the Editor or the Launcher?
I get an
Quote:
First-chance exception at 0x36aca205 in Launcher.exe: 0xC00000FD: Stack overflow.
Unhandled exception at 0x36aca205 in Launcher.exe: 0xC00000FD: Stack overflow.

I have compiled with VS 2008 and with VS 2010, release and debug, win32 and x64.


Katoun
  Beginner BeginnerMember since: 17.10.2011, 11:59Posts: 1 Likes: 0
 

 Post Topic: Re: Common compiler errors
PostPosted 17.10.2011, 23:44 
Quote by katoun:
Dose anyone have problem compiling 2572 build and them starting the Editor or the Launcher?
I get an
Quote:
First-chance exception at 0x36aca205 in Launcher.exe: 0xC00000FD: Stack overflow.
Unhandled exception at 0x36aca205 in Launcher.exe: 0xC00000FD: Stack overflow.

I have compiled with VS 2008 and with VS 2010, release and debug, win32 and x64.


i can confirm this, but only on 32bit

EDIT:
its because of the nvidia driver... i should read till the end :)
regarding the 64bit linker error, set the CryAction project to type utility, copy over CryAction.dll from SDK download if its gone.
  Beginner BeginnerMember since: 08.09.2011, 19:35Posts: 1 Likes: 0
 

 Post Topic: Re: Common compiler errors
PostPosted 19.10.2011, 13:36 
Quote by katoun:
Dose anyone have problem compiling 2572 build and them starting the Editor or the Launcher?
I get an
Quote:
First-chance exception at 0x36aca205 in Launcher.exe: 0xC00000FD: Stack overflow.
Unhandled exception at 0x36aca205 in Launcher.exe: 0xC00000FD: Stack overflow.

I have compiled with VS 2008 and with VS 2010, release and debug, win32 and x64.


I have the same problems using VS2008 (Express) and VS2010 (Express) with the new release. The previous Release was working with 2008 (Express) just fine.
Did anyone get this problem fixed?

Edit:
We changed the the graphiccard from nvidia to ati and now it works!
I hope they fix this problem with NVidia Cards or Drivers soon.

greets,
Sebastian
  Beginner BeginnerMember since: 28.09.2011, 17:09Posts: 4 Likes: 0
 

 Post Topic: Re: Common compiler errors
PostPosted 22.10.2011, 16:02 
HOW TO FIX CryAction.dll x64
Code:
LINK : error LNK2001: unresolved external symbol _DllMainCRTStartup

VS2010
Right clic 'CryAction.dll' > Properties:
Configuration: 'All Configuration' / Platform: 'x64'
Configuration Properties > General > Configuration Type > set to "Utility"
OK
User avatar   Trained Modder Trained ModderMember since: 21.10.2011, 07:12Posts: 252Location: USA Likes: 0
 

 Post Topic: Re: Common compiler errors
PostPosted 29.10.2011, 10:15 
Has anyone tried the new sdk update that says visual express 2010 now works?


-Bryan
http://www.SinisterRainbow.com
Image
See Stickman Thread Here - Updated Regularly (Videos, screenies, infinite system integration, more)