19
edits
Difference between revisions of "Game Packaging"
Jump to navigation
Jump to search
m
→How to extend DLC support to more distribution stores
Ankushdutt (talk | contribs) |
Ankushdutt (talk | contribs) |
||
| Line 12: | Line 12: | ||
# Set the <code>dlcspath</code> in appropriate backends. | # Set the <code>dlcspath</code> in appropriate backends. | ||
# Use <code>#ifdef USE_DLC</code> where applicable. Before building, make sure to enable DLC support by using <code>--enable-dlc</code> with <code>./configure</code>. | # Use <code>#ifdef USE_DLC</code> where applicable. Before building, make sure to enable DLC support by using <code>--enable-dlc</code> with <code>./configure</code>. | ||
# Add a new entry to <code>packaging/export-platforms.json</code>. The <code>export-platforms.json</code> consists of the description of scripts that | # Add a new entry to <code>packaging/export-platforms.json</code>. The <code>export-platforms.json</code> consists of the description of scripts that prepare and package the game in a specific format recognized by the distribution store and, if possible, upload the game directly to the distribution store. You can include the 3rd party SDK/scripts/tools or self-written scripts in the <code>packaging/scripts</code> directory. Here is an example for an entry to <code>export-platforms.json</code> (The single $ means variable from <code>packaging/package.py</code> context, double $ means variable from <code>packaging/dlc-games.json</code>, and triple $ means it is an environment variable): | ||
<syntaxhighlight lang="json"> | <syntaxhighlight lang="json"> | ||
"android": { | "android": { | ||