[C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
Ah, ugh, you meant video tutorials. I kind of hate those on general principles. Stuck them on the wiki anyway because I'm apparently pretty alone with that.
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
Most of the people are visual learners. So I thought a video would make a better impression on them rather than worded instructions.
So I'm going to put them in http://wiki.armagetronad.org/index.php? ... evelopment and create a section called "Tutorials".
Is that ok Z-Man?
So I'm going to put them in http://wiki.armagetronad.org/index.php? ... evelopment and create a section called "Tutorials".
Is that ok Z-Man?
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
also, Z-Man,. I'm wondering where you change the title menu of the game. You know when you start the game, it opens up and the title menu reads: Armagetron Sty+Ct v0.2.0-armagetronad-sty+ct 03-05-2012
You know how to change that to something that we prefer it to be?
You know how to change that to something that we prefer it to be?
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
Sure, I already put them up in the main dev section, but that's a good place to put them again. It's only links.
The title menu text, like all other texts, is somewhere in language/english_base.txt; identifier is main_menu_text. Right now it's "game name" v"version", so that's why it's a bit clunky for you.
The title menu text, like all other texts, is somewhere in language/english_base.txt; identifier is main_menu_text. Right now it's "game name" v"version", so that's why it's a bit clunky for you.
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
ok done.
Also, I can change it using main_menu_text but ... how do I make it automatically adjust it because I see it has \g v\1 but idk what to edit in the code:blocks.
Can you tell please.
Also, I can change it using main_menu_text but ... how do I make it automatically adjust it because I see it has \g v\1 but idk what to edit in the code:blocks.
Can you tell please.
- Tank Program
- Forum & Project Admin, PhD
- Posts: 6711
- Joined: Thu Dec 18, 2003 7:03 pm
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
Check config.h I think.
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
is that the config.h file inside win32?
If that's it then I'm not sure what to do in it as it only has
If that's it then I'm not sure what to do in it as it only has
Code: Select all
// Windows client configuration header
#ifndef CONFIG_H_INCLUDED
#define CONFIG_H_INCLUDED
// include common Windows header
#include "config_common.h"
#endif
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
Then check config_common.h
There's a difference between knowing your shit, and knowing you're shit. Grammar does matter.
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
Code: Select all
// config include file common for all Windows builds
// map BSD/Linux/OSX string compare function to Win pendant
#define strcasecmp strcmpi
// for visual studio 2005: use secure template overloads of strcopy and the like
#define _CRT_SECURE_CPP_OVERLOAD_STANDARD_NAMES 1
// and disable warnings about those calls that can't be converted. We may want to look at
// them later, though.
#define _CRT_SECURE_NO_DEPRECATE 1
// include of windows.h needed for consistency of silly windows #defines ( SetPort -> SetPortA, GetUserName -> GetUserNameA )
#include <windows.h>
// include common non-autoconf config file
#include "config_ide.h"
// disable long identifier warnings, they are common in STL
#pragma warning ( disable: 4786 )
// disable POD initialization behavior change warning in VisualC++ 2005
#pragma warning ( disable: 4345 )
// compatibility with later mingw versions
#if defined(__GNUC__) && __GNUC__ >= 4
#define HAVE_ISBLANK
#endif
// activate dirty OpenGL initialization option
#ifndef DIRTY
#define DIRTY
#endif
// Define if this is a Windows OS.
#ifndef WIN32
#define WIN32
#endif
// defines for data directories in Windows
#ifndef DEBUG
#define USER_DATA_DIR "${APPDATA}/Armagetron"
#define SCREENSHOT_DIR "${MYPICTURES}/Armagetron"
#else
#define USER_DATA_DIR "."
#endif
// Define this for the particle library
#define PARTICLEDLL_EXPORTS
- Tank Program
- Forum & Project Admin, PhD
- Posts: 6711
- Joined: Thu Dec 18, 2003 7:03 pm
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
I'm not sure where it is in the Windows sources. In the Linux sources in the root folder the config.h has:I seem to remember something about a batch file that generated this stuff...
Code: Select all
/* Name of package */
#define PACKAGE "armagetronad"
/* Define to the address where bug reports for this package should be sent. */
#define PACKAGE_BUGREPORT ""
/* Define to the full name of this package. */
#define PACKAGE_NAME "Armagetronad"
/* Define to the full name and version of this package. */
#define PACKAGE_STRING "Armagetronad 0.3.0"
/* Define to the one symbol short name of this package. */
#define PACKAGE_TARNAME "armagetronad"
/* Define to the version of this package. */
#define PACKAGE_VERSION "0.3.0"
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
From the only sources i currently have.
Code: Select all
n@ubuntu:~$ grep -Rn PACKAGE_NAME aiarma/
aiarma/0.4-random-features/resource/Makefile.in:108:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/resource/Makefile:108:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/config.log:203:| #define PACKAGE_NAME "armagetronad"
aiarma/0.4-random-features/config.log:225:| #define PACKAGE_NAME "armagetronad"
aiarma/0.4-random-features/config.log:277:| #define PACKAGE_NAME "armagetronad"
aiarma/0.4-random-features/config.log:299:| #define PACKAGE_NAME "armagetronad"
aiarma/0.4-random-features/config.log:332:| #define PACKAGE_NAME "armagetronad"
aiarma/0.4-random-features/config.log:527:| #define PACKAGE_NAME "armagetronad"
aiarma/0.4-random-features/config.log:981:PACKAGE_NAME='armagetronad'
aiarma/0.4-random-features/config.log:1110:#define PACKAGE_NAME "armagetronad"
aiarma/0.4-random-features/batch/Makefile.in:132:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/batch/Makefile:132:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/aclocal.m4:469:m4_if(m4_ifdef([AC_PACKAGE_NAME], 1)m4_ifdef([AC_PACKAGE_VERSION], 1), 11,,
aiarma/0.4-random-features/www-root/Makefile.in:132:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/www-root/Makefile:132:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/desktop/Makefile.in:135:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/desktop/Makefile:135:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/src/doc/Makefile.in:174:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/src/doc/net/Makefile.in:133:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/src/doc/net/Makefile:133:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/src/doc/Makefile:174:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/src/protobuf/Makefile.in:150:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/src/protobuf/Makefile:150:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/src/swig/Makefile.in:106:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/src/swig/Makefile:106:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/src/Makefile.in:527:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/src/thirdparty/mathexpr/Makefile.in:129:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/src/thirdparty/mathexpr/Makefile:129:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/src/thirdparty/scrap/Makefile.in:129:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/src/thirdparty/scrap/Makefile:129:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/src/thirdparty/Makefile.in:146:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/src/thirdparty/particles/Makefile.in:132:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/src/thirdparty/particles/Makefile:132:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/src/thirdparty/Makefile:146:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/src/first/Makefile.in:108:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/src/first/Makefile:108:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/src/Makefile:527:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/aa_config.h:188:#define PACKAGE_NAME "armagetronad"
aiarma/0.4-random-features/aa_config.h.in:187:#undef PACKAGE_NAME
aiarma/0.4-random-features/Makefile.in:199:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/config/Makefile.in:133:PACKAGE_NAME = @PACKAGE_NAME@
aiarma/0.4-random-features/config/Makefile:133:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/Makefile:199:PACKAGE_NAME = armagetronad
aiarma/0.4-random-features/config.status:859:S["PACKAGE_NAME"]="armagetronad"
aiarma/0.4-random-features/config.status:903:D["PACKAGE_NAME"]=" \"armagetronad\""
aiarma/0.4-random-features/configure:550:PACKAGE_NAME='armagetronad'
aiarma/0.4-random-features/configure:798:PACKAGE_NAME
aiarma/0.4-random-features/configure:2583:#define PACKAGE_NAME "$PACKAGE_NAME"
aiarma/0.4-random-features/autom4te.cache/traces.0:267:m4_if(m4_ifdef([AC_PACKAGE_NAME], 1)m4_ifdef([AC_PACKAGE_VERSION], 1), 11,,
aiarma/0.4-random-features/autom4te.cache/traces.0:1381:m4trace:configure.ac:11: -1- m4_pattern_allow([^PACKAGE_NAME$])
aiarma/0.4-random-features/autom4te.cache/traces.0:1399:m4trace:configure.ac:11: -1- m4_pattern_allow([^PACKAGE_NAME$])
aiarma/0.4-random-features/autom4te.cache/traces.1:19:m4trace:configure.ac:11: -1- AC_SUBST([PACKAGE_NAME], [m4_ifdef([AC_PACKAGE_NAME], ['AC_PACKAGE_NAME'])])
aiarma/0.4-random-features/autom4te.cache/traces.1:20:m4trace:configure.ac:11: -1- AC_SUBST_TRACE([PACKAGE_NAME])
aiarma/0.4-random-features/autom4te.cache/traces.1:21:m4trace:configure.ac:11: -1- m4_pattern_allow([^PACKAGE_NAME$])
aiarma/0.4-random-features/autom4te.cache/traces.1:73:m4trace:configure.ac:11: -1- AC_DEFINE_TRACE_LITERAL([PACKAGE_NAME])
aiarma/0.4-random-features/autom4te.cache/traces.1:74:m4trace:configure.ac:11: -1- m4_pattern_allow([^PACKAGE_NAME$])
aiarma/0.4-random-features/autom4te.cache/traces.1:75:m4trace:configure.ac:11: -1- AH_OUTPUT([PACKAGE_NAME], [/* Define to the full name of this package. */
aiarma/0.4-random-features/autom4te.cache/traces.1:76:@%:@undef PACKAGE_NAME])
aiarma/0.4-random-features/autom4te.cache/output.0:550:PACKAGE_NAME='armagetronad'
aiarma/0.4-random-features/autom4te.cache/output.0:798:PACKAGE_NAME
aiarma/0.4-random-features/autom4te.cache/output.0:2583:@%:@define PACKAGE_NAME "$PACKAGE_NAME"
aiarma/0.4-random-features/autom4te.cache/output.1:550:PACKAGE_NAME='armagetronad'
aiarma/0.4-random-features/autom4te.cache/output.1:798:PACKAGE_NAME
aiarma/0.4-random-features/autom4te.cache/output.1:2583:@%:@define PACKAGE_NAME "$PACKAGE_NAME"
There's a difference between knowing your shit, and knowing you're shit. Grammar does matter.
- AI-team
- Shutout Match Winner
- Posts: 1020
- Joined: Tue Jun 23, 2009 6:17 pm
- Location: Germany/Munich
- Contact:
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
this thread is about 0.2.8-sty+ct tho
"95% of people believe in every quote you post on the internet" ~ Abraham Lincoln
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
Ya thanks for pointing it out AI. Tank and nux, you guys are on about the 0.4 trunk version
Re: [C++] 0.2.8+sty+ct Compiling with Code:Blocks troubles
I wouldnt think _this_ has changed a lot from .2.8-sty to .4.
There's a difference between knowing your shit, and knowing you're shit. Grammar does matter.