[sword-devel] BibleTime 1.7.beta1 is released - please create binary packages

Greg Hellings greg.hellings at gmail.com
Thu Aug 28 08:38:48 MST 2008


Martin,

On Thu, Aug 28, 2008 at 10:27 AM, Martin Gruner <mg.pub at gmx.net> wrote:
> Hi Greg,
>
> after thinking about it a second time, we do use cmake for installation. The
> shell scripts I mentioned only set some environment variables to further
> automate the process. So I am not sure what you are referring to.

I was asking why Bibletime needed enough extra material and
environment variables that it required the shell script and why those
can't be worked up in the cmake structure directly?  Bibletime surely
is far from the most complicated thing with cmake that I've compiled,
yet it's the only one that didn't maintain a pure cmake-style building
system.  You could just accept user-defined values for a variable
named something like RELEASE and do the processing which is in the .sh
script inside of the cmake, couldn't you?  It surely would make the
cross-platform goal of Qt, cmake and KDE much more attainable when
you're on a system which lacks a native bash environment, and would
also make the system easier for newcomers to build.

--Greg

>
> mg
>
> Am Donnerstag, 28. August 2008 09:39:24 schrieb Greg Hellings:
>> Martin,
>>
>> On Thu, Aug 28, 2008 at 1:22 AM, Martin Gruner <mg.pub at gmx.net> wrote:
>> > Hi Greg,
>> >
>> > you cannot run build/bibletime because BT expects to start from its final
>> > installation directory, so that it can find its data files by relative
>> > path lookups. If you used build_debug.sh, run build/install/bin/bibletime
>> > instead after "make install", in case of build_release.sh this would be
>> > /usr/local/bin/bibletime.
>>
>> I see.  Is there a reason you use custom shell scripts instead of the
>> normal cmake/make series?  For cmake packages I usually build them in
>> a separate directory from the source, seeing as that's what the cmake
>> documents recommend when possible.  Why not just include the creation
>> of the necessary file structure and so on within the cmake?
>>
>> --Greg
>>
>> > Yes, we are trying to get rid of KDE dependencies. Sorry about the
>> > trouble.
>> >
>> > God bless,
>> >
>> > mg
>> >
>> > am Donnerstag, 28. August 2008 um 02:09 schrieben Sie:
>> >> Martin,
>> >>
>> >> I have successfully built bibletime under Ubuntu 8.04 amd64 version.
>> >> However, upon trying to run the executable, I am greeted with the
>> >> following lovely message:
>> >>
>> >> hellings1 at ubuntu-desktop:~/Public/bibletime-1.7.beta1.build$ ./bibletime
>> >> (BibleTime 1.7.beta1) WARNING: Cannot find icon directory relative to
>> >> "/home/hellings1/Public/bibletime-1.7.beta1.build"
>> >> terminate called without an active exception
>> >> KCrash: crashing... crashRecursionCounter = 2
>> >> KCrash: Application Name = bibletime path = <unknown> pid = 11112
>> >> sock_file=/home/hellings1/.kde4/socket-ubuntu-desktop/kdeinit4__0
>> >> Warning: connect() failed: : No such file or directory
>> >> KCrash cannot reach kdeinit, launching directly.
>> >> KCrash failed to exec(), errno = 2
>> >>
>> >>
>> >> I have tried running "make install" but that doesn't seem to do much:
>> >> hellings1 at ubuntu-desktop:~/Public/bibletime-1.7.beta1.build$ sudo make
>> >> install [sudo] password for hellings1:
>> >> [100%] Built target bibletime
>> >> Install the project...
>> >> -- Install configuration: "RelWithDebInfo"
>> >>
>> >> I also must say, the install/build dependencies are extremely steep.
>> >> I already have a very hefty system from doing lots of other builds and
>> >> development, and I was required to install about 2 GB of packages,
>> >> etc, to build Bibletime.  I sure hope you can get away from the KDE4
>> >> dependency soon.  In addition to that I needed Qt4.4, clucene and
>> >> boost.
>> >>
>> >> --Greg
>> >>
>> >> On Wed, Aug 27, 2008 at 2:13 PM, Martin Gruner <mg.pub at gmx.net> wrote:
>> >>> Hi.
>> >>>
>> >>> BibleTime 1.7.beta1 is out, basically the same as alpha4 with updated
>> >>> message files for UI i18n.
>> >>>
>> >>> This is BibleTime 1.7.beta1 for QT 4.4 and KDE 4.
>> >>>
>> >>> Despite being labeled as beta, this version should be good for everyday
>> >>> use and can be used as a basis for binary packages for the various
>> >>> distributions.
>> >>>
>> >>> Since 1.6, BibleTime has undergone major changes, which is why the
>> >>> developers hesitate to release it as "final" yet, even though it seems
>> >>> to be in a good shape.
>> >>>
>> >>> @Ralph, Daniel and other packagers: please update the distribution's
>> >>> binary packages with this new version, even though it is labeled as
>> >>> beta.
>> >>>
>> >>> @Joachim: Can you please post a big announcement on bibletime.info?
>> >>> Please see the changelog for information you can use.
>> >>>
>> >>> God bless you all.
>> >>>
>> >>> Martin
>> >>>
>> >>> _______________________________________________
>> >>> sword-devel mailing list: sword-devel at crosswire.org
>> >>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> >>> Instructions to unsubscribe/change your settings at above page
>> >>
>> >> _______________________________________________
>> >> sword-devel mailing list: sword-devel at crosswire.org
>> >> http://www.crosswire.org/mailman/listinfo/sword-devel
>> >> Instructions to unsubscribe/change your settings at above page
>> >
>> > --
>> > Mit freundlichen Grüßen
>> > Martin Gruner
>> > mailto:mg.pub at gmx.net
>> >
>> >
>> > _______________________________________________
>> > sword-devel mailing list: sword-devel at crosswire.org
>> > http://www.crosswire.org/mailman/listinfo/sword-devel
>> > Instructions to unsubscribe/change your settings at above page
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>



More information about the sword-devel mailing list