View Single Post
Old 10-19-2014, 09:12 PM   #4
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,691
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Yes. The launcher root is expected (on Linux) to be found in the /share directory adjacent to the directory the Sigil binary is in. This will work "as is" if Sigil is installed to either of the "typical" /usr or /usr/local prefixes. If you relocate the binary (as I've done in my binary packages)--or the entire installation--to somewhere where that the typical ./bin ./share structure doesn't exist, then it will be necessary to set the launcher root directory manually via the SIGIL_PLUGIN_LAUNCHERS environment variable (either in your bash profile or the Sigil launch script).

I jump through the hoops I do with my binary package so that the Sigil.desktop file (/usr/local/share/applications) still functions as expected with regard to the various Linux Desktop Environments, their menus, and the "open with" context menus. Rather than launching from a terminal, the application launcher from the menu system can be easily copied to the desktop.

Last edited by DiapDealer; 10-19-2014 at 10:00 PM.
DiapDealer is offline   Reply With Quote