Emulation/cxbx-shogun
1
0
Fork 0
mirror of https://github.com/Echelon9/cxbx-shogun.git synced 2025-04-02 10:41:47 -04:00
Code Issues Projects Releases Packages Wiki Activity
shogun's mirrored branch of the Cxbx original Xbox emulator
183 commits 6 branches 0 tags 17 MiB
Find a file
Exact
Echelon9 bf70d51391 Fix initializer order for Error() object. 
clang++ -g -O2 -Wall -I../../src -I../../src/Common/Linux -I../..src/Linux -o ../../src/Common/OpenXDK.o -c ../../src/Common/OpenXDK.cpp
In file included from ../../src/Common/OpenXDK.cpp:34:
In file included from ../../src/Common/Xbe.h:37:
../../src/Common/Error.h:54:19: warning: field 'm_szError' will be initialized
      after field 'm_bFatal' [-Wreorder]
        Error() : m_szError(0), m_bFatal(false) { }
                  ^
1 warning generated.
2015-10-30 02:43:13 +11:00
build Fixup GNU Makefile for building intermediate tools 2015-10-30 01:32:49 +11:00
doc Run doxygen config file through 'doxygen -u' 2015-10-30 00:19:08 +11:00
import Remove static import of upx. Development environment can contain this functionality, if required. Cleanup broken script. 2015-10-30 00:27:54 +11:00
resource Update gitattributes (with line ending fixes) 2012-10-07 23:58:52 +11:00
src Fix initializer order for Error() object. 2015-10-30 02:43:13 +11:00
.gitattributes git-svn-id: https://cxbx.svn.sourceforge.net/svnroot/cxbx/branches/private/shogun/wip@174 2012-11-25 22:49:51 +11:00
.gitignore Fixup GNU Makefile for building intermediate tools 2015-10-30 01:32:49 +11:00
.travis.yml Initial Travis CI support for Linux intermediate tools 2015-10-30 02:03:15 +11:00
COPYING Update gitattributes (with line ending fixes) 2012-10-07 23:58:52 +11:00
README.md Add README 2015-10-30 02:17:21 +11:00

README.md

Cxbx

Build Status

A branch of the Cxbx source code.

This fork builds upon the SVN Cxbx in that it attempts to use modern software development practices:

  1. greater reliability through code robustness and automated testing.
  2. easier maintenance through code cleanliness.
  3. easier to develop new features.
  4. easier to re-use code though code de-coupling and modularisation.

Further details to be specified in time.

Developers

For now the code itself, 'doc/' folder and self-generated Doxygen documentation are the best resources.

TravisCI is used to run automatic builds of a limited subset of functionality.