Editing MG/CodeBlocks Compiling
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | ''' | + | =='''CodeBlocks Cross Platform IDE / Compiling'''== |
| + | Please note that we do not currently recommend this approach on Windows unless you know how to fix compilation and linking issues by yourself. On Windows, use VC++ 2008 for now. | ||
| + | ===Choose a subversion client=== | ||
| − | == | + | ====Linux==== |
| + | |||
| + | Most users will want to use the [https://subversion.apache.org/ Apache Software Foundation (ASF) subversion] command line interface (CLI), as provided, on most distributions, by the 'subversion' package. Many distributions also provide graphical interfaces which are either frontends to the ASF subversion CLI or are standalone. | ||
| + | |||
| + | ====Windows==== | ||
| + | |||
| + | If you fancy graphical interfaces then [http://tortoisesvn.tigris.org/ Tortoise] is for you. If you actually like to work on a command line interfaces, then [http://www.sliksvn.com/en/download/ SlikSVN] is the utility you want. | ||
| + | |||
| + | Windows 7 note: If you are going to use subversion on 64-bit Windows 7 and get error messages like ''The file or directory is corrupted and unreadable'' then that's because your OS's only primary file system [http://glest.org/glest_board/?topic=5611.msg58480#msg58480 is buggy]. | ||
===Check out the source code=== | ===Check out the source code=== | ||
| − | + | [[MG/Getting The Code|Get the project]] from [[MG/SVN Structure|MegaGlests' subversion repository]]. | |
===Get the dependencies=== | ===Get the dependencies=== | ||
| Line 12: | Line 22: | ||
''jpeg, lua5.1, png, SDL, openal, curl, xerces-c, ogg, vorbis, vorbisfile, vorbisenc, z, GL, GLU, SDLmain, ircclient'' | ''jpeg, lua5.1, png, SDL, openal, curl, xerces-c, ogg, vorbis, vorbisfile, vorbisenc, z, GL, GLU, SDLmain, ircclient'' | ||
| − | Some of the tools also require ''wx'' | + | Some of the tools also require ''wx.<br />'' |
| + | Hint: On Debian like systems (such as Ubuntu and its derivatives), these packages will typically start with "lib", sometimes have a number added, and end with "-dev". For example, the development package for the xerces-c library may be called ''libxerces-c2-dev''. | ||
====Windows==== | ====Windows==== | ||
| − | Download the [https://sourceforge.net/projects/megaglest/files/win32_deps_mingw.7z/download | + | Download the [https://sourceforge.net/projects/megaglest/files/win32_deps_mingw.7z/download mingw build dependencies archive], then decompress (using [http://www.7-zip.org/ 7-zip]) the mingw dependency archive into the '''source''' folder. You should now see a '''source\win32_deps''' sub-folder with lots of stuff inside. |
===Install CodeBlocks=== | ===Install CodeBlocks=== | ||
| + | |||
[http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks Install CodeBlocks] for your platform. | [http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks Install CodeBlocks] for your platform. | ||
===Configure CodeBlocks=== | ===Configure CodeBlocks=== | ||
| − | If you plan to build Windows binaries ([http://forums.codeblocks.org/index.php?topic=3343.0 Linux Cross Compile] or [http://wiki.codeblocks.org/index.php?title=MinGW_installation Windows Mingw]) configure CodeBlocks for | + | |
| + | If you plan to build Windows binaries ([http://forums.codeblocks.org/index.php?topic=3343.0 Linux Cross Compile] or [http://wiki.codeblocks.org/index.php?title=MinGW_installation Windows Mingw]) configure CodeBlocks for mingw. | ||
Open the main workspace in CodeBlocks located in:''' mk/windoze/megaglest.workspace''' | Open the main workspace in CodeBlocks located in:''' mk/windoze/megaglest.workspace''' | ||
===Make a build=== | ===Make a build=== | ||
| + | |||
Select the build target (the dropdown at the top) from current available options: | Select the build target (the dropdown at the top) from current available options: | ||
| Line 37: | Line 51: | ||
*Debug Linux. | *Debug Linux. | ||
| − | From the Build Menu option Select ''Rebuild Workspace''. | + | From the Build Menu option Select '''Rebuild Workspace'''.<br /> |
===Inspecting your builds=== | ===Inspecting your builds=== | ||
| + | |||
====Linux targets==== | ====Linux targets==== | ||
| − | Linux targets compile into ''mk/linux'' and are called ''glest.bin, glest_editor, glest_g3dviewer'' etc. | + | |
| + | Linux targets compile into '''mk/linux''' and are called '''glest.bin, glest_editor, glest_g3dviewer''' etc. | ||
====Windows targets==== | ====Windows targets==== | ||
| − | |||
| − | To test the game, Windows users copy dependency | + | If nothing goes wrong you will see '''glest_game.exe''' (and other binaries) in '''data/glest_game''' for Windows targets (where all the data content lives). |
| − | + | ||
| + | To test the game, Windows users copy dependency dll's from the '''win32_deps\lib''' folder to the runtime binary folder. | ||