3.10 vs 2008 build issues

Expanding and utilizing the engine via C++.
9 posts Page 1 of 1
Hodo33
Posts: 42
Joined: Fri Dec 29, 2017 4:34 pm
by Hodo33 » Fri Jun 08, 2018 5:06 pm
I get many lines of this

Engine/source/console/engineTypes.h(589) : error C2143: syntax error : missing ';' before '}'

can someone direct me to fix this?
LoLJester
Posts: 66
Joined: Thu Aug 13, 2015 5:58 pm
 
by LoLJester » Fri Jun 08, 2018 7:53 pm
Hi,

Double click on the error and post the line of code that the Debugger will highlight.
I have a feeling that there is a syntax error on how a variable in the engineTypes.h file is declared; or, it could be that there is a missing } somewhere.
Hodo33
Posts: 42
Joined: Fri Dec 29, 2017 4:34 pm
by Hodo33 » Sat Jun 09, 2018 1:57 pm
just go to engineTypes.h and every line is syntax error. I dont think it's one line that is bugged it's a setting someplace.
Like to think the build would just work right out of the box on virgin code.
OTHGMars
Posts: 26
Joined: Fri Jul 14, 2017 2:19 am
by OTHGMars » Sat Jun 09, 2018 11:59 pm
VS2008 is not a supported IDE. It will build with VS2015 or VS2017.
JeffR
Steering Committee
Steering Committee
Posts: 858
Joined: Tue Feb 03, 2015 9:49 pm
 
by JeffR » Sun Jun 10, 2018 2:07 am
Yeah, that looks to be an issue with how 2008 handles the code structure for whatever reason. Likely a code features 2008's compiler just doesn't support.

As OTHGMars said, 2015 and 2017 both compile just fine, so I'd suggest upgrading to one of the two(2015 is a bit more stable than 2017, they've had a very weird bug/bugfix cycle with 2017)
Hodo33
Posts: 42
Joined: Fri Dec 29, 2017 4:34 pm
by Hodo33 » Sun Jun 10, 2018 2:13 pm
Thanks for the input.
Opening the 3.10.1 full template there is only vs 2008, vs 2010 and vs 2012 in the build directory. I have 2017 so which solution should I use to convert? Is it possible to drop a 2017 solution into the build directory for future use?
Hodo33
Posts: 42
Joined: Fri Dec 29, 2017 4:34 pm
by Hodo33 » Sun Jun 10, 2018 3:15 pm
Update:
I got it to mostly build in 2017 using 2012 sln
Open AL wont build because of the include path.
In the lib directory I find this Engine/lib/openal-soft/include/al
but the includes path in the compiler is looking for engine/lib/openal/win32
any suggestion to rename directory or change path in compiler ?
Thanks for any input
OTHGMars
Posts: 26
Joined: Fri Jul 14, 2017 2:19 am
by OTHGMars » Mon Jun 11, 2018 2:46 am
@ Hodo33 That project is also a bit outdated. Currently T3D requires cmake to generate the solution files needed for compiling the engine. You'll probably want to start with a fresh clone or download of the engine source code. Then follow the instructions here. If you follow those instructions and then open the solution file that cmake generates for you, you should be up and running with the new T3D.
Hodo33
Posts: 42
Joined: Fri Dec 29, 2017 4:34 pm
by Hodo33 » Tue Jun 12, 2018 2:45 am
Up and running meaning I can use VS 2017?
Why go to all the trouble of using cmake to generate it wouldn't it be simpler to just post a game.sln for 2017 ?
I'll do the cmake deed but seems redundant.. Thanks for the help and info...
9 posts Page 1 of 1

Who is online

Users browsing this forum: No registered users and 3 guests