tangent/LovePackaging
1
0
Fork 0
mirror of https://github.com/TangentFoxy/LovePackaging.git synced 2024-11-26 10:44:21 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

ready to release the next version now

Browse Source
This commit is contained in:
Paul Liverman 2014-12-29 21:29:36 -08:00
parent 5d653cabd5
commit b54ec59fe0
1 changed files with 7 additions and 66 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

73
README.md
View File

@ -11,11 +11,15 @@ Features
- Builds executables for distribution on Windows, Mac, and Linux. - Builds executables for distribution on Windows, Mac, and Linux.
- Supports including extra files automatically. - Supports including extra files automatically.
- That's about it for now, but there are other features planned. - Can automatically number builds.
- Supports loading a specified config file.
(Note: Must be called from its own directory, but can access a config file from anywhere relative to there.)
Installation Installation
------------ ------------
(Note that this guide may differ from the one in the latest release, refer to the ReadMe there for 100% correct info!)
Quick Guide: Quick Guide:
1. Download the [latest release](https://github.com/Guard13007/LovePackaging/releases)! 1. Download the [latest release](https://github.com/Guard13007/LovePackaging/releases)!
@ -24,6 +28,8 @@ Quick Guide:
4. Run `./build` for Linux / Mac OS X (OSX users need wget installed!!). 4. Run `./build` for Linux / Mac OS X (OSX users need wget installed!!).
No Windows version yet, sorry. No Windows version yet, sorry.
A quick note to mention: The build script must be run from its own directory. Everything in the config.sh should be absolute directories. If specifying a custom config script, the path must be a relative path to where the build script is located. This is kinda shitty, but I am kinda shitty, sorry.
Contributing Contributing
------------ ------------
@ -38,68 +44,3 @@ Feel free to submit an issue for any problem you have, also check [the forum](ht
Screenshots are great if you're reporting a problem. But in any case, common Screenshots are great if you're reporting a problem. But in any case, common
problems listed below, all one of them! problems listed below, all one of them!
#### What does "WARN: Mac packaging disabled." mean?
It means you have not edited the config file to specify that you have fixed the
Info.plist for your program. To fix this, first open the Info.plist file in the
same directory as this README file and edit the values on lines 43, 47, and 51.
They look like this by default:
```xml
<string>YOUR.OWN.UNIQUE.IDENTIFIER</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>YOUR PROGRAM NAME</string>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>CFBundleShortVersionString</key>
<string>YOUR.CURRENT.VERSION</string>
```
An example of what they should look like:
```xml
<string>com.example.package</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>Example Program by You</string>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>CFBundleShortVersionString</key>
<string>0.1.0</string>
```
Also line 71:
```xml
<key>NSHumanReadableCopyright</key>
<string>© YEAR You</string>
```
Something like:
```xml
<key>NSHumanReadableCopyright</key>
<string>© 2013-2014 Guard13007</string>
```
Once you have fixed that, open config.txt and change the line:
```bash
# Only change this if you know what you're doing (Read the README.md file).
macInfoPlistFixed=false
```
To this:
```bash
# Only change this if you know what you're doing (Read the README.md file).
macInfoPlistFixed=true
```
This will get rid of that error and start building Mac OS X packages. Sorry
this part isn't more streamlined (yet). I am a bit of a noob.