Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<h2>The basics</h2> <p>(disclaimer: the following was tested with kubuntu, you might need to make some adjustments for your system)</p> <p>Actually there is a standard to do that, not just for Ubuntu but for any number of *nix systems. Consult: <a href="http://www.freedesktop.org/wiki/Howto_desktop_files" rel="nofollow noreferrer">http://www.freedesktop.org/wiki/Howto_desktop_files</a>:</p> <p>Lets assume you have your <code>foo.bin</code> file you want to deploy. According to the <a href="http://www.pathname.com/fhs/" rel="nofollow noreferrer">Filesystem Hierarchy Standard</a>, a good place to put it (if you are not using a package manager) is <code>/usr/local/bin/</code>. You will also need an icon, I will assume your artistic talent produced <code>foo.png</code>, and a good place for it might be <code>/usr/local/share/icons/</code>.</p> <p>Now you need to create <code>foo.desktop</code> that might look like this:</p> <pre><code>[Desktop Entry] Comment=My awesome fooish application Exec=/usr/local/bin/foo.bin Icon=/usr/local/share/icons/foo.png Name=Foobar NoDisplay=false StartupNotify=false Terminal=1 TerminalOptions= Type=Application </code></pre> <p>and put it in <code>/usr/share/applications/</code>.</p> <p>You might be able to use your menu editor to create such a file. Look for the generated desktop file under <code>~/.local/share/applications/</code>.</p> <p>This should do the trick.</p> <hr> <p>Another convention is to put everything under <code>/opt/foo/</code> and create symbolic links to <code>/usr/local/</code>.</p> <h1>Cross DE with Portland</h1> <p>The <a href="http://en.wikipedia.org/wiki/Portland_Project" rel="nofollow noreferrer">Portland project</a> provides the <code>xdg-*</code> command line utilities that make it easy to install the application's icon / menu entry / resource file, in a DE (GNOME, KDE, etc) independent way.</p> <p>See the <a href="http://www.linuxuser.co.uk/tutorials/kde-gnome-cross-desktop-development/" rel="nofollow noreferrer">KDE &amp; GNOME cross-desktop development tutorial</a> on linuxuser.co.uk.</p> <h1>A better way</h1> <p>For deployment you should consider creating a <code>*.deb</code> package. (with your executable, <code>*.desktop</code> file and icon). There are several tutorials on this subject e.g. <a href="http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/How-to-make-deb-packages/" rel="nofollow noreferrer">http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/How-to-make-deb-packages/</a>.</p> <p>Note that if you are using a package manager, the convention for file location becomes <code>/usr/</code> instead of <code>/usr/local/</code>.</p> <h1>Go all the way</h1> <p>The next step, if you are inclined to take it, is setup your own repository, or <a href="https://launchpad.net/ubuntu/+ppas" rel="nofollow noreferrer">PPA</a>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload