[sword-devel] SWORD + Qt better support

[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 a signature in the headers, so if we don't do 
it now, then 1.7.x will never get them.  These were my + that made me 
want to try.  Maybe they'll get dropped, considering the other recent 
responses).

Troy



On 07/28/2013 08:22 PM, Karl Kleinpaste wrote:
> 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 -lclucene
> ./lib/.libs/libsword.so: undefined reference to `QString::fromUtf8(char const*, int)'
> ./lib/.libs/libsword.so: undefined reference to `qFree(void*)'
> ./lib/.libs/libsword.so: undefined reference to `QString::toUtf8() const'
> collect2: ld returned 1 exit status
> make[1]: *** [buildtest] Error 1
> make[1]: Leaving directory `/home/karl/src/bible/sword'
> make: *** [all-recursive] Error 1
>
> Is it wise, after almost a year of stress over whether 1.7.0 will get
> out the door, to be adding brand new, untested capabilities?  When
> you've been talking about the "final stretch" for 2 months?  So that
> now, today, you add this stuff?
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page