date:20130124


On Jan 23, 2013, at 12:05:20PM, Manfred Bergmann manfred.bergm...@me.com 
wrote:

 Just out of curiosity, what do you need the objc wrappers for?
 

Just want to play around with the API. Develop a simple client. Curiosity while 
I learn to code in Objective-C/Cocoa.

Jeff


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken


On Jan 23, 2013, at 2:21:09PM, Manfred Bergmann manfred.bergm...@me.com wrote:

 
 OK. Can you upgrade to Lion at least?
 That would probably be the easiest because the this Xcode project is 
 maintained.
 

Last night, while we were asleep, my wife poked me in the eye when she rolled 
over. I upgraded to Mountain Lion today. I must say, the poke in the eye was 
less painful. It only lasted a few minutes.

Gcc? gone
Java? gone
XCode? gone
Subversion client? gone
XWindows?

Well, you get the idea. But now, I've got the new Xcode and I'm building 
ObjCSword. So far it's been about 15 minutes… (Not counting the 2 hour download 
/ install / fix of Mountain Lion)

More to follow.
Jeff


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

2013-01-24 Thread Jeff Barnes



Sent from my iPhone

On Jan 23, 2013, at 4:20 PM, Manfred Bergmann manfred.bergm...@me.com wrote:

 
 Well, you know how Apple is. Much changes, especially over on two major 
 versions.
 Many things have their advantages. Installing Xcode over App Store is pretty 
 much painless (except the download). You get gcc, subversion, git and many 
 other goodies once you've installed it.
 The OS X Java port is now maintained by Oracle which IMO is a good thing as 
 well.
 
 
 Manfred

I downloaded fink to get gcc. I read all the blogs, etc. that said gcc doesn't 
come with Xcode anymore. Did I misread something? 
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

2013-01-24 Thread Trevor Jenkins

On 23 Jan 2013, at 22:21, Jeff Barnes jbarnes...@gmail.com wrote:

 I downloaded fink to get gcc. I read all the blogs, etc. that said gcc 
 doesn't come with Xcode anymore. Did I misread something? 

The gcc compiler is no longer shipped with Xcode. Instead it comes with the 
LLVM project's reworking of it. http://llvm.org/ and 
https://developer.apple.com/library/mac/#documentation/CompilerTools/Conceptual/LLVMCompilerOverview/_index.html
 The claim is that LLVM produces better object code than its gcc equivalent. 
The Xcode command line tools options will expose the installed compiler and 
linker for use outside of Xcode, e.g. for hacking with eclipse.

Regards, Trevor.

 Re: deemed!


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Location of prebuilt lucene indexes.

2013-01-24 Thread David Haslam

*And Bible* allows the user to create the search index for a module if it
does not already exist.

This is useful in these situations:

(a) The user is currently not [reliably] connected to the Internet,
(b) Martin has not yet made the downloadable index for new/updated modules.

And Bible does not have a UI option to remove a search index, 
though this could be done manually by means of the file system, 
assuming you know where to look within the Android directory structure.

David





--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Location-of-prebuilt-lucene-indexes-tp4651756p4651788.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Location of prebuilt lucene indexes.

2013-01-24 Thread Martin Denham

Hi David,

To delete an index in And Bible you long-press the desired module in the
Documents list to reveal module and index delete actions in the context
menu.

Martin

On 24 January 2013 12:36, David Haslam dfh...@googlemail.com wrote:

 *And Bible* allows the user to create the search index for a module if it
 does not already exist.

 This is useful in these situations:

 (a) The user is currently not [reliably] connected to the Internet,
 (b) Martin has not yet made the downloadable index for new/updated modules.

 And Bible does not have a UI option to remove a search index,
 though this could be done manually by means of the file system,
 assuming you know where to look within the Android directory structure.

 David





 --
 View this message in context:
 http://sword-dev.350566.n4.nabble.com/Location-of-prebuilt-lucene-indexes-tp4651756p4651788.html
 Sent from the SWORD Dev mailing list archive at Nabble.com.

 ___
 sword-devel mailing list: sword-devel@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

2013-01-24 Thread Jeff Barnes

- Original Message -
 From: Manfred Bergmann manfred.bergm...@me.com
 To: Jeff Barnes jbarnes...@gmail.com
 Cc: SWORD Developers' Collaboration Forum sword-devel@crosswire.org
 Sent: Thursday, January 24, 2013 1:25 AM
 Subject: Re: [sword-devel] bindings/objc build broken
  I downloaded fink to get gcc. I read all the blogs, etc. that said gcc 
 doesn't come with Xcode anymore. Did I misread something?

 No need to do that. As Nic pointed out, the command line tools can be 
 installed 
 from Xcode Preferences.
 And unless you want to compile something from command line directly via 
 issuing 
 gcc you don't need the command line tools to build Xcode projects.

 Manfred

I need gcc for the rest of the world ex-mac. Not sure, but I think I need gcc 
to compile the Sword project trunk tip. No?

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

On Jan 23, 2013, at 3:54:32PM, Barnes, Jeffrey jbarnes...@gmail.com wrote:

On Jan 23, 2013, at 2:21:09PM, Manfred Bergmann manfred.bergm...@me.com
wrote:

OK. Can you upgrade to Lion at least?
That would probably be the easiest because the this Xcode project is
maintained.

Last night, while we were asleep, my wife poked me in the eye when she rolled
over. I upgraded to Mountain Lion today. I must say, the poke in the eye was
less painful. It only lasted a few minutes.

Gcc? gone
Java? gone
XCode? gone
Subversion client? gone
XWindows?

Well, you get the idea. But now, I've got the new Xcode and I'm building
ObjCSword. So far it's been about 15 minutes… (Not counting the 2 hour
download / install / fix of Mountain Lion)

More to follow.
Jeff

I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2.

I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran the
build. It failed on Lucene dependency. Just to try to get it to build, I
removed the lucene define and ran the build again. It failed on the ICU
dependency. I removed the ICU define.

Now it fails on the AnalysisHeader step. Here's the last line of the build
output.

clang: error: no such file or directory:
'/Users/jbarne200/sword/trunk/bindings/objc/dependencies/clucene/CLucene/analysis/AnalysisHeader.cpp'
clang: error: no input files
Command
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
failed with exit code 1

Regards,
Jeff___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Method Name Normalization

On Sun, Jan 20, 2013 at 5:30 PM, Ben Morgan benpmor...@gmail.com wrote:

 Hi Greg,

 On Mon, Jan 21, 2013 at 6:28 AM, Greg Hellings greg.helli...@gmail.comwrote:




 SWIG bindings now up-to-date.

 Bindings users, please holler if I removed things overzealously.

 I haven't tried it, but I believe that this will break BPBible for
 example.

 As the bindings are part of SWORD, I believe it makes sense to mirror the
 deprecations in the bindings somehow if possible, rather than ignoring the
 deprecated definitions.
 I know that's what e.g. wxPython does, but I'm not sure how it does it.


I can't see any way of marking the methods as deprecated using SWIG. A
Google search has turned up no such evidence that it is even possible.
While I would like to mark them as deprecated, I think it is more proper
for there to be no such warnings coming from building the engine. I think
it would just smack as an issue with building if the engine produced
warnings that it uses its own deprecation warnings!



 Doing this will make it easier to support both SWORD 1.6 and SVN, which I
 think is desirable until a couple of versions down the road.


Supporting both is not something that either BibleTime or Xiphos is able to
do at this point, either. In BT we maintain a separate branch for
compatibility with SWORD while in Xiphos we simply can't make a new release
until the engine releases. BPBible will probably need to take a similar
path.

Part of cleaning up warnings from building are to allow the bindings to
make it into distros. I've cleaned them up enough since 1.6.2 that
hopefully this release will see at least Dmitrijs and whoever is our Fedora
maintainer at this point able to build the bindings and include them in the
distro which ought to allow BPBible to be packaged as well. Previously at
least Debian was choking on the bindings failing to build due to warnings
and -Werror flags.

In short, I'd rather keep these out unless there's a way to suppress the
compile warnings and mark them as deprecated in the SWIG output. If you
find evidence of that possibility, please let me know.

--Greg



 God Bless,
 Ben
 -
  For I have no pleasure in the death of anyone,
 declares the Lord God; so turn, and live.”
 Ezekiel 18:32 (ESV)

 ___
 sword-devel mailing list: sword-devel@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

On Jan 24, 2013, at 9:52:37AM, Barnes, Jeffrey jbarnes...@yahoo.com wrote:

I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2.

Now it fails on the AnalysisHeader step. Here's the last line of the build
output.

Regards,
Jeff

Also, there are compiler warnings on almost every file. The most common one
being like the following:

/Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit conversion
loses integer precision: 'unsigned long' to 'unsigned int'

etc.

I have a gut wrench every time I see a compiler warning. I have to maintain
code at work and one of the first things my boss told me to do was clean up the
compiler warnings. I have to encourage the other members of my team constantly
to keep trunk pristine. Forgive me if I'm being pedantic, but Me no like
compiler warnings!

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Method Name Normalization

2013-01-24 Thread ref...@gmx.net


FWIW, I am probably the only frequent Perl binding user and I would accept 
whatever is easiest for you. Thanks for doing this. Once the bindings are 
working, I will fix all scripts depending on it

Peter
Sent from my HTC

- Reply message -
From: Greg Hellings greg.helli...@gmail.com
To: SWORD Developersapos; Collaboration Forum sword-devel@crosswire.org
Subject: [sword-devel] Method Name Normalization
Date: Thu, Jan 24, 2013 15:55
On Sun, Jan 20, 2013 at 5:30 PM, Ben Morgan benpmor...@gmail.com wrote:

Hi Greg,

On Mon, Jan 21, 2013 at 6:28 AM, Greg Hellings greg.helli...@gmail.com wrote:






SWIG bindings now up-to-date.

Bindings users, please holler if I removed things overzealously.
I haven't tried it, but I believe that this will break BPBible for example.




As the bindings are part of SWORD, I believe it makes sense to mirror the 
deprecations in the bindings somehow if possible, rather than ignoring the 
deprecated definitions. 
I know that's what e.g. wxPython does, but I'm not sure how it does it.


I can't see any way of marking the methods as deprecated using SWIG. A Google 
search has turned up no such evidence that it is even possible. While I would 
like to mark them as deprecated, I think it is more proper for there to be no 
such warnings coming from building the engine. I think it would just smack as 
an issue with building if the engine produced warnings that it uses its own 
deprecation warnings!
 

 
Doing this will make it easier to support both SWORD 1..6 and SVN, which I 
think is desirable until a couple of versions down the road.

Supporting both is not something that either BibleTime or Xiphos is able to do 
at this point, either. In BT we maintain a separate branch for compatibility 
with SWORD while in Xiphos we simply can't make a new release until the engine 
releases. BPBible will probably need to take a similar path.

Part of cleaning up warnings from building are to allow the bindings to make it 
into distros. I've cleaned them up enough since 1.6.2 that hopefully this 
release will see at least Dmitrijs and whoever is our Fedora maintainer at this 
point able to build the bindings and include them in the distro which ought to 
allow BPBible to be packaged as well. Previously at least Debian was choking on 
the bindings failing to build due to warnings and -Werror flags.

In short, I'd rather keep these out unless there's a way to suppress the 
compile warnings and mark them as deprecated in the SWIG output. If you find 
evidence of that possibility, please let me know.

--Greg God Bless,
Ben

-




For I have no pleasure in the death of anyone, 
declares the Lord God; so turn, and live.”
Ezekiel 18:32 (ESV)




___

sword-devel mailing list: sword-devel@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Method Name Normalization

On Thu, Jan 24, 2013 at 9:17 AM, ref...@gmx.net ref...@gmx.net wrote:


 FWIW, I am probably the only frequent Perl binding user and I would accept
 whatever is easiest for you. Thanks for doing this. Once the bindings are
 working, I will fix all scripts depending on it


Perl and Python bindings should be identical to within the limits of SWIG
to emulate them. I have already submitted the chance that removes all
deprecated methods from the SWIG bindings. If you do an SVN up, you should
get the updated bindings.

To help with your updating, you can find the list of deprecated and removed
functions in bindings/swig/deprecated.i or similar.

