10-14-2014, 05:27 PM | #1 |
Connoisseur
Posts: 67
Karma: 10
Join Date: Sep 2014
Device: sony prs 2
|
sigil 0.8.1 building on linux
ok heres what i've done so far.
downloaded the qt online installer running as a user it installs to \home\user\Qt if you sudo it installs to opt/Qt a better location. http://www.cmake.org/download/ sudo /bin/sh cmake-3.0.2-Linux-i386.sh extracted the cmake files which i copied into /usr/ overwriting the 2.8 version of cmake this does not seem ideal but it works. i unpacked the sigil0.8.1 archive and created the build and run folders in there then in sigil-0.8.1/ cmake -G "Unix Makefiles" -DCMAKE_PREFIX_PATH=/opt/Qt/5.3/gcc/lib/cmake -DCMAKE_INSTALL_PREFIX=~/Sigil-0.8.1/run -DCMAKE_BUILD_TYPE=Release -DFORCE_BUNDLED_COPIES=1 ~/Sigil-0.8.1/ this built the config (few seconds really to do this) then ran make (i think i initially did this in Sigil-0.8.1/build/ ) and then make install only its not quite working i can click on the sigil binary and it works but its not in my path I tried check install but that fails. Can anyone help me build it properly? cheers |
10-14-2014, 05:49 PM | #2 |
Grand Sorcerer
Posts: 27,993
Karma: 199013032
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
I think you have it built properly if it runs. It doesn't need to be in your path to work.
If you want it to be in your path then either create a symlink in /usr/bin or /usr/local/bin to the sigil binary in your ~/Sigil-0.8.1/run/bin folder, or eliminate the "-DCMAKE_INSTALL_PREFIX=~Sigil-0..8.1/run" from your original cmake command and use: "sudo make install" to install Sigil to the /usr/local prefix. The Sigil binary (/usr/local/bin/sigil) will be in your path. |
Advert | |
|
10-14-2014, 06:08 PM | #3 |
Ex-Helpdesk Junkie
Posts: 19,421
Karma: 85397180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
Yeah, installing it into the ~/Sigil-0.8.1/run/ folder will put the binary in the bin/ folder of the install location.
compiling programs into $HOME will always require you to setup the path manually. |
10-15-2014, 03:59 AM | #4 | |
Connoisseur
Posts: 67
Karma: 10
Join Date: Sep 2014
Device: sony prs 2
|
Quote:
/usr/local/bin/sigil is a script which sets up the qt lib locations and then runs /usr/local/share/sigil/sigil-real There is also a warn on compilation "/src/Sigil/Misc/PluginDB.cpp:101:18: warning: unused variable ‘plugin’ [-Wunused-variable] Plugin *plugin; " cheers other than that it seems without problems. |
|
10-15-2014, 06:47 AM | #5 | ||
Grand Sorcerer
Posts: 27,993
Karma: 199013032
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
Quote:
|
||
Advert | |
|
10-15-2014, 06:53 AM | #6 |
Wizard
Posts: 4,520
Karma: 121692313
Join Date: Oct 2009
Location: Heemskerk, NL
Device: PRS-T1, Kobo Touch, Kobo Aura
|
|
10-15-2014, 08:00 AM | #7 |
Grand Sorcerer
Posts: 27,993
Karma: 199013032
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Dangerous? Hardly. The worst that can happen is the program won't work. In all my years of compiling stuff on Linux, I've never really encountered a warning that affected the final result -- IF the compilation process ultimately finished successfully. And I've rarely compiled any large projects where there weren't warnings along the way (especially with code that's going to be compiled with multiple compilers on multiple platforms). Cavalier?? Possibly ... but not dangerous. Especially when I'm familiar with blackest's particular warning and know that it can be safely ignored. So I have no problem telling anyone who ended up with a functioning version of Sigil that they can ignore any warnings they may have encountered during compilation. Welcome to cross-platform compilation.
Perhaps I should have said; "ignore them until they won't allow you to ignore them any more," but that seems like a given to me. *shrug* Last edited by DiapDealer; 10-15-2014 at 08:47 AM. |
10-15-2014, 01:57 PM | #8 |
Wizard
Posts: 4,520
Karma: 121692313
Join Date: Oct 2009
Location: Heemskerk, NL
Device: PRS-T1, Kobo Touch, Kobo Aura
|
Well, not quite. Perhaps in this case it cannot do much harm, but I have experience otherwise for other programs. In those cases there was usually also a warning about a missing library or function but the program compiled and did run. However, there was a major issue with the programs and a big loss of data as a result... A warning is not always a warning.
In this particular case I totally agree with you, it is not important and indeed there are almost always warnings. However, unless you are familiar with the warnings, investigation should be done. |
10-15-2014, 02:38 PM | #9 |
Grand Sorcerer
Posts: 27,993
Karma: 199013032
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Fair enough. Further investigation is never going to hurt someone in any case.
|
10-15-2014, 06:22 PM | #10 | |
Connoisseur
Posts: 67
Karma: 10
Join Date: Sep 2014
Device: sony prs 2
|
Quote:
maybe it was a left over from an experiment or it is needed on another platform. The sigil source is very clean (just one warning seems to be exceptional in most projects). i only really mentioned it for completeness. sigil feels rock solid in this update. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Building Sigil from source on Linux | xingenter | Sigil | 10 | 04-29-2013 01:18 PM |
Sigil build on Linux | vepo | Sigil | 1 | 03-16-2013 11:59 AM |
Building a running Linux on M92 from scratch | ManDay | Onyx Boox | 1 | 01-21-2013 11:11 AM |
Problems building Sigil on Win7/64 | Man Eating Duck | Sigil | 11 | 10-03-2012 02:51 PM |
Building Sigil under Linux | st_albert | Sigil | 1 | 08-07-2011 03:19 PM |