Did a fresh checkout of https://crosswire.org/svn/sword/trunk. Changed to
bindings/objc.
1) The bindings/objc/README instructions are inaccurate. There is no Makefile
in build_sword.
2) The build breaks in build_sword/build_mac_sword.sh.
$ cd build_clucene
$ make release-fat
...
looks like
The Obj-C bindings have not been updated since Troy's major commit to
deprecate methods and the like. However, the error you're seeing appears to
be a result of missing some of the autofoo material that you need. Do you
have any information on the state of your autotools package? That might
help
Thanks for the quick response, Greg.
PACCPL-334LAGYA:trunk jbarne200$ which autoconf
/usr/bin/autoconf
PACCPL-334LAGYA:trunk jbarne200$ which automake
/usr/bin/automake
PACCPL-334LAGYA:trunk jbarne200$ which libtool
/usr/bin/libtool
PACCPL-334LAGYA:trunk jbarne200$ which aclocal
/usr/bin/aclocal
Hi.
The build scripts are deprecated and should be removed altogether.
Try building using the ObjCSword Xcode project.
I just made some code changes lately so it should still work.
Manfred
Am 23.01.2013 um 15:31 schrieb Jeff Barnes jbarnes...@yahoo.com:
Thanks for the quick response, Greg.
If you want to build from command line you can also use something like this:
# xcodebuild -target some target -configuration some config clean build
The pre-lion Xcode project may also be outdated as I didn't have the time to
maintain it.
Manfred
Am 23.01.2013 um 15:45 schrieb Manfred
Hi Daniel,
I put the question to Martin Denham (the developer of And Bible).
He replied: (lightly edited by me)
And Bible's indexes are here: http://www.crosswire.org/and-bible/indices/v1/
but they are only guaranteed to work with And Bible and almost definitely
won't work with SWORD C++
Daniel, the indexes themselves are created using the utility mkfastmod. If
built, the lucene indexes typically sit off of the modules directory
directly .. ie:
.../modules/texts/ztext/kjv/lucene
Administrators of a repo, you can generate the lucene directories, and have
them automatically
Von: Andrew Thule thules...@gmail.com
The nice thing about when
repo administrators do this, is when you get a module from that repo, you
also automatically get the lucene index.
The reason that this is not done are manifold - including that sword and jsword
indices are different, that
On Jan 23, 2013, at 11:02 AM, Peter von Kaehne ref...@gmx.net wrote:
Von: Andrew Thule thules...@gmail.com
The nice thing about when
repo administrators do this, is when you get a module from that repo, you
also automatically get the lucene index.
The reason that this is not done are
Peter, DM, Thanks for your response. I wasn't being critical and I agree.
There are Pros and Cons either way (resource usage and download time being
considerations) as you point out.
I also agree it's ultimately it's up to the repo administrator and the
user, to decide for themselves what works
Von: Andrew Thule thules...@gmail.com
There are Pros and Cons either way (resource usage and download time
being considerations) as you point out.
There are no pros and only contras. And I certainly have not pointed out any
pros. Nor has DM. Please stop using my name as supposedly in
To add to the discussion. Step ships data files and later indexes as part
of the installation of software plus automatically after installation of
any module.
We considered shipping indexes but decided against it. This is because
indexes can become corrupt quite easily and can be incompatible
Peter, if I offended you, I hope you'll forgive me.
~A
On Wednesday, January 23, 2013, Peter von Kaehne wrote:
Von: Andrew Thule thules...@gmail.com javascript:;
There are Pros and Cons either way (resource usage and download time
being considerations) as you point out.
There are no
Am 23.01.2013 um 19:41 schrieb Barnes, Jeffrey jbarnes...@gmail.com:
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.
Am 23.01.2013 um 21:54 schrieb Barnes, Jeffrey jbarnes...@gmail.com:
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,
Looks like the pre-Lion project hadn't been updated in a long time and so
didn't have any newly required headers added to it (which you can see from the
build log you pasted in a previous email).
You could also look at the PocketSword source to get another idea of how to go
about compiling
My suggestion would be to avoid pre-built indices. However, given I'm the one
who first went about making them, I think there are pros in certain situations.
:P
In my situation, I get to be gatekeeper over the entire solution (PocketSword),
where users cannot change the version of clucene or
On Jan 23, 2013, at 8:31:29PM, Nic Carter niccar...@mac.com wrote:
You could also look at the PocketSword source to get another idea of how to
go about compiling things?
The reason I posted to sword-devel is because they own the broken build.
Whoever is the objc bindings build maintainer
On Wed, Jan 23, 2013 at 10:30 PM, Barnes, Jeffrey jbarnes...@yahoo.comwrote:
On Jan 23, 2013, at 8:31:29PM, Nic Carter niccar...@mac.com wrote:
You could also look at the PocketSword source to get another idea of how
to go about compiling things?
The reason I posted to sword-devel is
Thanks for making them .. It is appreciated! ... I find them
incredibly useful (and I was surprised they worked by way of a repo too!)
I am sympathetic to many of the arguements presented against creating them
in repos, and I do create them for myself on the desktop (so to speak) so I
also see
Am 23.01.2013 um 23:21 schrieb Jeff Barnes jbarnes...@gmail.com:
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.
21 matches
Mail list logo