--Greg



 Peter
 Sent from my HTC


 - Reply message -
 From: Greg Hellings greg.helli...@gmail.com
 To: SWORD Developers' Collaboration Forum sword-devel@crosswire.org
 Subject: [sword-devel] Method Name Normalization
 Date: Thu, Jan 24, 2013 15:55





 On Sun, Jan 20, 2013 at 5:30 PM, Ben Morgan benpmor...@gmail.com wrote:

 Hi Greg,

 On Mon, Jan 21, 2013 at 6:28 AM, Greg Hellings 
 greg.helli...@gmail.comwrote:




 SWIG bindings now up-to-date.

 Bindings users, please holler if I removed things overzealously.

 I haven't tried it, but I believe that this will break BPBible for
 example.

 As the bindings are part of SWORD, I believe it makes sense to mirror the
 deprecations in the bindings somehow if possible, rather than ignoring the
 deprecated definitions.
 I know that's what e.g. wxPython does, but I'm not sure how it does it.


 I can't see any way of marking the methods as deprecated using SWIG. A
 Google search has turned up no such evidence that it is even possible.
 While I would like to mark them as deprecated, I think it is more proper
 for there to be no such warnings coming from building the engine. I think
 it would just smack as an issue with building if the engine produced
 warnings that it uses its own deprecation warnings!



 Doing this will make it easier to support both SWORD 1..6 and SVN, which
 I think is desirable until a couple of versions down the road.


 Supporting both is not something that either BibleTime or Xiphos is able
 to do at this point, either. In BT we maintain a separate branch for
 compatibility with SWORD while in Xiphos we simply can't make a new release
 until the engine releases. BPBible will probably need to take a similar
 path.

 Part of cleaning up warnings from building are to allow the bindings to
 make it into distros. I've cleaned them up enough since 1.6.2 that
 hopefully this release will see at least Dmitrijs and whoever is our Fedora
 maintainer at this point able to build the bindings and include them in the
 distro which ought to allow BPBible to be packaged as well. Previously at
 least Debian was choking on the bindings failing to build due to warnings
 and -Werror flags.

 In short, I'd rather keep these out unless there's a way to suppress the
 compile warnings and mark them as deprecated in the SWIG output. If you
 find evidence of that possibility, please let me know.

 --Greg



 God Bless,
 Ben
 -
  For I have no pleasure in the death of anyone,
 declares the Lord God; so turn, and live.”
 Ezekiel 18:32 (ESV)

 ___
 sword-devel mailing list: sword-devel@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@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Pre-verse div and headings

2013-01-24 Thread David Haslam

Another reminder for potential newcomers:

Pasted from
http://crosswire.org/wiki/DevTools:conf_Files#Optional_elements_to_support_particular_features

For the GlobalOptionFilter=*OSISHeadings* 
the accompanying explanation is (For OSIS texts having non-canonical
headings)

David







--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Pre-verse-div-and-headings-tp4651710p4651796.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

Indeed, there are a lot of warnings, not mentioning CLucene.

I'll do a clean checkout of the sources and see if I can replicate your errors.
You should however build with ICU. CLucene it not necessarily needed since on
Mac the index is built using SearchKit framework.

Manfred

Am 24.01.2013 um 15:59 schrieb Barnes, Jeffrey jbarnes...@yahoo.com:

On Jan 24, 2013, at 9:52:37AM, Barnes, Jeffrey jbarnes...@yahoo.com wrote:

I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2.

Now it fails on the AnalysisHeader step. Here's the last line of the build
output.

Regards,
Jeff

Also, there are compiler warnings on almost every file. The most common one
being like the following:

/Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit conversion
loses integer precision: 'unsigned long' to 'unsigned int'

etc.

I have a gut wrench every time I see a compiler warning. I have to maintain
code at work and one of the first things my boss told me to do was clean up
the compiler warnings. I have to encourage the other members of my team
constantly to keep trunk pristine. Forgive me if I'm being pedantic, but Me
no like compiler warnings!

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken


On Jan 24, 2013, at 12:18:18PM, Manfred Bergmann manfred.bergm...@me.com 
wrote:

 I'll do a clean checkout of the sources and see if I can replicate your 
 errors.
 You should however build with ICU. CLucene it not necessarily needed since on 
 Mac the index is built using SearchKit framework.

How do I link against ICU? Are the .h/.cpp files in trunk?

Sorry for the need to hold my hand.

Jeff
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

Alright.
Here is what you need to do.
in objc folder go to dependencies and execute retrieve.sh.
This downloads the icu and clucene sources and headers which are required for
the Xcode build.

I've done some adaptions to the latest sword src changes. One method was
removed which gave an error. And there are now a lot of deprecation warnings
which I have to go through.
I've also removed two old library search paths from the project which pointed
to a folder that doesn't exist.

If you update your sources it should build fine now.

Manfred

Am 24.01.2013 um 18:18 schrieb Manfred Bergmann manfred.bergm...@me.com:

