Tutorial  Updated

L4T Ubuntu Applcation Install guides.

So, instead of clogging up poor @bylaws L4T thread (sorry buddy!) with emulators apps, I figured it might be a good idea to try and make a separate thread for quick guides, and leave his one to troubleshooting actual L4T issues.

The intent for this thread is to leave behind quickshot guides for others to install applications we know works for Tegra Linux, so here's the one's I've managed so far, with the help of some folks in the L4T OS thread.

If others are going to add to this thread with their own little guides, try to keep each seperate command on it's own line, and if the command is too big for 1 line, seperate it as I have done in the Vulkan Dolphin guide. Little comments should go into square brackets and have the color changed to red. Try to keep it in a format that people can copy/paste each line as they're needed.

(It is advised to make a Swapfile, so please follow that guide first!)

sudo apt install nano
[You can change 1G to whatever size you want, I used 2G]
sudo fallocate -l 1G /swapfile
[If fallocate throws an error, you want to run the]
[next command, if it doesn't, skip it]

sudo dd if=/dev/zero of=/swapfile bs=1024 count=1048576
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
sudo nano /etc/fstab
[You need to add this entry to the file you just opened]
[to make the change permanent:]

/swapfile swap swap defaults 0 0
[To verify that it installed correctly:]
sudo free -h
[Something like this should be the output:]

       [total        used         free       shared  buff/cache  available]
[Mem: 488M 158M 83M 2.3M 246M 217M]
[Swap: 1.0G 506M 517M]

echo performance | sudo tee /sys/devices/system/cpu/cpufreq/policy0/scaling_governor

sudo add-apt-repository ppa:dolphin-emu/ppa
sudo apt-get update
git clone https://github.com/Tinob/Ishiiruka.git
cd Ishiiruka
mkdir build
cd build

[This next line is all in one, so copy/paste]
sudo apt install git cmake ffmpeg libavcodec-dev libevdev-dev libusb-1.0-0-dev libavformat-dev libswscale-dev libsfml-dev libminiupnpc-dev libmbedtls-dev curl libhidapi-dev libwxbase3.0-dev libwxgtk3.0-dev libpangocairo-1.0-0 libgtk2.0-dev libbluetooth-dev qt5-default qtbase5-private-dev libudev-dev libxi-dev

cmake ..
make -j4
sudo make install

[Once installed, execute with]
ishiiruka
[Then lock it to the sidebar for easy access]

sudo add-apt-repository ppa:libretro/testing
sudo apt-get install retroarch* libretro*
sudo apt-get update && sudo apt-get upgrade
[Easy enough to install]

sudo apt-get install xserver-xorg-input-joystick

[To use your joycons as a mouse, press the sync buttons on the rail of each joycon, then use the bluetooth app to connect to them both. Once both are connected, hold them like you normally do, and press L+R (L1, R1 in Playstation terms), and that should be it!]
[Another easy install, to change sensitivity, go to system settings, mouse, and make your changes]

sudo apt-get install kodi
[After installing Kodi, you will need to logout. Do not shut down or reboot, but if you did, follow the same instructions.]
[Log out, and you'll be at the login menu. Click the account, and it'll ask you for your password.]
[Underneath the password box, is a cog. Click the cog, and click Unity.]
[From now on, Kodi will not automatically start upon booting up linux.]
[Yet another easy one, but this is a very powerful media box program]

[Original Post https://gbatemp.net/threads/tutoria...ling-moonlight-embedded-on-l4t-ubuntu.537429/ ]
sudo apt-get update
[Next line is all 1 command]
sudo apt-get install libopus0 libexpat1 libasound2 libudev1 libavahi-client3 libcurl3 libevdev2 libenet7 -y && sudo apt-get install libssl-dev libopus-dev libasound2-dev libudev-dev libavahi-client-dev libcurl4-openssl-dev libevdev-dev libexpat1-dev libpulse-dev uuid-dev libenet-dev cmake gcc g++ fakeroot debhelper
libavcodec-dev libsdl2-dev -y

git clone https://github.com/irtimmer/moonlight-embedded.git
cd moonlight-embedded
git submodule update --init
mkdir build
cd build/
cmake ../
make
sudo make install
sudo ldconfig

[Now reboot your switch]
moonlight pair <pc local ip>
moonlight stream <pc local ip>

[Where pc local ip, you must put in your pc's ip address. To find that, on windows, open Win+r, in the dialog box, put in cmd.exe. In the new window, type in ipconfg, then look for your systems ip address. if you computer is wired to your network, it'll fall under "Ethernet adapter Ethernet".
If it is Wireless, then it'll fall under "Wireless LAN adapter WiFi"
Either way, you'll want the IPv4 Address.]
[In linux, just open terminal, the command "ifconfig" and look for IPv4]


[To configure your joycons to work with Moonlight]
sudo gedit /usr/local/share/moonlight/gamecontroller.txt

[Scroll to the bottom and copy/paste one of these style codes into the file]
[For Nintendo Style:]
050000007e0500000620000001000000,Nintendo Switch Joy-Cons,a:b1,b:b0,back:b9,dpdown:b15,dpleft:b16,dpright:b17,dpup:b14,guide:b11,leftshoulder:b5,leftstick:b12,lefttrigger:b7,leftx:a0,lefty:a1,rightshoulder:b6,rightstick:b13,righttrigger:b8,rightx:a2,righty:a3,start:b10,x:b2,y:b3,

[For Microsoft Style:] 050000007e0500000620000001000000,Nintendo Switch Joy-Cons,a:b0,b:b1,back:b9,dpdown:b15,dpleft:b16,dpright:b17,dpup:b14,guide:b11,leftshoulder:b5,leftstick:b12,lefttrigger:b7,leftx:a0,lefty:a1,rightshoulder:b6,rightstick:b13,righttrigger:b8,rightx:a2,righty:a3,start:b10,x:b3,y:b2,

[Then,press CTRL + X. Then press Y. Then close terminal and reboot your switch.]
 
Last edited by ,
D

Deleted User

Guest
OP
Hangover Installation Tutorial

1. Get L4T running on your Switch and connect to network. Going to assume you have the basics down. I had to reflash my SD card because I screwed up the DE so I'm writing this tutorial off of a fresh install.

2. Install required dependencies: sudo apt-get install git build-essential mingw-w64 mingw-w64-i686-dev mingw-w64-x86-64-dev libfreetype6-dev

3. Clone the Hangover repository: git clone <link removed because this forum is dumb, google "wine hangover github" and you'll find it>

4. cd into the hangover directory: cd hangover

5. Initialize submodules: git submodule update --init --recursive

6. Both times I've tried to build this, the qemu submodule seems to initialize to an empty commit. To fix this, cd into the qemu directory and reset: git reset --hard HEAD

7. cd back up to the hangover directory: cd ..

5. Build the project: make -j4

6. Rerun make -j4 until there are no errors. You may want to enable the overclock/performance mode for this step as it will take a while.

7. Symlink libgcc_s_sjlj-1.dll into hangover build: ln -s /usr/lib/gcc/i686-w64-mingw32/7.3-win32/libgcc_s_sjlj-1.dll build/qemu/x86_64-windows-user/qemu_guest_dll32/libgcc_s_sjlj-1.dll


kind sir who have already done so much for me can you help me with this 7. step in terms of command and how would i run winmugen using this power?
actually edit i figured that out just how would i run an exe once it's installed?
 
Last edited by ,

tansoftware

Active Member
Newcomer
Joined
Apr 15, 2019
Messages
36
Trophies
0
Age
42
XP
351
Country
Canada
@tansoftware @nabelo

I am going to share how to install gzdoom
I wish the person who originally posted the successful compile would have shared the super simple answer that the wiki "told him todo" meanwhile it did not, it does not go into arm Linux. You need to know, fmodapilinux is for x32 architecture when fmodapiandroid which is for arm and the one you want.

STEP 1: Install the dependency files, this can all be pasted in all at once in terminal:
sudo apt-get install g++ make cmake libsdl2-dev git zlib1g-dev \
libbz2-dev libjpeg-dev libfluidsynth-dev libgme-dev libopenal-dev \
libmpg123-dev libsndfile1-dev libwildmidi-dev libgtk-3-dev timidity nasm \
libgl1-mesa-dev tar libsdl1.2-dev libglew-dev

STEP 2: Create the build directory
mkdir -pv ~/gzdoom_build

STEP 3: Get the git of gzdoom
cd ~/gzdoom_build &&
git clone git://github.com/coelckers/gzdoom.git &&
mkdir -pv gzdoom/build

Then run these three commands:
cd gzdoom

git config --local --add remote.origin.fetch +refs/tags/*:refs/tags/*

git pull

STEP 4: FMOD...
Gzdoom needs fmod, there's options on the wiki to disable fmod SOUND but that still does not eliminate need for FMODapi. The wiki does not explain that FMOD needs to be the android version for arm support. To get this and have it setup you need to do the following commands:

cd ~/gzdoom_build &&
wget -nc https://zdoom.org/files/fmod/fmodapi43623android.tar.gz &&
tar -xvzf fmodapi43623android.tar.gz -C gzdoom

STEP 5: Compile
Paste this all in at once in the terminal:
a='' && [ "$(uname -m)" = x86_64 ] && a=64
c="$(lscpu -p | grep -v '#' | sort -u -t , -k 2,4 | wc -l)" ; [ "$c" -eq 0 ] && c=1
cd ~/gzdoom_build/gzdoom/build &&
rm -f output_sdl/liboutput_sdl.so &&
if [ -d ../fmodapi43623android ]; then
f="-DFMOD_LIBRARY=../fmodapi43623android/api/lib/libfmodex${a}-4.44.64.so \
-DFMOD_INCLUDE_DIR=../fmodapi43623android/api/inc"; else
f='-UFMOD_LIBRARY -UFMOD_INCLUDE_DIR'; fi &&
cmake .. -DCMAKE_BUILD_TYPE=Release $f &&
make -j$c

STEP 6: Setup GZDOOM & Profit
copy your wads and iwads to ~/.config/gzdoom if you can't find it press CTRL+H to show hidden folders.
after that go back to the build folder/your terminal and type ./gzdoom
it should startup with a wad.
the wiki goes into how to install gzdoom into the system finder here I tested to make sure this step works and it does.

@coppertj

I can't thank you enough :-)
 
  • Like
Reactions: nabelo

tansoftware

Active Member
Newcomer
Joined
Apr 15, 2019
Messages
36
Trophies
0
Age
42
XP
351
Country
Canada
@tansoftware @nabelo

I am going to share how to install gzdoom
I wish the person who originally posted the successful compile would have shared the super simple answer that the wiki "told him todo" meanwhile it did not, it does not go into arm Linux. You need to know, fmodapilinux is for x32 architecture when fmodapiandroid which is for arm and the one you want.

STEP 1: Install the dependency files, this can all be pasted in all at once in terminal:
sudo apt-get install g++ make cmake libsdl2-dev git zlib1g-dev \
libbz2-dev libjpeg-dev libfluidsynth-dev libgme-dev libopenal-dev \
libmpg123-dev libsndfile1-dev libwildmidi-dev libgtk-3-dev timidity nasm \
libgl1-mesa-dev tar libsdl1.2-dev libglew-dev

STEP 2: Create the build directory
mkdir -pv ~/gzdoom_build

STEP 3: Get the git of gzdoom
cd ~/gzdoom_build &&
git clone git://github.com/coelckers/gzdoom.git &&
mkdir -pv gzdoom/build

Then run these three commands:
cd gzdoom

git config --local --add remote.origin.fetch +refs/tags/*:refs/tags/*

git pull

STEP 4: FMOD...
Gzdoom needs fmod, there's options on the wiki to disable fmod SOUND but that still does not eliminate need for FMODapi. The wiki does not explain that FMOD needs to be the android version for arm support. To get this and have it setup you need to do the following commands:

cd ~/gzdoom_build &&
wget -nc https://zdoom.org/files/fmod/fmodapi43623android.tar.gz &&
tar -xvzf fmodapi43623android.tar.gz -C gzdoom

STEP 5: Compile
Paste this all in at once in the terminal:
a='' && [ "$(uname -m)" = x86_64 ] && a=64
c="$(lscpu -p | grep -v '#' | sort -u -t , -k 2,4 | wc -l)" ; [ "$c" -eq 0 ] && c=1
cd ~/gzdoom_build/gzdoom/build &&
rm -f output_sdl/liboutput_sdl.so &&
if [ -d ../fmodapi43623android ]; then
f="-DFMOD_LIBRARY=../fmodapi43623android/api/lib/libfmodex${a}-4.44.64.so \
-DFMOD_INCLUDE_DIR=../fmodapi43623android/api/inc"; else
f='-UFMOD_LIBRARY -UFMOD_INCLUDE_DIR'; fi &&
cmake .. -DCMAKE_BUILD_TYPE=Release $f &&
make -j$c

STEP 6: Setup GZDOOM & Profit
copy your wads and iwads to ~/.config/gzdoom if you can't find it press CTRL+H to show hidden folders.
after that go back to the build folder/your terminal and type ./gzdoom
it should startup with a wad.
the wiki goes into how to install gzdoom into the system finder here I tested to make sure this step works and it does.

@coppertj

I followed your instructions to the letter, and was able to compile the gzdoom file, but when executing it, I still get the same error:

------------------------------------------------------------------------------------------------------------
terry@terry-switch:~/gzdoom_build/gzdoom/build$ ./gzdoom
GZDoom g4.2pre-44-gcace5079f - 2019-05-09 16:06:18 +0200 - SDL version
Compiled on May 9 2019

M_LoadDefaults: Load system defaults.
W_Init: Init WADfiles.
adding /home/terry/gzdoom_build/gzdoom/build/gzdoom.pk3, 621 lumps
adding /home/terry/gzdoom_build/gzdoom/build/zd_extra.pk3, 1657 lumps
adding /home/terry/.config/gzdoom/TNT.WAD, 3101 lumps
I_Init: Setting up machine state.
I_InitSound: Initializing OpenAL
Opened device Built-in Audio Speaker playback + Headphones playback
EFX enabled
V_Init: allocate screen.
S_Init: Setting up sound.
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
script parsing took 470.52 ms
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)

dbus[24884]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.

D-Bus not built with -rdynamic so unable to print a backtrace
Aborted (core dumped)
------------------------------------------------------------------------------------------------------------

I'm not sure why this is happening... I even tried compiling gzdoom on a clean ubuntu img, but I still get the same error, is there something I'm missing ?
 

specht

Well-Known Member
Member
Joined
Oct 26, 2008
Messages
234
Trophies
1
XP
917
Country
Canada
@coppertj

I followed your instructions to the letter, and was able to compile the gzdoom file, but when executing it, I still get the same error:

------------------------------------------------------------------------------------------------------------
terry@terry-switch:~/gzdoom_build/gzdoom/build$ ./gzdoom
GZDoom g4.2pre-44-gcace5079f - 2019-05-09 16:06:18 +0200 - SDL version
Compiled on May 9 2019

M_LoadDefaults: Load system defaults.
W_Init: Init WADfiles.
adding /home/terry/gzdoom_build/gzdoom/build/gzdoom.pk3, 621 lumps
adding /home/terry/gzdoom_build/gzdoom/build/zd_extra.pk3, 1657 lumps
adding /home/terry/.config/gzdoom/TNT.WAD, 3101 lumps
I_Init: Setting up machine state.
I_InitSound: Initializing OpenAL
Opened device Built-in Audio Speaker playback + Headphones playback
EFX enabled
V_Init: allocate screen.
S_Init: Setting up sound.
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
script parsing took 470.52 ms
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)

dbus[24884]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.

D-Bus not built with -rdynamic so unable to print a backtrace
Aborted (core dumped)
------------------------------------------------------------------------------------------------------------

I'm not sure why this is happening... I even tried compiling gzdoom on a clean ubuntu img, but I still get the same error, is there something I'm missing ?

Try this command before running the executable:

export DBUS_FATAL_WARNINGS=0

It worked for OpenMW at least.
 

coppertj

Well-Known Member
Member
Joined
May 26, 2017
Messages
193
Trophies
0
Age
25
XP
482
Country
United States
@tansoftware hm it must have been something inside the dolphin packages I downloaded, I must have lucked out and that's installed most the arm versions of the dependencies. I am at work now but I can rewrite the dependency apt-get list when I get home. For now though you may want to try downloading all the dependencies in the dolphin guide and then try recompile

Edit: sorry for the trouble but it should 99.99% work after that. The reason is because that's the only dependencies I've downloaded/only other thing I compiled on my Linux (besides gzdoom) process of elimination says that whatever is failing to build is in that list
 
Last edited by coppertj,

WuskyDingo

Active Member
Newcomer
Joined
Jun 2, 2018
Messages
26
Trophies
0
Location
San Diego, CA
Website
www.youtube.com
XP
122
Country
United States
@tansoftware @nabelo

I am going to share how to install gzdoom
I wish the person who originally posted the successful compile would have shared the super simple answer that the wiki "told him todo" meanwhile it did not, it does not go into arm Linux. You need to know, fmodapilinux is for x32 architecture when fmodapiandroid which is for arm and the one you want.

STEP 1: Install the dependency files, this can all be pasted in all at once in terminal:
sudo apt-get install g++ make cmake libsdl2-dev git zlib1g-dev \
libbz2-dev libjpeg-dev libfluidsynth-dev libgme-dev libopenal-dev \
libmpg123-dev libsndfile1-dev libwildmidi-dev libgtk-3-dev timidity nasm \
libgl1-mesa-dev tar libsdl1.2-dev libglew-dev

STEP 2: Create the build directory
mkdir -pv ~/gzdoom_build

STEP 3: Get the git of gzdoom
cd ~/gzdoom_build &&
git clone git://github.com/coelckers/gzdoom.git &&
mkdir -pv gzdoom/build

Then run these three commands:
cd gzdoom

git config --local --add remote.origin.fetch +refs/tags/*:refs/tags/*

git pull

STEP 4: FMOD...
Gzdoom needs fmod, there's options on the wiki to disable fmod SOUND but that still does not eliminate need for FMODapi. The wiki does not explain that FMOD needs to be the android version for arm support. To get this and have it setup you need to do the following commands:

cd ~/gzdoom_build &&
wget -nc https://zdoom.org/files/fmod/fmodapi43623android.tar.gz &&
tar -xvzf fmodapi43623android.tar.gz -C gzdoom

STEP 5: Compile
Paste this all in at once in the terminal:
a='' && [ "$(uname -m)" = x86_64 ] && a=64
c="$(lscpu -p | grep -v '#' | sort -u -t , -k 2,4 | wc -l)" ; [ "$c" -eq 0 ] && c=1
cd ~/gzdoom_build/gzdoom/build &&
rm -f output_sdl/liboutput_sdl.so &&
if [ -d ../fmodapi43623android ]; then
f="-DFMOD_LIBRARY=../fmodapi43623android/api/lib/libfmodex${a}-4.44.64.so \
-DFMOD_INCLUDE_DIR=../fmodapi43623android/api/inc"; else
f='-UFMOD_LIBRARY -UFMOD_INCLUDE_DIR'; fi &&
cmake .. -DCMAKE_BUILD_TYPE=Release $f &&
make -j$c

STEP 6: Setup GZDOOM & Profit
copy your wads and iwads to ~/.config/gzdoom if you can't find it press CTRL+H to show hidden folders.
after that go back to the build folder/your terminal and type ./gzdoom
it should startup with a wad.
the wiki goes into how to install gzdoom into the system finder here I tested to make sure this step works and it does.

I did not need the android fmod at all. Straight compile of the source as the git said worked 100% fine for me, hence my simple reply. not sure what happened to y'all. Maybe my source code is different?
 

WuskyDingo

Active Member
Newcomer
Joined
Jun 2, 2018
Messages
26
Trophies
0
Location
San Diego, CA
Website
www.youtube.com
XP
122
Country
United States
Anyone had any luck with Citra? I compiled & installed but can not get it to open.

This is as far as I got:
Sca8ksg.png
 

skinnyBIGGS

Well-Known Member
Newcomer
Joined
Apr 2, 2019
Messages
89
Trophies
0
Age
41
XP
605
Country
Canada
Any way you could direct me to the linux version to use.. thnx great write up loved linux on ps3 before jailbreak i had vlc media player as ps3s was garbage ..and had emus..had ylod returned to sony and the bastards erased it .. this was prior to removal of linux 3.15...
 

mathew77

Lovin' life.
Member
Joined
Jan 19, 2019
Messages
1,183
Trophies
0
Age
47
XP
3,672
Country
Kazakhstan
Good day! I successfully installed xserver-xorg-input-joystick, but is there any configuration file to edit it, for example, to map cursor movement on the right stick?
Thanks!
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    S @ salazarcosplay: no character has quite claimed the mascot for sony