Age | Commit message (Collapse) | Author | |
---|---|---|---|
2007-12-25 | (svn r11695) -Codechange: Converted the md5 algorithm to OOP | skidd13 | |
-Codechange: Adapt the md5 algorithm to the OpenTTD source | |||
2007-03-07 | (svn r9051) -Codechange: typedef [enum|struct] Y {} X; -> [enum|struct] X {}; | rubidium | |
2007-03-03 | (svn r8987) -Cleanup: doxygen changes. Again. Mostly (still) @files missing ↵ | belugas | |
tags and (more than just) a few comments style. | |||
2007-02-05 | (svn r8605) -Codechange: [OSX] changed all objective C to objective C++ | bjarni | |
This will permanently solve the issue where compilation on OSX broke because C++ code was added to some header files -Note: (important if you develop mac specific code) taken from http://developer.apple.com/releasenotes/Cocoa/Objective-C++.html gdb lacks an integrated C++ with Objective-C parser. This means that gdb won't be able to evaluate expressions that contain both C++ and Objective-C constructs. gdb assumes that the language for ".mm" files is C++. you can change it to objective C by typing: (gdb) set language objc Mixing C++ and objective C has some limitation (see link for all of them) | |||
2007-01-02 | (svn r7759) -Merge: makefile rewrite. This merge features: | rubidium | |
- A proper ./configure, so everything needs to be configured only once, not for every make. - Usage of makedepend when available. This greatly reduces the time needed for generating the dependencies. - A generator for all project files. There is a single file with sources, which is used to generate Makefiles and the project files for MSVC. - Proper support for OSX universal binaries. - Object files for non-MSVC compiles are also placed in separate directories, making is faster to switch between debug and release compiles and it does not touch the directory with the source files. - Functionality to make a bundle of all needed files for for example a nightly or distribution of a binary with all needed GRFs and language files. Note: as this merge moves almost all files, it is recommended to make a backup of your working copy before updating your working copy. |