Indeed, there are a lot of warnings, not mentioning CLucene.

I'll do a clean checkout of the sources and see if I can replicate your
errors.
You should however build with ICU. CLucene it not necessarily needed since on
Mac the index is built using SearchKit framework.

Manfred

Am 24.01.2013 um 15:59 schrieb Barnes, Jeffrey jbarnes...@yahoo.com:

On Jan 24, 2013, at 9:52:37AM, Barnes, Jeffrey jbarnes...@yahoo.com
wrote:

I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2.

I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran
the build. It failed on Lucene dependency. Just to try to get it to build,
I removed the lucene define and ran the build again. It failed on the ICU
dependency. I removed the ICU define.

Now it fails on the AnalysisHeader step. Here's the last line of the build
output.

Regards,
Jeff

Also, there are compiler warnings on almost every file. The most common one
being like the following:

/Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit conversion
loses integer precision: 'unsigned long' to 'unsigned int'

etc.

I have a gut wrench every time I see a compiler warning. I have to maintain
code at work and one of the first things my boss told me to do was clean up
the compiler warnings. I have to encourage the other members of my team
constantly to keep trunk pristine. Forgive me if I'm being pedantic, but Me
no like compiler warnings!

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken


Am 24.01.2013 um 20:02 schrieb Barnes, Jeffrey jbarnes...@yahoo.com:

 
 On Jan 24, 2013, at 12:18:18PM, Manfred Bergmann manfred.bergm...@me.com 
 wrote:
 
 I'll do a clean checkout of the sources and see if I can replicate your 
 errors.
 You should however build with ICU. CLucene it not necessarily needed since 
 on Mac the index is built using SearchKit framework.
 
 How do I link against ICU? Are the .h/.cpp files in trunk?

The project links against libicu-core which is shipped with OS X.
The ICU headers are in the dependencies once retrieve.sh is executed.


Manfred

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

I had trouble updating, so I blew away my local trunk directory.

I tried the command line.

