17 Feb
2014
17 Feb
'14
7:20 p.m.
The issue seems to be in this obscure sqlite source
included in
kmymoney:
23011-qt-sqlite3-0.2.tar.gz
that explains why the files were missed in the q->tq renaming
scheme.
That explains what?
I'll see
if I can come up with some sort of patch, but the git tree
including an external
.tar.gz source of sqlite3 seems like a really bad idea :)
Yet this is working for everybody else?
If kmymoney does not include an intrnal sqlite engine, like amarok,
then kmymoney should be built against the external installed
version. There probably is a configuration option to build with the
external version or an option to not build with the internal
version, which then reverts to the external version. Probably
should first test that before ripping sources.
Darrell
17 Feb
17 Feb
7:54 p.m.
New subject: [trinity-devel] kmymoney FTBFS - fatal error: qsqldriverplugin.h: No such file
On 02/17/2014 09:20 PM, Darrell Anderson wrote:
Well, crud. I'll check again. I just opened a bug that I'll have to close.
I've
pulled my hair out on this one and it just seems fried.
http://bugs.pearsoncomputing.net/bugzilla/show_bug.cgi?id=1942
I'll see if I can figure out what is up. I'll go close the bug since it works
for everyone else...
I am just using a standard build and kmymoney will not find any of the
tqtinterface includes, etc..
--
David C. Rankin, J.D.,P.E.
The issue
seems to be in this obscure sqlite source included in
kmymoney:
23011-qt-sqlite3-0.2.tar.gz
that explains why the files were missed in the q->tq renaming
scheme.
That explains what?
I'll see
if I can come up with some sort of patch, but the git tree
including an external
.tar.gz source of sqlite3 seems like a really bad idea :)
Yet this is working for everybody else?
If kmymoney does not include an intrnal sqlite engine, like amarok,
then kmymoney should be built against the external installed
version. There probably is a configuration option to build with the
external version or an option to not build with the internal
version, which then reverts to the external version. Probably
should first test that before ripping sources.
Darrell
8:22 p.m.
New subject: [trinity-devel] kmymoney FTBFS - fatal error: qsqldriverplugin.h: No such file
On 02/17/2014 09:54 PM, David C. Rankin wrote:
On 02/17/2014 09:20 PM, Darrell Anderson wrote:
Well, crud. I'll check again. I just opened a bug that I'll have to close.
I've
pulled my hair out on this one and it just seems fried.
http://bugs.pearsoncomputing.net/bugzilla/show_bug.cgi?id=1942
I'll see if I can figure out what is up. I'll go close the bug since it works
for everyone else...
I am just using a standard build and kmymoney will not find any of the
tqtinterface includes, etc..
That explains your success:
--disable-sqlite3 \
it is on by default, and unless you disable it, you will find all of the same
problems I am reporting....
--
David C. Rankin, J.D.,P.E.
The
issue seems to be in this obscure sqlite source included in
kmymoney:
23011-qt-sqlite3-0.2.tar.gz
that explains why the files were missed in the q->tq renaming
scheme.
That explains what?
I'll see
if I can come up with some sort of patch, but the git tree
including an external
.tar.gz source of sqlite3 seems like a really bad idea :)
Yet this is working for everybody else?
If kmymoney does not include an intrnal sqlite engine, like amarok,
then kmymoney should be built against the external installed
version. There probably is a configuration option to build with the
external version or an option to not build with the internal
version, which then reverts to the external version. Probably
should first test that before ripping sources.
Darrell
8:52 p.m.
New subject: [trinity-devel] kmymoney FTBFS - fatal error: qsqldriverplugin.h: No such file
On 02/17/2014 10:22 PM, David C. Rankin wrote:
That explains your success:
--disable-sqlite3 \
it is on by default, and unless you disable it, you will find all of the same
problems I am reporting....
In fact, unless you specifically disable virtually all the options in kmymoney,
the build fails. Try building with just the default options. I've opened:
http://bugs.pearsoncomputing.net/bugzilla/show_bug.cgi?id=1942
set at major due to the fact that unless you disable all the options for
kmymoney, the build fails.
Further, the 23011-qt-sqlite3-0.2.tar.gz contained within the tree is NOT
updated to work with tqtinterface or tqt3. There is no database backend
capability for kmymoney at all. The only reason it works for anyone building on
R14 is if they are building with --disable-sqlite3.
What if you want an actual database backend for kmymoney?
In kmymoney's case "works for me" is a qualified "works for me" at
best. The
documentation blows up the build as well unless you specifically disable the pdf
documents or install a 3rd party perl package of html2ps:
<snip>
make[4]: Leaving directory '/build/tde-kmymoney/src/kmymoney/doc/en'
/opt/trinity/bin/meinproc --check --stylesheet `dirname
/opt/trinity/share/apps/ksgmltools2/customization/tde-chunk.xsl`/tde-nochunk.xsl
./index.docbook -o index.html;
recode utf8..latin1 index.html || :
recode: index.html failed: Invalid input in step `UTF-8..ISO-8859-1'
html2ps -o kmymoney-user.ps -n index.html
make[3]: html2ps: Command not found
Makefile:755: recipe for target 'kmymoney-user.pdf' failed
This despite ./configure thinking all is hunky-dory. Further, if html2ps is NOT
present on the system the autoconf setup should test and handle it
automatically, not crash 9 minutes into the build. 99% of the other TDE apps
build correctly with the default options - kmymoney is a visible exception
compared to the readiness of the remaining applications.
No this is not "critical", but is certainly is not a "works for everyone
else".
--
David C. Rankin, J.D.,P.E.
3741
days inactive
3741
days old
3 comments
2 participants
participants (2)
-
Darrell Anderson -
David C. Rankin