Karl,
RV1960 is a copyrighted work, for which we do not have permission to
distribute.
Copyright belongs to the Bible Society of Spain.
SpaRVG2010 was a provisional build that I made on my PC (2012-01-07), and
was replaced by the SpaRVG module version 1.1 updated to the 2010 edition
(2012-01-19).
Greg Hellings took up the NASB project.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/NASB-tp4654673p4654681.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
sword-devel mailing list: sword-devel@cr
Okay, at first it looked like 'make install' only copied the libsword-1.7.3.so
and not the libsword.so.
I was linking against libsword.so which didn't have the definitions of
renderText.
When I linked against libsword-1.7.3.so - it was fine.
I removed all the sword libs on my /usr/local/lib dir
Is one not a symlink to the other?
On March 19, 2015 3:19:40 PM EDT, Daniel Sheffield wrote:
>Okay, at first it looked like 'make install' only copied the
>libsword-1.7.3.so and not the libsword.so.
>I was linking against libsword.so which didn't have the definitions of
>renderText.
>When I linke
I'm waiting on DM to release the new version of BibleDesktop which has
several style handling improvements utilized by the NASB. Troy has
mandated that the module appear properly in the main desktop
applications, and that's the last one to come into line.
Once that's done, then we can move on to t
Indeed it is .
But I double checked: -lsword doesn't work but -lsword-1.7.3 does... is
that normal?
--
In the beginning Kibo created the Internet. Now the Internet was formless,
and empty. Randomness was upon the face of computing, and the Spirit of
ARPA moved upon the face of the computers. Then
Daniel,
My guess is that you have a libsword.so in /usr/lib or /usr/lib64 or
someplace else causing problems.
Troy
On 03/19/2015 02:47 PM, Daniel Sheffield wrote:
Indeed it is .
But I double checked: -lsword doesn't work but -lsword-1.7.3 does...
is that normal?
--
In the beginning Kibo
Thanks Troy,
Your guess was correct.
:)
Cheers,
Daniel
On Thu 19Mar15 06:20:22PM, Troy A. Griffitts wrote:
> Daniel,
>
> My guess is that you have a libsword.so in /usr/lib or /usr/lib64 or someplace
> else causing problems.
>
> Troy
>
>
>
> On 03/19/2015 02:47 PM, Daniel Sheffield wrote:
>
