I just saw this failure last night just before I retired for the evening.
Thanks for finding a solution before I got back to it!
--Greg
On Thu, Dec 31, 2020, 13:09 Troy A. Griffitts wrote:
> Dear Jaak,
>
> Thank you for reporting the problem. Yes, it looks like you have
> pointed out exactly t
Dear Jaak,
Thank you for reporting the problem. Yes, it looks like you have
pointed out exactly the problem. I've committed a small change to do
the svn revision lookup differently and to ignore any failures if not
building within an svn working copy. My apologies for the troubles.
Troy
On 1
Hello and Merry Christmas! :)
Today the BibleTime CI system started getting the following errors from
CMake when trying to build Sword:
CMake Error at cmake/options.cmake:75 (PROCESS_VERSION):
PROCESS_VERSION Macro invoked with incorrect arguments for macro
named:
PROCESS_VER
Chris,
This commit broke building with gcc on Fedora 18.
[ 0%] Building CXX object CMakeFiles/sword.dir/src/mgr/swmgr.cpp.o
/usr/bin/c++ -DGLOBCONFPATH=\"/sword.conf\" -D_FTPLIB_NO_COMPAT -D_ICU_
-Dsword_EXPORTS -g3 -Wall -O0 -fPIC -I/home/greg/Source/sword/include
-o CMakeFiles/sword.dir/sr
Seems to be better now. Thanks a lot!
mg
Am Dienstag, 19. Januar 2010 16:46:15 schrieb Troy A. Griffitts:
> We've attempted to tighten our spam control on our server. Please let
> us know if you have problems getting emails through to any of the lists.
> You can email me directly at: scribe at
On Apr 13, 2009, at 8:58 PM, Jonathan Marsden wrote:
I agree entirely. I think the bugtracker is a great tool for us.
(But it _sorely_ needs an update with respect to versions of Sword
that it recognizes.)
I'd think (hope) that any bugtracker admin can add new product
versions? If not
On Apr 13, 2009, at 5:31 PM, Chris Little wrote:
Jonathan Marsden wrote:
Matthew Talbert wrote:
I subscribe to sword-svn as an attempt to educate myself on the
library, and, of course, to keep track of current changes. It
would be
a real help to me if the commit messages were longer and mo
Quoting Chris Little :
It would greatly encourage use of the bug tracker if there was more
activity. Also, an rss feed might help (I'm not aware of one if there
is one already).
I agree entirely. I think the bugtracker is a great tool for us. (But
it _sorely_ needs an update with respect to ve
Chris Little wrote:
http://crosswire.org/bugs/browse/API-88
This bug was filed in 2007, but was resolved in 1.5.11 I believe, yet
it is still open.
In the strictest sense, this bug has been addressed. TEI filters do
exist. But I believe they still need significant improvement. We could
close
Matthew Talbert wrote:
The problem that I've had with that, is that it appears that the bug
tracker is not up-to-date and goes long periods with no activity. I
believe Peter mentioned this recently as well. A couple of examples:
I would say the tracker is fairly up to date (minus new bugs tha
> This scheme would work fine if folks would use the bugtracker (i.e. not
> report bugs only to sword-devel or in the wiki). When I fix things in the
> library that I notice myself, I don't tend to file a bug report before
> fixing them--I just fix them--and I would expect others who work on the
>
Jonathan Marsden wrote:
Matthew Talbert wrote:
I subscribe to sword-svn as an attempt to educate myself on the
library, and, of course, to keep track of current changes. It would be
a real help to me if the commit messages were longer and more
informative. As I am very new to a lot of the engin
Matthew Talbert wrote:
I subscribe to sword-svn as an attempt to educate myself on the
library, and, of course, to keep track of current changes. It would be
a real help to me if the commit messages were longer and more
informative. As I am very new to a lot of the engine stuff, it is hard
to te
I subscribe to sword-svn as an attempt to educate myself on the
library, and, of course, to keep track of current changes. It would be
a real help to me if the commit messages were longer and more
informative. As I am very new to a lot of the engine stuff, it is hard
to tell just by looking at the
Hi Chris,
IMHO the locales are already in Sword's SVN. I think it would be a bad idea to
maintain them in 2 places.
Am Samstag, 6. Oktober 2007 schrieb [EMAIL PROTECTED]:
> Author: chrislit
> Date: 2007-10-06 12:50:26 -0700 (Sat, 06 Oct 2007)
> New Revision: 102
>
> Added:
>trunk/modules/con
Troy
On 9/22/06, Troy A. Griffitts <[EMAIL PROTECTED]> wrote:
> Greg,
> What awesome debug information! Thank you for being so detailed and
> more so, for your persistence!
>
> I've heard we have cygwin compile problems and was hoping someone
> familiar with autotools and cygwin m
Greg,
What awesome debug information! Thank you for being so detailed and
more so, for your persistence!
I've heard we have cygwin compile problems and was hoping someone
familiar with autotools and cygwin might have a look and fix things.
I might be able to help with t
Fellow swords(wo)men,I have been trying to compile the latest SVN (as of this morning - I believe it's revision 1979) under Cygwin in Windows XP Pro. I've noticed the following oddities:1) When configured with the command:
CC="gcc -mno-cygwin" CXX="g++ -mno-cygwin" ./usrinst.sh --target=i686-pc-mi
Paul,
I'm not sure what you're asking:
1.7 = 1.5.7?
SVN doesn't have version numbers
apps directory?
_BibleCS_ now asks the engine for UTF-8 (by virtue of using ICUStringMgr)
I'd like to help, but I need more information.
-Troy.
Pham, Khoi wrote:
Troy,
I just downlo
Troy,
I just download sword 1.7 source from SVN, but it seems to miss the apps
subdirectory. Have you changed the files in the Apps subdirectory to
use utf8?
Paul Pham
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Troy A.
Griffitts
Sent: Wednesday, March
20 matches
Mail list logo
