/ Nuke Launcher for Linux (Centos) (.desktop)
Jorge Vidal
Installing Nuke on Linux doesn’t provide the icon launcher you have on Mac or Windows.
But you can manually create it.
I recommend this tips but you can go to step 2 for shorter version:
/ First of all. Create an alternative Nuke path.
I use to install the Nuke App outside my main local disk.
This way I get a faster and better gestion on upgrading every three months and save more space.
So, in my Workstation I download the .tgz compress app in my SSD (named SDT01)
and this will be my Nuke folder:
/run/media/user/SDT01/00_Apps_Backup/02_Nukes/Nuke13.0v2/Nuke13.0
If you don’t wanna do the same, just keep in mind the path you have on installing nuke.
/ 1. Editing my bashrc
Then I get this path line (/run/media/user/SDT01/00_Apps_Backup/02_Nukes/Nuke13.0v2/Nuke13.0)
into my .bashrc script (located in my home folder) here:
/home/user
and write down as it drives my Nuke directory:
alias n='/run/media/user/SDT01/00_Apps_Backup/02_Nukes/Nuke13.0v2/Nuke13.0 --NukeX -nc'
Creating this alias I can launch nuke just writing “n” on my console.
This is just useful and faster, and you can create your own alias, as “patata” or “sugarbaby” instead “n”
NOTE: For watching on graphical mode the .bashrc script, use COMAND + H, because is hidden by default.
The launch comands provide you different calls to Nuke and the way you wanna launch the application.
Also you can use it for launching Hiero, Nuke, Nuke X, etc.
I’m using Nuke X in non commercial mode (—NukeX -nc)
Go to the foundry for specific launch comands, or just remove -nc at the end.
/ 2. Creating my .desktop launcher
Now, I’m ready to create my .desktop launcher.
The .desktop launcher will be another script you need to create as root into this folder:
/usr/share/applications
This way you are creating a link to the app using a desktop icon as windows or Mac.
(Also works in any directory, so keet it in mind, you need to mark it as TRUST and Allow executing file as program )
The right way to write the file is:
[Desktop Entry]
Name=Nuke.13.0v2
Comment=Nuke desktop shortcut
Exec="/run/media/user/SDT01/00_Apps_Backup/02_Nukes/Nuke13.0v2/Nuke13.0" --NukeX -nc %F
Terminal=true
MimeType=application/x-nuke;
Icon=/run/media/user/SDT01/00_Apps_Backup/02_Nukes/Nuke13.0v2/plugins/icons/NukeApp48.png
Type=Application
Categories=Graphics;2DGraphics;RasterGraphics;FLTK;
Name[en_GB]=Nuke.desktop
As you can see, I’m writing my path on the Exec line.
Write your OWN real path, and name correctly your Nuke version. On updating Nuke you must to do it recursively.
(Remove -nc if you have license and don’t forget the %F at the end.)
Ok, now log out, this way you will get the changes on your App launcher.
NOTE: This .desktop file can be also created at ~/.local/share/applications in case you have differente users.
Take in mind that on launching the .desktop as root, you will be root user using Nuke. It is preferible to run it as another (non root) user, with non-Administrative privileges.
The .desktop file also can be pasted on your Desktop, this way you can grab your script to the icon and Nuke will open it.
As you can see, it works at any place. But because it is executable file you must take care of the permissions.
/ 3. Open scripts directly in graphical mode
Last step is go to your graphical and click one .nk script + right mouse button and select Open with Other Application.
If your Nuke.desktop is right you can find Nuke in the list and select as default launcher for .nk files.
Easy!!! Now every time you double click on .nk will open the app.
/ 4. Set your mine list
Some times, the .nk file is not recognizable by Centos, then you must edit the mine list.
The mine list is which tell Centos that Nuke run .nk files.
Your .desktop file will work without the mine list, but is better to have it setted.
Here you can find the right way, at The Foundry. I’ve screenshot the main instructions.
/ Final thoughts:
Of course, you can use this tip on any application, as Blender.desktop.
Manage your apps in external drives, much more easy to update.
In opposition they can made your workstation more vulnerable, but you can solve it adjusting privileges.