projects:liflg:mojosetup
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
projects:liflg:mojosetup [2009/09/24 09:08] – kratz00 | projects:liflg:mojosetup [2012/02/21 19:44] (current) – [x86 and x86-64 Support] kratz00 | ||
---|---|---|---|
Line 6: | Line 6: | ||
======Problems====== | ======Problems====== | ||
- | * doesn' | + | * doesn' |
* how can we launch a shell script from within the installer? | * how can we launch a shell script from within the installer? | ||
* how can we copy the same behavior which is possible with loki_setup and the component tag (there is something nasty for the downloadable Postal installers done by Ryan) | * how can we copy the same behavior which is possible with loki_setup and the component tag (there is something nasty for the downloadable Postal installers done by Ryan) | ||
Line 12: | Line 12: | ||
* no support for extracting Microsoft cabinet files (*.cab) | * no support for extracting Microsoft cabinet files (*.cab) | ||
* no support for extracting InstallShield cabinet files (*.cab) | * no support for extracting InstallShield cabinet files (*.cab) | ||
- | * no support for extracting Descent 3 Mercenary | + | * no support for 7z archives |
- | * no support for extracting Theocracy archives | + | |
- | | + | |
- | ====== x86 and x86-64 | + | ====== x86 and x86_64 |
- | If we have binaries for both architectures we build two installers, most likely we only have binaries | + | If we have binaries for both architectures we build two installers, most likely we only have x86 binaries, |
- | in this case we will only make a installer for x86. | + | in this case we will only make an installer for x86. |
- | It would not make sense to build a native x86_64 installer, if you need the 32 libs anyway to run the game. | + | It would not make sense to build a native x86_64 installer, if you need all the 32 bit libraries |
- | + | ||
- | * since the installer itself is a binary, there has to be a separate x64 installer to deliver x64-game-binaries | + | |
- | * it's not possible for a x86 installer to detect if its running on a x64 machine (and install the x64 binary of the game) | + | |
+ | * since the installer itself is a binary, there has to be a separate x86_64 installer to deliver x86_64 game binaries | ||
======Worth reading====== | ======Worth reading====== | ||
- | http:// | + | |
+ | Initial tech discussion about MojoSetup features:\\ | ||
+ | http:// | ||
+ | |||
+ | Documentation:\\ | ||
+ | http:// | ||
======Naming schema====== | ======Naming schema====== | ||
< | < | ||
- | $GameName_$Version-$Language.$Special-$Patchlevel_$Arch.bin | + | $GameName_$Version-$Language.$Special-$Patchlevel_$Arch.mojo.run |
</ | </ | ||
Line 38: | Line 39: | ||
* $Language: indicates in which language the game is, if it supports more than one language use // | * $Language: indicates in which language the game is, if it supports more than one language use // | ||
* $Special: normally this field can be omitted, it's used to distinguish special flavours of a game, e.g. our Serious Sam 2 installer is avaiable as a dvd, 4 cd and //Software Pyramide// dvd version (multiple words have to be separated by a dot) | * $Special: normally this field can be omitted, it's used to distinguish special flavours of a game, e.g. our Serious Sam 2 installer is avaiable as a dvd, 4 cd and //Software Pyramide// dvd version (multiple words have to be separated by a dot) | ||
- | * $Patchlevel: | + | * $Patchlevel: |
* $Arch: x86 or x86_64 | * $Arch: x86 or x86_64 | ||
- | Example 1: mohaa_1.11beta3-dutch.warchest.edition_x86.bin | + | Example 1: mohaa_1.11beta3-dutch.warchest.edition_x86 |
^ $GameName ^ $Version ^ $Language ^ $Special ^ $Patchlevel ^ $Arch ^ | ^ $GameName ^ $Version ^ $Language ^ $Special ^ $Patchlevel ^ $Arch ^ | ||
| mohaa | 1.11beta3 | dutch | warchest.edition| | x86| | | mohaa | 1.11beta3 | dutch | warchest.edition| | x86| | ||
- | Example 2: true.combat.elite_0.49b-english-4_x86_64.bin | + | Example 2: true.combat.elite_0.49b-english-4_x86_64 |
^ $GameName ^ $Version ^ $Language ^ $Special ^ $Patchlevel ^ $Arch ^ | ^ $GameName ^ $Version ^ $Language ^ $Special ^ $Patchlevel ^ $Arch ^ | ||
Line 52: | Line 53: | ||
======Installer Howto====== | ======Installer Howto====== | ||
- | *check out the dummy: < | + | *get a clone of the LIFLG repository: < |
+ | |||
+ | | ||
- | | + | |
| | ||
Line 68: | Line 71: | ||
*add needed files to data/ | *add needed files to data/ | ||
- | *pack the installer | + | *pack the installer: < |
#!/bin/sh | #!/bin/sh | ||
- | DIR=" | + | NAME=`basename "$PWD".mojo.run` |
- | NAME="`basename | + | cp mojosetup* " |
- | cp mojosetup* " | + | zip - -qr9 data/ guis/ meta/ scripts/ | cat >> " |
- | zip - -qr9 data/ guis/ meta/ scripts/ | cat >> " | + | sha256sum " |
- | sha256sum " | + | |
If anybody knows why the following does not work, please let us know: | If anybody knows why the following does not work, please let us know: | ||
< | < | ||
- | zip - -qr9 data/ guis/ meta/ scripts/ >> " | + | zip - -qr9 data/ guis/ meta/ scripts/ >> " |
</ | </ | ||
======Create the hash file====== | ======Create the hash file====== | ||
< | < | ||
- | sha256sum $Installer.bin > $Installer.bin.sha256 | + | sha256sum $Installer > $Installer.sha256 |
</ | </ | ||
======Signing the hash file====== | ======Signing the hash file====== | ||
< | < | ||
- | gpg -b --armor -u team@liflg.org $Installer.bin.sha256 | + | gpg -b --armor -u team@liflg.org $Installer.sha256 |
</ | </ | ||
======Bugreports by the LIFLG team====== | ======Bugreports by the LIFLG team====== | ||
Line 99: | Line 101: | ||
http:// | http:// | ||
+ | * Wrong wording vs. automatically mount install CD/DVD | ||
+ | http:// | ||
== Closed/ | == Closed/ | ||
projects/liflg/mojosetup.1253776133.txt.gz · Last modified: 2009/09/24 09:08 by kratz00