About real frontend using Qt (current attempt was doomed from start, that's bad that it happened when I was away...), I could try to do that, using QML, but since it most probably wouldn't be used then it doesn't make sense to invest in it. Especially since it would only make sense to start with QML2 (Qt5) which would require OpenGL ES 2 for GUI part... But since we are apparently going to support only that version anyway... There could be always legacy version, network compatible with upstream, if someone would like to support older hardware (for example OpenArena has one, with even smaller manpower...).
Compiling 3.1 with visual studio
Re: Compiling 3.1 with visual studio
vexed, yeah, I've read earlier about that their stupid change for new Visual Studio... They don't shoot on their foot but in face this time. 
About real frontend using Qt (current attempt was doomed from start, that's bad that it happened when I was away...), I could try to do that, using QML, but since it most probably wouldn't be used then it doesn't make sense to invest in it. Especially since it would only make sense to start with QML2 (Qt5) which would require OpenGL ES 2 for GUI part... But since we are apparently going to support only that version anyway... There could be always legacy version, network compatible with upstream, if someone would like to support older hardware (for example OpenArena has one, with even smaller manpower...).
About real frontend using Qt (current attempt was doomed from start, that's bad that it happened when I was away...), I could try to do that, using QML, but since it most probably wouldn't be used then it doesn't make sense to invest in it. Especially since it would only make sense to start with QML2 (Qt5) which would require OpenGL ES 2 for GUI part... But since we are apparently going to support only that version anyway... There could be always legacy version, network compatible with upstream, if someone would like to support older hardware (for example OpenArena has one, with even smaller manpower...).
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.
Beware! Mad Qt Evangelist.
The time has come, the high time, to destroy hatred in oneself.
Beware! Mad Qt Evangelist.
-
Lord Apocalypse
- Regular

- Posts: 678
- Joined: 29 Jul 2009, 18:01
Re: Compiling 3.1 with visual studio
Got everything up except the following...
There aren't in the repo that I can tell...
Code: Select all
Error 1 error C1083: Cannot open source file: 'strres_lexer.cpp': No such file or directory E:\SCM\Warzone 2100 git\lib\framework\c1xx framework
Error 2 error C1083: Cannot open source file: 'chat_lexer.cpp': No such file or directory E:\SCM\Warzone 2100 git\lib\script\c1xx script
Error 3 error C1083: Cannot open source file: 'script_lexer.cpp': No such file or directory E:\SCM\Warzone 2100 git\lib\script\c1xx script
Error 4 error C1083: Cannot open source file: 'audp_lexer.cpp': No such file or directory E:\SCM\Warzone 2100 git\lib\gamelib\c1xx gamelib
Re: Compiling 3.1 with visual studio
Probably you simply need to remove them form project file, maybe that will be enough.
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.
Beware! Mad Qt Evangelist.
The time has come, the high time, to destroy hatred in oneself.
Beware! Mad Qt Evangelist.
-
cybersphinx
- Inactive

- Posts: 1695
- Joined: 01 Sep 2006, 19:17
Re: Compiling 3.1 with visual studio
They're autogenerated by lex/flex and yacc/bison, no clue how that works on Windows. Should be in the source archives as well, iirc.
We want information... information... information.
-
Lord Apocalypse
- Regular

- Posts: 678
- Joined: 29 Jul 2009, 18:01
Re: Compiling 3.1 with visual studio
searched both hard drives and nothing so far (its almost done). Will see about taking them out and go from there I guess.
Re: Compiling 3.1 with visual studio
you need correct install flex/bison, write paths + write in OS "path" variable...Lord Apocalypse wrote:searched both hard drives and nothing so far (its almost done). Will see about taking them out and go from there I guess.
when you rebuild first time that files will be generated automatically
you should not search that files
-
Lord Apocalypse
- Regular

- Posts: 678
- Joined: 29 Jul 2009, 18:01
Re: Compiling 3.1 with visual studio
have flex, bison, and some other gnu files in E:\Programming\GnuWin32\bin and correct path set or I would be getting flex/bison errors. Not sure what you mean by write paths.
Re: Compiling 3.1 with visual studio
did you restarted pc?Lord Apocalypse wrote:have flex, bison, and some other gnu files in E:\Programming\GnuWin32\bin and correct path set or I would be getting flex/bison errors. Not sure what you mean by write paths.
try rebuild..
hmm i had same problem but i dont remember what i did to solve it
problem in bison/flex... check all things with that stuff 100 times
-
Lord Apocalypse
- Regular

- Posts: 678
- Joined: 29 Jul 2009, 18:01
Re: Compiling 3.1 with visual studio
I used the binary install of flex and bison. No VC files for source so decided to use what I had installed. Think I need to install source anyway?
Re: Compiling 3.1 with visual studio
no.. i installed flex/bison same way - from link in compile guide..Lord Apocalypse wrote:I used the binary install of flex and bison. No VC files for source so decided to use what I had installed. Think I need to install source anyway?
i had same propblem but i corrected path enviroment variable and may be something else
-
Lord Apocalypse
- Regular

- Posts: 678
- Joined: 29 Jul 2009, 18:01
Re: Compiling 3.1 with visual studio
Think I may have found something. In the various projects that require Flex I see (name)_lexer.lpp I also see an output file called (name)_lexer.lex.c which is the output of lex as far as I can tell. If I change the name in the flex config from %(Filename).lex.c to %(Filename).cpp do you think it will work? Will try in a few, kids are fighting... 
Re: Compiling 3.1 with visual studio
The compiler's build logs should tell you why it failed...you shouldn't have to change anything from that file to make it work.
As for why we are not using cmake / scons / whatever. Simple, nobody has done it.
Dropped pre VS2010 because of the horrible performance with STL, it still isn't that great compared to STLport, it has improved though.
As for why we are not using cmake / scons / whatever. Simple, nobody has done it.
Dropped pre VS2010 because of the horrible performance with STL, it still isn't that great compared to STLport, it has improved though.
/facepalm ...Grinch stole Warzone

contra principia negantem non est disputandum
Super busy, don't expect a timely reply back.
Super busy, don't expect a timely reply back.
-
Lord Apocalypse
- Regular

- Posts: 678
- Joined: 29 Jul 2009, 18:01
Re: Compiling 3.1 with visual studio
There is a cmake file for mingw thats why I asked. As for STL, never noticed performance problems and I believe Vega Strike uses a lot of the basic STL stuff. Is it the entire STL on windows that sucks or certain parts?
-
Lord Apocalypse
- Regular

- Posts: 678
- Joined: 29 Jul 2009, 18:01
Re: Compiling 3.1 with visual studio
Got it to compile finally but running it gives me a font error...
Any ideas? At least it compiles now though 
Code: Select all
error |12:29:41: [iV_initializeGLC:165] Failed to select font family DejaVu Sans as regular font
error |12:29:41: [iV_initializeGLC:183] iV_initializeGLC: Failed to select font family DejaVu Sans for the bold fontRe: Compiling 3.1 with visual studio
i have same error...Lord Apocalypse wrote:Got it to compile finally but running it gives me a font error...
Any ideas? At least it compiles now thoughCode: Select all
error |12:29:41: [iV_initializeGLC:165] Failed to select font family DejaVu Sans as regular font error |12:29:41: [iV_initializeGLC:183] iV_initializeGLC: Failed to select font family DejaVu Sans for the bold font
you know. i have wz folder with prepared sources and it works well..
but when i've tried make another folder (dowloaded from git and etc..) then i got error with djvu font
may be there is something wrong with my devpkg