So if in the past we had to run something like ./build.sh linguist && ./build.sh && ./SilentDragonLite and then manually create a launcher now we can just run ./install.sh
If you're okay with my solution run-after-build.sh can be removed.
The below is the file that should be stored in `~/.local/share/applications` in order to make a nice Hush SDL laucher with SD logo.
```
[Desktop Entry]
Name=SilentDragonLite
Exec=/home/user/SilentDragonLite/SilentDragonLite
Icon=/home/user/SilentDragonLite/res/SDLogo.png
Terminal=false
Type=Application
```
`install.sh` is the only one script that needs to be run in order to compile the software and move `SilentDragonLite.desktop`
```
./build.sh linguist && ./build.sh
username=$(id -un)
sed -i "s|\/home\/.*\/SilentDragonLite\/|\/home\/$username\/SilentDragonLite\/|g" SilentDragonLite.desktop
mv SilentDragonLite.desktop ~/.local/share/applications
```
So if in the past we had to run something like `./build.sh linguist && ./build.sh && ./SilentDragonLite` and then manually create a launcher now we can just run `./install.sh`
If you're okay with my solution ` run-after-build.sh` can be removed.
Let me know if it makes sense. @duke
@onryo looks useful, thanks! I would like to keep run-after-build.sh since I use it to automate the running of SDL after a successful compile, which is slightly different.
@onryo looks useful, thanks! I would like to keep `run-after-build.sh` since I use it to automate the running of SDL after a successful compile, which is slightly different.
One thing, when git cloning the repo install.sh doesn't have enough permissions as build.sh
Here's the details:
-rwxrwxr-x 1 user user build.sh
-rw-rw-r-- 1 user user install.sh
We don't want to make users run sudo chmod +x install.sh, could you clarify how can I fix it? @duke
One thing, when git cloning the repo `install.sh` doesn't have enough permissions as `build.sh`
Here's the details:
```
-rwxrwxr-x 1 user user build.sh
-rw-rw-r-- 1 user user install.sh
```
We don't want to make users run `sudo chmod +x install.sh`, could you clarify how can I fix it? @duke
The below is the file that should be stored in
~/.local/share/applicationsin order to make a nice Hush SDL laucher with SD logo.install.shis the only one script that needs to be run in order to compile the software and moveSilentDragonLite.desktopSo if in the past we had to run something like
./build.sh linguist && ./build.sh && ./SilentDragonLiteand then manually create a launcher now we can just run./install.shIf you're okay with my solution
run-after-build.shcan be removed.Let me know if it makes sense. @duke
2b23bd7603into master 3 years ago@onryo looks useful, thanks! I would like to keep
run-after-build.shsince I use it to automate the running of SDL after a successful compile, which is slightly different.One thing, when git cloning the repo
install.shdoesn't have enough permissions asbuild.shHere's the details:
We don't want to make users run
sudo chmod +x install.sh, could you clarify how can I fix it? @duke@onryo do a
chmod +x install.shthengit add install.sh, then commit and push. Git keeps track of that stuffHm, I believe I've done it before pushing files, anyways it's done now, both on
masteranddevbranches. @duke2b23bd7603.