<div dir="ltr">Is there a gnome version?<br><br><div class="gmail_quote">On Thu, Aug 28, 2008 at 11:38 AM, Greg Hellings <span dir="ltr"><<a href="mailto:greg.hellings@gmail.com">greg.hellings@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Martin,<br>
<div class="Ih2E3d"><br>
On Thu, Aug 28, 2008 at 10:27 AM, Martin Gruner <<a href="mailto:mg.pub@gmx.net">mg.pub@gmx.net</a>> wrote:<br>
> Hi Greg,<br>
><br>
</div><div class="Ih2E3d">> after thinking about it a second time, we do use cmake for installation. The<br>
> shell scripts I mentioned only set some environment variables to further<br>
> automate the process. So I am not sure what you are referring to.<br>
<br>
</div>I was asking why Bibletime needed enough extra material and<br>
environment variables that it required the shell script and why those<br>
can't be worked up in the cmake structure directly? Bibletime surely<br>
is far from the most complicated thing with cmake that I've compiled,<br>
yet it's the only one that didn't maintain a pure cmake-style building<br>
system. You could just accept user-defined values for a variable<br>
named something like RELEASE and do the processing which is in the .sh<br>
script inside of the cmake, couldn't you? It surely would make the<br>
cross-platform goal of Qt, cmake and KDE much more attainable when<br>
you're on a system which lacks a native bash environment, and would<br>
also make the system easier for newcomers to build.<br>
<font color="#888888"><br>
--Greg<br>
</font><div><div></div><div class="Wj3C7c"><br>
><br>
> mg<br>
><br>
> Am Donnerstag, 28. August 2008 09:39:24 schrieb Greg Hellings:<br>
>> Martin,<br>
>><br>
>> On Thu, Aug 28, 2008 at 1:22 AM, Martin Gruner <<a href="mailto:mg.pub@gmx.net">mg.pub@gmx.net</a>> wrote:<br>
>> > Hi Greg,<br>
>> ><br>
>> > you cannot run build/bibletime because BT expects to start from its final<br>
>> > installation directory, so that it can find its data files by relative<br>
>> > path lookups. If you used build_debug.sh, run build/install/bin/bibletime<br>
>> > instead after "make install", in case of build_release.sh this would be<br>
>> > /usr/local/bin/bibletime.<br>
>><br>
>> I see. Is there a reason you use custom shell scripts instead of the<br>
>> normal cmake/make series? For cmake packages I usually build them in<br>
>> a separate directory from the source, seeing as that's what the cmake<br>
>> documents recommend when possible. Why not just include the creation<br>
>> of the necessary file structure and so on within the cmake?<br>
>><br>
>> --Greg<br>
>><br>
>> > Yes, we are trying to get rid of KDE dependencies. Sorry about the<br>
>> > trouble.<br>
>> ><br>
>> > God bless,<br>
>> ><br>
>> > mg<br>
>> ><br>
>> > am Donnerstag, 28. August 2008 um 02:09 schrieben Sie:<br>
>> >> Martin,<br>
>> >><br>
>> >> I have successfully built bibletime under Ubuntu 8.04 amd64 version.<br>
>> >> However, upon trying to run the executable, I am greeted with the<br>
>> >> following lovely message:<br>
>> >><br>
>> >> hellings1@ubuntu-desktop:~/Public/bibletime-1.7.beta1.build$ ./bibletime<br>
>> >> (BibleTime 1.7.beta1) WARNING: Cannot find icon directory relative to<br>
>> >> "/home/hellings1/Public/bibletime-1.7.beta1.build"<br>
>> >> terminate called without an active exception<br>
>> >> KCrash: crashing... crashRecursionCounter = 2<br>
>> >> KCrash: Application Name = bibletime path = <unknown> pid = 11112<br>
>> >> sock_file=/home/hellings1/.kde4/socket-ubuntu-desktop/kdeinit4__0<br>
>> >> Warning: connect() failed: : No such file or directory<br>
>> >> KCrash cannot reach kdeinit, launching directly.<br>
>> >> KCrash failed to exec(), errno = 2<br>
>> >><br>
>> >><br>
>> >> I have tried running "make install" but that doesn't seem to do much:<br>
>> >> hellings1@ubuntu-desktop:~/Public/bibletime-1.7.beta1.build$ sudo make<br>
>> >> install [sudo] password for hellings1:<br>
>> >> [100%] Built target bibletime<br>
>> >> Install the project...<br>
>> >> -- Install configuration: "RelWithDebInfo"<br>
>> >><br>
>> >> I also must say, the install/build dependencies are extremely steep.<br>
>> >> I already have a very hefty system from doing lots of other builds and<br>
>> >> development, and I was required to install about 2 GB of packages,<br>
>> >> etc, to build Bibletime. I sure hope you can get away from the KDE4<br>
>> >> dependency soon. In addition to that I needed Qt4.4, clucene and<br>
>> >> boost.<br>
>> >><br>
>> >> --Greg<br>
>> >><br>
>> >> On Wed, Aug 27, 2008 at 2:13 PM, Martin Gruner <<a href="mailto:mg.pub@gmx.net">mg.pub@gmx.net</a>> wrote:<br>
>> >>> Hi.<br>
>> >>><br>
>> >>> BibleTime 1.7.beta1 is out, basically the same as alpha4 with updated<br>
>> >>> message files for UI i18n.<br>
>> >>><br>
>> >>> This is BibleTime 1.7.beta1 for QT 4.4 and KDE 4.<br>
>> >>><br>
>> >>> Despite being labeled as beta, this version should be good for everyday<br>
>> >>> use and can be used as a basis for binary packages for the various<br>
>> >>> distributions.<br>
>> >>><br>
>> >>> Since 1.6, BibleTime has undergone major changes, which is why the<br>
>> >>> developers hesitate to release it as "final" yet, even though it seems<br>
>> >>> to be in a good shape.<br>
>> >>><br>
>> >>> @Ralph, Daniel and other packagers: please update the distribution's<br>
>> >>> binary packages with this new version, even though it is labeled as<br>
>> >>> beta.<br>
>> >>><br>
>> >>> @Joachim: Can you please post a big announcement on <a href="http://bibletime.info" target="_blank">bibletime.info</a>?<br>
>> >>> Please see the changelog for information you can use.<br>
>> >>><br>
>> >>> God bless you all.<br>
>> >>><br>
>> >>> Martin<br>
>> >>><br>
>> >>> _______________________________________________<br>
>> >>> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
>> >>> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
>> >>> Instructions to unsubscribe/change your settings at above page<br>
>> >><br>
>> >> _______________________________________________<br>
>> >> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
>> >> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
>> >> Instructions to unsubscribe/change your settings at above page<br>
>> ><br>
>> > --<br>
>> > Mit freundlichen Grüßen<br>
>> > Martin Gruner<br>
>> > mailto:<a href="mailto:mg.pub@gmx.net">mg.pub@gmx.net</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
>> > <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
>> > Instructions to unsubscribe/change your settings at above page<br>
>><br>
>> _______________________________________________<br>
>> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
>> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
>> Instructions to unsubscribe/change your settings at above page<br>
><br>
><br>
> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
><br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br></div>