Changes between Version 8 and Version 9 of premake


Ignore:
Timestamp:
Jan 12, 2013, 3:20:39 AM (11 years ago)
Author:
historic_bruno
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • premake

    v8 v9  
    5656'''Note:''' Most of the options are special purpose and not needed for the average build. You shouldn't use an option unless you understand it and have a need for it.
    5757
    58 The most commonly used options are `--atlas` and `--collada` (you might want to disable them if building the game on an experimental new platform like Android). `--atlas` is not used by default in `update-workspaces.bat`, because we don't bundle the wxWidgets libraries in SVN. If you are using `update-workspaces.sh` Atlas is build by default. Use `--disable-atlas` to skip it.
     58The most commonly used options are `--atlas` and `--collada` (you might want to disable them if building the game on an experimental new platform like Android). `--atlas` is not used by default in `update-workspaces.bat`, because we don't bundle the wxWidgets libraries in SVN. If you are using `update-workspaces.sh` Atlas is built by default. Use `--disable-atlas` to skip it.
    5959
    6060The `update-workspaces` scripts will pass arguments through to Premake:
    … …  
    7272== Modifying Premake ==
    7373
    74 To modify Premake's behavior, you typically modify the Lua scripts within [source:/ps/trunk/build/premake/premake4 build/premake/premake4]. You shouldn't modify the Makefile(s) or C source code directly, as these are automatically generated from the scripts by Premake. Obviously you need a working, already built Premake binary to do this. This is slightly confusing in that Premake creates the workspace you need to build a new version of Premake.
     74To modify Premake's behavior, you typically modify the Lua scripts within [source:/ps/trunk/build/premake/premake4 build/premake/premake4]. You shouldn't modify its [source:/ps/trunk/build/premake/premake4/build build files] or [source:/ps/trunk/build/premake/premake4/src/host/scripts.c scripts.c] directly, as these are automatically generated from the scripts. Obviously you need a working, already built Premake binary to do this. This is slightly confusing in that Premake creates the workspace you need to build a new version of Premake.
    7575
    7676After you've modified Premake's source scripts, you need to run the old Premake binary with the `embed` option to update e.g. `src/host/scripts.c`, see [http://industriousone.com/building-premake Building Premake] for more information.
    7777
    78 == Autogenerating Premake workspaces ==
     78== Generating Premake's workspaces ==
    7979
    80 Premake's own workspaces and Makefiles are mostly autogenerated using a Premake binary and the contents of [source:/ps/trunk/build/premake/premake4/premake4.lua build/premake/premake4/premake4.lua] - the Premake4 build configuration script (not to be confused with the game's custom `premake4.lua` script, one directory higher). Building Premake and running it with the `--help` option will list available options, the basic invocation is as follows (on *nix):
     80Premake's own workspaces and Makefiles are mostly generated using a Premake binary and the contents of [source:/ps/trunk/build/premake/premake4/premake4.lua build/premake/premake4/premake4.lua] - the Premake4 build configuration script (not to be confused with the game's custom `premake4.lua` script, one directory higher). Building Premake and running it with the `--help` option will list available options, the basic invocation is as follows (on *nix):
    8181{{{
    8282./bin/release/premake4 --os=linux --to=build/gmake.unix/ gmake