| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
module.mk file of the kyra engine
|
|
|
|
|
|
|
|
Some project files (iPhone) and backend files (Symbian) still reference m4.dat,
but I know not enough on how to remove that without breaking something.
|
|
|
|
|
|
tools
- Move project name and description to BuildSetup structure
- Add list of tools to generate project for (similar to the list of features)
|
|
|
|
|
|
|
|
Also, do the same commands for Release and Debug.
|
|
|
|
|
|
|
|
|
|
This allows distributing MSVC compiled binaries without the MSVCRT runtime dll.
|
|
|
|
|
|
|
|
|
|
This only outputs a skeleton project with no files and targets yet
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
determined
|
|
|
|
|
|
Formerly create_project incorrectly assumed that a given object file is only
present once in an module.mk file. This is not the case for backends/module.mk
for example. There the Windows FS object files are in two different if blocks.
In this particular case it resulted in the object file being added to both the
include list and the exclude list.
Now the module.mk handler prefers files being in the include list.
|
|
Embed engine/theme dists files into Win Executable.
Check the following link for further discussion:
https://github.com/scummvm/scummvm/pull/31
|
|
|
|
projects
|
|
|
|
The revision number now includes the number of commits since the last tag
|
|
|
|
Conflicts:
devtools/create_project/scripts/postbuild.cmd
devtools/create_project/visualstudio.cpp
ports.mk
|
|
|
|
|
|
|
|
Variadic macros are C99 and ugly in C++. If we would want to do it differently
we should rather rely on C++0x's initializer lists. But since we cannot assume
all compilers we want create_project to build support that we cannot do that.
|
|
of tree)
|
|
|
|
|
