#778: New feature: Challenges
---------------------------+------------------------------------------------
Reporter: Per | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 2.3
Component: other | Version: svn/trunk
Keywords: Challenge GUI | Operating_system: All/Non-Specific
Blockedby: | Blocking:
---------------------------+------------------------------------------------
Comment(by i-NoD):
Per, the funny thing is that you've '''ALMOST''' completed #779...
Meanwhile the latest change to iniparser lib simply ruined MSVC build
process...
Are you sure that there is a strict need in using PHYSFS through
"physfs_ext.h" just to use PHYSFS_printf?
I can't handle those errors myself :(((
1>------ Rebuild All started: Project: iniparser, Configuration: Debug
Win32 ------
1>Deleting intermediate and output files for project 'iniparser',
configuration 'Debug|Win32'
1>Compiling...
1>iniparser.c
1> *** Warnings 4018,4100,4127,4204,4244,4267,4389 have been squelched.
***
1>c:\wzsvn\lib\framework\physfs_ext.h(27) : error C2061: syntax error :
identifier 'PHYSFS_writeSLE8'
1>c:\wzsvn\lib\framework\physfs_ext.h(27) : error C2059: syntax error :
';'
1>c:\wzsvn\lib\framework\physfs_ext.h(27) : error C2059: syntax error :
'type'
...same errors on every function in this header...
1>c:\wzsvn\lib\iniparser\iniparser.c(234) : warning C4013: 'PHYSFS_printf'
undefined; assuming extern returning int
1>dictionary.c
1>Generating Code...
1>iniparser - 33 error(s), 1 warning(s)
I do know that same header compiles OK in "map.c" file...
--
Ticket URL: <http://developer.wz2100.net/ticket/778#comment:6>
Warzone 2100 Trac <http://developer.wz2100.net/>
The Warzone 2100 Resurrection Project
_______________________________________________
Warzone-dev mailing list
[email protected]
https://mail.gna.org/listinfo/warzone-dev
