Re: [sword-devel] SWORD + Qt better support

2013-07-29 Thread Jaak Ristioja
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! On 29.07.2013 11:08, Troy A. Griffitts wrote: > From the 2 responses from people who use the Bibletime wrappers, > it sounds like there are many things which are useful for building > At apps with SWORD. When I responded 'No' to Jaak's prompting t

Re: [sword-devel] SWORD + Qt better support

2013-07-29 Thread Troy A. Griffitts
Good morning, Just a couple quick comments about my messages from last night to clear up possible misunderstandings. >From the 2 responses from people who use the Bibletime wrappers, it sounds >like there are many things which are useful for building At apps with SWORD. >When I responded 'No'

Re: [sword-devel] SWORD + Qt better support

2013-07-28 Thread Troy A. Griffitts
On 07/28/2013 09:29 PM, Greg Hellings wrote: On Sun, Jul 28, 2013 at 2:07 PM, Jaak Ristioja > wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! On 28.07.2013 20:36, Troy A. Griffitts wrote: > Hey guys. I spent today to try to add a few met

Re: [sword-devel] SWORD + Qt better support

2013-07-28 Thread Troy A. Griffitts
Sorry Karl, I didn't test with shared-enabled. I have now and it works --without-qt and --with-qt both on F19. Let me know. (Yeah, I understand throwing a couple new methods in at the last minute isn't wise. But they are additional methods so they shouldn't break existing stuff. They add

Re: [sword-devel] SWORD + Qt better support

2013-07-28 Thread Greg Hellings
On Sun, Jul 28, 2013 at 2:07 PM, Jaak Ristioja wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi! > > On 28.07.2013 20:36, Troy A. Griffitts wrote: > > Hey guys. I spent today to try to add a few methods into 1.7.0 > > before we push it out the door to ease your (those building Qt

Re: [sword-devel] SWORD + Qt better support

2013-07-28 Thread Jaak Ristioja
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! On 28.07.2013 20:36, Troy A. Griffitts wrote: > Hey guys. I spent today to try to add a few methods into 1.7.0 > before we push it out the door to ease your (those building Qt > frontends) integration with SWORD. I'm sorry, but this doesn't seem

Re: [sword-devel] SWORD + Qt better support

2013-07-28 Thread Karl Kleinpaste
Also: libtool: link: g++ -O3 -fPIC -D_ICU_ -ftemplate-depth-25 -DCURLAVAILABLE -DCURLSFTPAVAILABLE -I/usr/include -I/usr/lib64 -DUSELUCENE -I/usr/lib64 -o .libs/buildtest buildtest.o ./lib/.libs/libsword.so -L/usr/lib64 -lz -licui18n -licuuc -licudata -lpthread -ldl -lm -licuio -lcurl -lclucen

Re: [sword-devel] SWORD + Qt better support

2013-07-28 Thread Karl Kleinpaste
"Troy A. Griffitts" writes: > Hey guys. I spent today to try to add a few methods into 1.7.0 before we > push it out the door to ease your (those building Qt frontends) > integration with SWORD. ... checking for vsnprintf... yes checking for QT4... yes checking for moc-qt4... /usr/lib64/qt4/bin/

[sword-devel] SWORD + Qt better support

2013-07-28 Thread Troy A. Griffitts
Hey guys. I spent today to try to add a few methods into 1.7.0 before we push it out the door to ease your (those building Qt frontends) integration with SWORD. It's really not much but I wanted to target at least a minimal Qt app without adding any extra conversion code. I've added this min