PACCPL-334LAGYA:sword jbarne200$ svn co https://crosswire.org/svn/sword/trunk
Error validating server certificate for 'https://crosswire.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
- The certificate hostname does not match.
Certificate information:
- Hostname: www.crosswire.org
- Valid: from Fri, 04 May 2012 23:03:07 GMT until Sat, 04 May 2013 23:03:07 GMT
- Issuer: SomeOrganizationalUnit, SomeOrganization, SomeCity, SomeState, --
- Fingerprint: 60:d4:77:54:37:d3:37:ed:42:92:7b:eb:1a:f0:25:f7:50:ff:c2:57
(R)eject, accept (t)emporarily or accept (p)ermanently? p
svn: PROPFIND of '/svn/sword/trunk': SSL handshake failed: Secure connection
truncated (https://crosswire.org)

I tried from Xcode. It told me to validate the fingerprint (where do I do
that?).

Is the repository down? I thought the command line version should have worked.

Jeff

On Jan 24, 2013, at 2:27:58PM, Manfred Bergmann manfred.bergm...@me.com wrote:

Alright.
Here is what you need to do.
in objc folder go to dependencies and execute retrieve.sh.
This downloads the icu and clucene sources and headers which are required for
the Xcode build.

If you update your sources it should build fine now.

Manfred

Am 24.01.2013 um 18:18 schrieb Manfred Bergmann manfred.bergm...@me.com:

Indeed, there are a lot of warnings, not mentioning CLucene.

I'll do a clean checkout of the sources and see if I can replicate your
errors.
You should however build with ICU. CLucene it not necessarily needed since
on Mac the index is built using SearchKit framework.

Manfred

Am 24.01.2013 um 15:59 schrieb Barnes, Jeffrey jbarnes...@yahoo.com:

On Jan 24, 2013, at 9:52:37AM, Barnes, Jeffrey jbarnes...@yahoo.com
wrote:

I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2.

I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran
the build. It failed on Lucene dependency. Just to try to get it to build,
I removed the lucene define and ran the build again. It failed on the ICU
dependency. I removed the ICU define.

Now it fails on the AnalysisHeader step. Here's the last line of the build
output.

Regards,
Jeff

Also, there are compiler warnings on almost every file. The most common one
being like the following:

/Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit
conversion loses integer precision: 'unsigned long' to 'unsigned int'

etc.

I have a gut wrench every time I see a compiler warning. I have to maintain
code at work and one of the first things my boss told me to do was clean up
the compiler warnings. I have to encourage the other members of my team
constantly to keep trunk pristine. Forgive me if I'm being pedantic, but
Me no like compiler warnings!

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

I'm not sure. Maybe try plain http?
It's also enough to rm objc and do svn update. It will fetch objc folder again.

Manfred

Am 24.01.2013 um 21:06 schrieb Barnes, Jeffrey jbarnes...@yahoo.com:

I had trouble updating, so I blew away my local trunk directory.

I tried the command line.

PACCPL-334LAGYA:sword jbarne200$ svn co https://crosswire.org/svn/sword/trunk
Error validating server certificate for 'https://crosswire.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
- The certificate hostname does not match.
Certificate information:
- Hostname: www.crosswire.org
- Valid: from Fri, 04 May 2012 23:03:07 GMT until Sat, 04 May 2013 23:03:07
GMT
- Issuer: SomeOrganizationalUnit, SomeOrganization, SomeCity, SomeState, --
- Fingerprint: 60:d4:77:54:37:d3:37:ed:42:92:7b:eb:1a:f0:25:f7:50:ff:c2:57
(R)eject, accept (t)emporarily or accept (p)ermanently? p
svn: PROPFIND of '/svn/sword/trunk': SSL handshake failed: Secure connection
truncated (https://crosswire.org)

I tried from Xcode. It told me to validate the fingerprint (where do I do
that?).

Is the repository down? I thought the command line version should have worked.

Jeff

On Jan 24, 2013, at 2:27:58PM, Manfred Bergmann manfred.bergm...@me.com
wrote:

Alright.
Here is what you need to do.
in objc folder go to dependencies and execute retrieve.sh.
This downloads the icu and clucene sources and headers which are required
for the Xcode build.

If you update your sources it should build fine now.

Manfred

Am 24.01.2013 um 18:18 schrieb Manfred Bergmann manfred.bergm...@me.com:

Indeed, there are a lot of warnings, not mentioning CLucene.

I'll do a clean checkout of the sources and see if I can replicate your
errors.
You should however build with ICU. CLucene it not necessarily needed since
on Mac the index is built using SearchKit framework.

Manfred

Am 24.01.2013 um 15:59 schrieb Barnes, Jeffrey jbarnes...@yahoo.com:

On Jan 24, 2013, at 9:52:37AM, Barnes, Jeffrey jbarnes...@yahoo.com
wrote:

I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2.

I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran
the build. It failed on Lucene dependency. Just to try to get it to
build, I removed the lucene define and ran the build again. It failed on
the ICU dependency. I removed the ICU define.

Now it fails on the AnalysisHeader step. Here's the last line of the
build output.

Regards,
Jeff

Also, there are compiler warnings on almost every file. The most common
one being like the following:

/Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit
conversion loses integer precision: 'unsigned long' to 'unsigned int'

etc.

I have a gut wrench every time I see a compiler warning. I have to
maintain code at work and one of the first things my boss told me to do
was clean up the compiler warnings. I have to encourage the other members
of my team constantly to keep trunk pristine. Forgive me if I'm being
pedantic, but Me no like compiler warnings!

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

Ok, everything built. (Hooray!)

I recommend updating bindings/objc/README to the following.

Building ObjCSword wrapper framework howto
==

Mac OS X target:
This project can only be built on OS X 10.8 (Mountain Lion) or later.

To build for Mac OS X:

1) Change to the dependencies directory.
2) Run retrieve.sh. This downloads the icu and clucene sources and headers 
which are required for the Xcode build.

To build from inside Xcode double-click the ObjCSword.xcodeproj in Finder. This 
opens Xcode and loads the Sword Project. Press Command + B to build (or 
select Build from the Product menu).

To build from the command line, enter xcodebuild -project ./ObjCSword.xcodeproj.


+

How can I reference this new ObjCSword in another project?

Thanks so much for your help Manfred.

Jeff



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] bindings/objc build broken

Yep, thanks. I will update the README.

You can now use the result (ObjCSword.framework) as a dependency in another 
project.
Or you add the whole Xcode project to another Xcode project.
If you build the outer project the inner project is built as well or actually 
the inner one is built first.

You can also have a look at the (too few) OCUnit tests (i.e. SwordModuleTest) 
in ObjCSword, at least regarding the API usage.



