As we're beginning to polish the packaging for 1.7.0, I'd like to ping
everyone with this request once more. Specifically:
charcoal
chrislit
dmsmith
mdbergmann
refdoc
You still have entries in the ChangeLog which haven't been converted
from svn log format to our ChangeLog format, thus co
Bindings on Ubuntu 13.04 - i386 server install, clean VM
apart from needing ldconfig been run and that ICU error message, both Perl and
Python bindings seem to work.
Peter
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.or
On 7/16/2013 5:19 AM, Greg Hellings wrote:
On Tue, Jul 16, 2013 at 7:14 AM, Mark Trompell mailto:m...@foresightlinux.org>> wrote:
I think it's one of these that bite us:
"""
r2831 | chrislit | 2013-06-23 06:21:14 +0200 (So, 23 Jun 2013) | 2 lines
removed ICU stuff from CMake
On Tue, Jul 16, 2013 at 7:14 AM, Mark Trompell wrote:
> I think it's one of these that bite us:
> """
> r2831 | chrislit | 2013-06-23 06:21:14 +0200 (So, 23 Jun 2013) | 2 lines
>
> removed ICU stuff from CMake files to match autotools files
>
> -
I think it's one of these that bite us:
"""
r2831 | chrislit | 2013-06-23 06:21:14 +0200 (So, 23 Jun 2013) | 2 lines
removed ICU stuff from CMake files to match autotools files
r2830 | chrislit | 2013-06-23 03:22:45 +0200 (S
On 7/16/2013 5:04 AM, Mark Trompell wrote:
On Tue, Jul 16, 2013 at 10:40 AM, Peter von Kaehne wrote:
Von: "Troy A. Griffitts"
Does anyone have Ubuntu installed and can try building the swig bindings to confirm
or deny they have the same problem as > Peter? This is using autotools.
S
On Tue, Jul 16, 2013 at 10:40 AM, Peter von Kaehne wrote:
>
> Von: "Troy A. Griffitts"
>
>> Does anyone have Ubuntu installed and can try building the swig bindings to
>> confirm or deny they have the same problem as > Peter? This is using
>> autotools. Simply compile and install sword, t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16.07.2013 06:15, Troy A. Griffitts wrote:
> OK, wrapping up final things for packaging up 1.7.0.
>
> Jaak, I've normalized ListKey for you, so you should have your
> getCount const and added getElement const and non-const methods.
> Other method n
Von: "Troy A. Griffitts"
> Does anyone have Ubuntu installed and can try building the swig bindings to
> confirm or deny they have the same problem as > Peter? This is using
> autotools. Simply compile and install sword, then cd to
> bindings/swig/package and follow the short> READM
That's all right.
The ObjC wrapper user probably expects that it builds against the current SWORD
sources.
Saying that, I had to update the Xcode project as more files had been
removed/added in SWORD.
Manfred
Am 16.07.2013 um 07:49 schrieb Troy A. Griffitts :
> It seems we've all been negli
It seems we've all been negligent updating ChangeLog.
I've seeded it will the svn log since the last release. I spent a while
reviewing the entries and deleted about 70% of them that had to do with
"fixed this, improved that" or entries where I saw something like "added
iOS XCode Project" wit
OK, wrapping up final things for packaging up 1.7.0.
Jaak, I've normalized ListKey for you, so you should have your getCount
const and added getElement const and non-const methods. Other method
names have been normalized with old names deprecated, so this will
almost certainly cause deprecatio
> Von: "Troy A. Griffitts"
> Just to confirm, you're building and installing sword, then building the
> bindings, yes?
Yes
> pkg-config sword --libs
peter@peter-ThinkPad-Twist:~$ pkg-config sword --libs
-Wl,-Bsymbolic-functions -Wl,-z,relro -L/usr/local/lib -lsword -lz -lcurl
-lclucene -lic
Peter,
It seems you're missing an ICU symbol.
Just to confirm, you're building and installing sword, then building the
bindings, yes?
Could you send me a few things:
pkg-config sword --libs
and also when you build the python bindings, could you send me the build
output lines for the compil
On Thu, Jul 11, 2013 at 2:49 AM, Peter von Kaehne wrote:
>
> > Gesendet: Dienstag, 09. Juli 2013 um 08:53 Uhr
> > Von: "Troy A. Griffitts"
>
> > Peter, are you building with auto tools or cmake? I can look more into
> the autotools system if the problem is here. It> doesn't seem to
> use
> Gesendet: Dienstag, 09. Juli 2013 um 08:53 Uhr
> Von: "Troy A. Griffitts"
> Peter, are you building with auto tools or cmake? I can look more into the
> autotools system if the problem is here. It> doesn't seem to use
> pkgconfig to get libs and flags and I'd like to switch it to tha
Von: "Greg Hellings"
In that case I might not be able to help you much. Can you try building them
with CMake (you can see a sample invocation and build call in
cmake/build-debug.sh that should be configured to build both Perl and Python
bindings) and see if that installation works? If so, the
gt;>> sword-tools/modules/crossreferences/xreffix.pl without arguments will
>> >>> test loading Perl Sword bindings
>> >>>
>> >>> and in Python:
>> >>>
>> >>> Simply run from commandline Python and do "import Sword" and
On Tue, Jul 9, 2013 at 9:26 AM, Peter von Kaehne wrote:
>
> Von: "Greg Hellings"
>
> In that case I might not be able to help you much. Can you try building
> them with CMake (you can see a sample invocation and build call in
> cmake/build-debug.sh that should be configured to build both Perl an
On Tue, Jul 9, 2013 at 4:41 AM, Peter von Kaehne wrote:
>
> > Von: "Troy A. Griffitts"
>
> > Peter, are you building with auto tools or cmake? I can look more into
> the autotools system if the problem is here. It> doesn't seem to
> use pkgconfig to get libs and flags and I'd like to swi
> >>> Simply run from commandline Python and do "import Sword" and see it
> fail:
> >>>
> >>> >>> import Sword
> >>> Traceback (most recent call last):
> >>> File "", line 1, in
> >>> Fi
> Von: "Dmitrijs Ledkovs"
> And subsequently dropped, due to failure to compile with gcc-4.7:
Just some speculation:
http://www.swig.org/Doc2.0/SWIGDocumentation.html#Perl5_nn9
suggests that there is a problem with 64 bit compiled applications and Perl.
Peter
_
"import Sword" and see it fail:
>>>
>>> >>> import Sword
>>> Traceback (most recent call last):
>>> File "", line 1, in
>>> File "Sword.py", line 26, in
>>> _Sword = swig_import_helper()
>>>
> Von: "Troy A. Griffitts"
> Peter, are you building with auto tools or cmake? I can look more into the
> autotools system if the problem is here. It> doesn't seem to use
> pkgconfig to get libs and flags and I'd like to switch it to that. Just one
> suspect.
auto tools.
___
Peter, are you building with auto tools or cmake? I can look more into the
autotools system if the problem is here. It doesn't seem to use pkgconfig to
get libs and flags and I'd like to switch it to that. Just one suspect.
Troy
Peter von Kaehne wrote:
>
>> Von: "John Zaitseff"
>
>> Pardon my
> Von: "John Zaitseff"
> Pardon my ignorance, but would the problem be that Sword.so is
> trying to pull in another shared library and cannot find it?
Thanks!
> Can you try running "ldd .../auto/Sword/Sword.so" (replace the path,
> of course) and see what the output is?
peter@peter-ThinkPad-X
Dear Peter et al.,
> These are the messages I get:
>
> peter@peter-ThinkPad-X200s:~/bin$
> ~/Source/sword-tools/modules/crossreferences/xreffix.pl
> Can't load '/usr/local/lib/perl/5.14.2/auto/Sword/Sword.so' for module Sword:
> /usr/local/lib/perl/5.14.2/auto/Sword/Sword.so: undefined symbol:
Sorry this did not get completed:
Von: "Greg Hellings"
> Peter, can you try and do a new install from the latest versions of SVN HEAD?
I have updated to SVN HEAD and I have prior to that looked through my $PATH to
check for any old libsword remainders (I have done that now so often, I really
Von: "Greg Hellings"
> Peter, can you try and do a new install from the latest versions of SVN HEAD?
I have updated to SVN HEAD and I have prior to that looked through my $PATH to
check for any old libsword remainders (I have done that now so often, I really
see not how I can have missed s
;> File "Sword.py", line 26, in
>> _Sword = swig_import_helper()
>> File "Sword.py", line 18, in swig_import_helper
>> import _Sword
>> ImportError: /usr/local/lib/python2.7/dist-packages/_Sword.so: undefined
>> symbol: u_strFromUTF8
_Sword = swig_import_helper()
> File "Sword.py", line 18, in swig_import_helper
> import _Sword
> ImportError: /usr/local/lib/python2.7/dist-packages/_Sword.so: undefined
> symbol: u_strFromUTF8_48
> >>>
>
>
> *Gesendet:* Sonntag, 07. Juli 2
gt;>> Traceback (most recent call last):
>>>>File "", line 1, in
>>>>File "Sword.py", line 26, in
>>>> _Sword = swig_import_helper()
>>>> File "Sword.py", line 18, in swig_import_helper
>>>>
) The Perl bindings are being built, but are not currently being installed
at all, it would appear. I have no idea why this is right now.
--Greg
Gesendet: Sonntag, 07. Juli 2013 um 19:06 Uhr
Von: "Greg Hellings"
An: "SWORD Developers' Collaboration Forum"
Betreff: Re:
appears to be stale
> on your system.
>
> 2) The Perl bindings are being built, but are not currently being installed
> at all, it would appear. I have no idea why this is right now.
>
> --Greg
>
>>
>> >>>
>>
>>
>> Gesendet: Sonntag, 07. Jul
.
2) The Perl bindings are being built, but are not currently being installed
at all, it would appear. I have no idea why this is right now.
--Greg
> >>>
>
>
> *Gesendet:* Sonntag, 07. Juli 2013 um 19:06 Uhr
> *Von:* "Greg Hellings"
> *An:* "SWORD De
> Von: "Jaak Ristioja"
> I guess in the future it might be worth to consider developing and
> releasing the bindings for other languages separately from the core of
> Sword.
While the bindings do not need by necessity an awful lot of ongoing development
they should usually function on release.
nntag, 07. Juli 2013 um 19:06 Uhr
Von: "Greg Hellings"
An: "SWORD Developers' Collaboration Forum"
Betreff: Re: [sword-devel] SWORD 1.7.0 final stretch
There should be a sample of each in the swig directory tree somewhere. I can check in an hour our so, when I get home.
There should be a sample of each in the swig directory tree somewhere. I
can check in an hour our so, when I get home.
- Greg
On Jul 7, 2013 11:42 AM, "Troy A. Griffitts" wrote:
> OK guys,
>
> I have just updated the autotools stuff and the README files to build the
> swig bindings for both Per
OK guys,
I have just updated the autotools stuff and the README files to build
the swig bindings for both Perl and Python. Anyone know how to use
SWORD with Perl or Python and can let me know if it actually works?
Troy
On 07/06/2013 03:04 PM, Peter von Kaehne wrote:
On Sat, 2013-07-06 at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.07.2013 16:04, Peter von Kaehne wrote:
> On Sat, 2013-07-06 at 04:00 +0200, Troy A. Griffitts wrote:
>> Peter, still wondering if we have a problem we need to fix for
>> you. Do our Perl and Python bindings work for other people with
>> a simila
On Sat, 2013-07-06 at 04:00 +0200, Troy A. Griffitts wrote:
> Peter, still wondering if we have a problem we need to fix for you. Do
> our Perl and Python bindings work for other people with a similar
> configuration as you?
I have not heard from anyone that the Perl bindings are working nor ha
On Fri, Jul 5, 2013 at 9:00 PM, Troy A. Griffitts wrote:
> How are we looking these day for everyone?
>
I think anything else that might be outstanding is either still under
discussion or is a bug that can be part of a 1.7.1.
We are going to actually make a 1.7 branch that is only bugfixes, corr
How are we looking these day for everyone?
Chris and I have ironed out the Rahlfs v11n.
Peter, still wondering if we have a problem we need to fix for you. Do
our Perl and Python bindings work for other people with a similar
configuration as you?
Let's wrap up an RC1 this weekend.
Troy
On Wed, 2013-06-19 at 10:45 +0200, Troy A. Griffitts wrote:
>
> Peter, still binding troubles? Can you give me your exact commands
> executed and I'll try them here.
Yes. Building works, using the Perl bindings though fails invariably.
cd ~/Source/sword
make clean
make distclean
svn up
./autoge
works as it should only docs differ because of the revision in their path:
$ diff -u <(conary showcs sword-1.6.2+r2825.ccs --ls|sort) <(conary
showcs sword-1.6.2+r2820.ccs --ls|sort)
--- /dev/fd/63 2013-06-20 08:14:57.784287767 +0200
+++ /dev/fd/62 2013-06-20 08:14:57.784287767 +0200
@@ -204,27 +20
I believe today's commit lands all of the outstanding issues I have. It
introduces enhanced functionality for CMake installs where the user does
not want to install to ../lib and ../include. For those, in mirroring the
behavior of autotools, the options LIBDIR= and
INCLUDEDIR= are now available whe
On 6/19/2013 1:45 AM, Troy A. Griffitts wrote:
Anything else? Let's push this to completion. I need your help.
I wouldn't mind getting something in place to render the attribute
included by the OSISEnum filter through the OSISXHTML filter. But I can
foresee some pushback since that attribute
On Wed, Jun 19, 2013 at 7:17 AM, Mark Trompell wrote:
> I would still like to have some feedback on attached patch to be able
> to use -DLIB_SUFFIX=64 to make make install install to /lib64.
> Hardcoding lib is not good anyway, even if there might be better
> solutions than the one in the patch. B
I would still like to have some feedback on attached patch to be able
to use -DLIB_SUFFIX=64 to make make install install to /lib64.
Hardcoding lib is not good anyway, even if there might be better
solutions than the one in the patch. But at least the provided one
doesn't break existing buildscript
As long as we follow the advice to have subsequent releases that fix bugs and
minor details, I don't see any reason to wait. But I haven't had time to test
the new KJV and ESV with it.
I'll add my voice to a long list requesting branching for the release. Greg has
volunteered to manage such. I
Hi Troy,
I'm worried about a number of things relating to titles, but these worries
are all focused on module build tools.
i.e. How well the output from usfm2osis.py matches what osis2mod expects.
Until this sleuthing is completed, and my evidence is presented to the right
audience,
I would not
Things have been quiet for a bit. I have all the patches in that are on my todo
list. Anyone else have outstanding issues? Now is the time to speak up.
Chris, any feedback on my Ralfs suggestion?
Peter, still binding troubles? Can you give me your exact commands executed and
I'll try them here.
52 matches
Mail list logo