Manfred


Am 24.01.2013 um 22:04 schrieb Barnes, Jeffrey jbarnes...@yahoo.com:

 Ok, everything built. (Hooray!)
 
 I recommend updating bindings/objc/README to the following.
 
 Building ObjCSword wrapper framework howto
 ==
 
 Mac OS X target:
 This project can only be built on OS X 10.8 (Mountain Lion) or later.
 
 To build for Mac OS X:
 
 1) Change to the dependencies directory.
 2) Run retrieve.sh. This downloads the icu and clucene sources and headers 
 which are required for the Xcode build.
 
 To build from inside Xcode double-click the ObjCSword.xcodeproj in Finder. 
 This opens Xcode and loads the Sword Project. Press Command + B to build 
 (or select Build from the Product menu).
 
 To build from the command line, enter xcodebuild -project 
 ./ObjCSword.xcodeproj.
 
 
 +
 
 How can I reference this new ObjCSword in another project?
 
 Thanks so much for your help Manfred.
 
 Jeff
 
 


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Location of prebuilt lucene indexes.

2013-01-24 Thread Daniel Hughes

Thanks all for your replies.

I am using Lucene.net which is a .net port of the java Lucene. I have been
able to consume an index created by xiphos which I assume uses clucene.

However based on the replies here I think I will generate my own indexes to
avoid and compatibility issues.

Daniel Hughes


On Fri, Jan 25, 2013 at 2:10 AM, Martin Denham mjden...@gmail.com wrote:

 Hi David,

 To delete an index in And Bible you long-press the desired module in the
 Documents list to reveal module and index delete actions in the context
 menu.

 Martin

 On 24 January 2013 12:36, David Haslam dfh...@googlemail.com wrote:

 *And Bible* allows the user to create the search index for a module if it
 does not already exist.

 This is useful in these situations:

 (a) The user is currently not [reliably] connected to the Internet,
 (b) Martin has not yet made the downloadable index for new/updated
 modules.

 And Bible does not have a UI option to remove a search index,
 though this could be done manually by means of the file system,
 assuming you know where to look within the Android directory structure.

 David





 --
 View this message in context:
 http://sword-dev.350566.n4.nabble.com/Location-of-prebuilt-lucene-indexes-tp4651756p4651788.html
 Sent from the SWORD Dev mailing list archive at Nabble.com.

 ___
 sword-devel mailing list: sword-devel@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@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Xiphos: Checked out revision 4411. (errors)

Has something changed in the Xiphos build?

I've had no problems until 4411 (last successful build before was 4408).

The build starts off ok:

[ 42/130] cxx: src/backend/module_manager.cc -
build/default/src/backend/module_manager_1.o
[ 43/130] cxx: src/backend/sword_main.cc -
build/default/src/backend/sword_main_1.o
../src/backend/module_manager.cc: In function ‘MOD_MGR*
backend_module_mgr_get_next_module()’:
../src/backend/module_manager.cc:171:30: warning: ‘const char*
sword::SWModule::Name() const’ is deprecated (declared at
/usr/local/include/sword/swmodule.h:285) [-Wdeprecated-declarations]
../src/backend/module_manager.cc:171:30: error: invalid conversion from
‘const char*’ to ‘gchar* {aka char*}’ [-fpermissive]
../src/backend/module_manager.cc:176:43: warning: ‘const char*
sword::SWModule::Lang(char*)’ is deprecated (declared at
/usr/local/include/sword/swmodule.h:353) [-Wdeprecated-declarations]
../src/backend/module_manager.cc:177:43: warning: ‘const char*
sword::SWModule::Type() const’ is deprecated (declared at
/usr/local/include/sword/swmodule.h:313) [-Wdeprecated-declarations]
../src/backend/module_manager.cc:216:48: warning: ‘const char*
sword::SWModule::Description() const’ is deprecated (declared at
/usr/local/include/sword/swmodule.h:299) [-Wdeprecated-declarations]
../src/backend/module_manager.cc:216:48: error: invalid conversion from
‘const char*’ to ‘char*’ [-fpermissive]

CUTTING LOTS OF INTERMEDIARY ERRORS

But ends with:
../src/backend/sword_main.cc: In member function ‘const char*
BackEnd::get_next_listkey()’:
../src/backend/sword_main.cc:921:24: warning: ‘char sword::SWKey::Error()’
is deprecated (declared at /usr/local/include/sword/swkey.h:159)
[-Wdeprecated-declarations]
../src/backend/sword_main.cc: In member function ‘int
BackEnd::set_range(char*)’:
../src/backend/sword_main.cc:943:57: warning: ‘sword::ListKey
sword::VerseKey::ParseVerseList(const char*, const char*, bool, bool)’ is
deprecated (declared at /usr/local/include/sword/versekey.h:452)
[-Wdeprecated-declarations]
Waf: Leaving directory `/usr/local/src/xiphos/build'
Build failed:
 - task failed (err #1):
{task: cxx module_manager.cc - module_manager_1.o}
 - task failed (err #1):
{task: cxx sword_main.cc - sword_main_1.o}

Is anyone else having trouble?  I haven't changed my environment (since
revision 4408)  Can anyone tell from the above what the issue might be?
~A
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Xiphos: Checked out revision 4411. (errors)

2013-01-24 Thread Karl Kleinpaste

If you're trying to build Xiphos against recently updated Sword, it's
going to be a mess right now.  I'll deal with it by week's end.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Xiphos: Checked out revision 4411. (errors)

.. and thinking about it, you're correct.  Something had changed on my end,
namely the Sword revision I was running. I had forgotten about that, until
you pointed it out.

~A


On Thu, Jan 24, 2013 at 10:39 PM, Andrew Thule thules...@gmail.com wrote:

 I was Karl.  Thanks for the heads up.  I look forward to your fixes (no
 rush).

 ~A


 On Thu, Jan 24, 2013 at 9:34 PM, Karl Kleinpaste k...@kleinpaste.orgwrote:

 If you're trying to build Xiphos against recently updated Sword, it's
 going to be a mess right now.  I'll deal with it by week's end.

 ___
 sword-devel mailing list: sword-devel@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Xiphos: Checked out revision 4411. (errors)

If you monitored the proper message stream you'd see I have created a patch
which attempts to fix this compile problem but introduces a minor display
bug in the process (module text will not display at all...).

--Greg


On Thu, Jan 24, 2013 at 9:39 PM, Andrew Thule thules...@gmail.com wrote:

 I was Karl.  Thanks for the heads up.  I look forward to your fixes (no
 rush).

 ~A


 On Thu, Jan 24, 2013 at 9:34 PM, Karl Kleinpaste k...@kleinpaste.orgwrote:

 If you're trying to build Xiphos against recently updated Sword, it's
 going to be a mess right now.  I'll deal with it by week's end.

 ___
 sword-devel mailing list: sword-devel@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@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Xiphos: Checked out revision 4411. (errors)

Thanks Greg .. Ill go looking for the patch .. or perhaps I won't.  Ill
give it thought.
It might be best if I keep a working version of Xiphos, allowing for the
compiler problems, until Karl's updates are merged.

I'm not sure how bad Xiphos withdraw can get ..
~A


On Thu, Jan 24, 2013 at 10:42 PM, Greg Hellings greg.helli...@gmail.comwrote:

 If you monitored the proper message stream you'd see I have created a
 patch which attempts to fix this compile problem but introduces a minor
 display bug in the process (module text will not display at all...).

 --Greg


 On Thu, Jan 24, 2013 at 9:39 PM, Andrew Thule thules...@gmail.com wrote:

 I was Karl.  Thanks for the heads up.  I look forward to your fixes (no
 rush).

 ~A


 On Thu, Jan 24, 2013 at 9:34 PM, Karl Kleinpaste k...@kleinpaste.orgwrote:

 If you're trying to build Xiphos against recently updated Sword, it's
 going to be a mess right now.  I'll deal with it by week's end.

 ___
 sword-devel mailing list: sword-devel@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@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@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Question about CMAKE build proceedures

I'm still fairly new to using CMAKE (but liking it).  I'm finally starting
to feel comfortable with its use, but still have questions .. so if this is
a newbie question, sorry.

Using traditional ./configure; make; make install' I could simply grab a
more recent copy (of sword) via svn and make  make install.

However, I'm finding with CMAKE I have to completely blow away my cmake
build directory before I cmake -DSWORD_BINDINGS=Perl Python ../sword.
If I don't, I seem to get never ending compiler/build loops.

Is it generally necessary to start with a fresh cmake build directory
before make  make install?

~A
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Question about CMAKE build proceedures