On 2019.10.10 18:27, jvap...@gmail.com wrote:
Thanks guys!
But, why do I get this then?
sqlcipher.x86_64 : SQLCipher is an open source extension to SQLite
that
provides transparent 256-bit AES encryption of database files.
sqlcipher.i686 : SQLCipher is an open source extension to SQLite that
provides transparent 256-bit AES encryption of database files.
sqlcipher.x86_64 : SQLCipher is an open source extension to SQLite
that
provides transparent 256-bit AES encryption of database files.
sqlcipher-devel.x86_64 : Development files for sqlcipher
sqlcipher-devel.i686 : Development files for sqlcipher
sqlcipher-devel.x86_64 : Development files for sqlcipher
=======================================================================
==================================================== Name Matched:
sqlcipher
=======================================================================
====================================================
libgda-sqlcipher.x86_64 : SQLiteCipher provider for libgda
libgda-sqlcipher.x86_64 : SQLiteCipher provider for libgda
I'm just guessing, but the above looks like output for some query about
packages with sqlcipher in the name. If so, it's just informative.
[kodemonkey@thinkpad build]$ sudo dnf install sqlcipher-devel.x86_64
Last metadata expiration check: 0:20:52 ago on Thu 10 Oct 2019
05:05:01
PM CDT.
Package sqlcipher-devel-3.4.1-5.fc30.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[kodemonkey@thinkpad build]$
It seems it is already installed.
Yes, it looks that way. What's the question here? If you are planning
on keeping your KMM data in a .xml or .kmy (gzipped xml) file, then you
do not need any sql related packages. It doesn't hurt anything if they
are installed, but you don't need them.
It is driving me nuts! LOL
I know it can be confusing, but I'm not sure what your current problem
or question is. If you have already run cmake once, then run "ccmake
." in the build directory, so you can browse all the parameters, and
turn off those you don't need. Because of all those options, I often
write a script to run cmake, with explicit values for all the ENABLE_
options, just so I know what I'm requestiong, and don't rely on default
values. It's perhaps a bit harder to set up, but it saves some sanity
in the long run.
I will try the libofx method. Thanks!
JV
On Thu, 2019-10-10 at 19:29 +0200, Thomas Baumgart wrote:
> On Donnerstag, 10. Oktober 2019 18:29:32 CEST Jack wrote:
>
> > Hello JV,
> >
> > On 2019.10.09 22:35, jvap...@gmail.com wrote:
> > > Thanks Thomas and Jack.
> > >
> > > I am a little confused/in shock now. :) It sounds like I do not
> need
> > > to use AQBanking? I believe I need it since I use it to allow me
> to
> > > update my accounts (download) transactions. Are you saying there
> is
> > > another way to set up a connection to the banks/Credit Card
> companies
> > > server to download transactions?
>
> > If you are in the US (and much of the world,) you have a
> choice. As
> > you have done in the past, you can use Aqbanking for OFX direct
> > connect. However, you can also use libofx, which is already
> included
> > in the KMM source. To do that, you would enable OFXIMPORTER at
> cmake
> > time, and you can disable KBANKING so it doesn't bother to look
> for
> > aqbanking or gwenhywfar. That's what I use for banking,
> investment,
> > and credit cards.
> > >
> > > I know I can manually download an OFX(qfx) file and then import
> it
> > > into KMyMoney but I really like the ability to right click and
> say
> > > 'update account'. I have always thought I needed AqBanking for
> that.
> > There are some banking systems, notably in Germany/EU, which use
> > features not handled by libofx, and thus those do require to
> enable
> > KBANKING, and use aqbanking and gwenhywfar.
> >
> > If you are not aware, once you have done the initial cmake, then
if
> you
> > run "ccmake ." in the build directory, you can see (and adjust)
all
> the
> > ENABLE_ settings, and turn OFF those you don't need.
> > >
> > > Anyways, I am hitting some other compile issue now with missing
> > > package. I will fix this first before I can test.
> > >
> > > [ 12%] Building CXX object
> > >
>
kmymoney/plugins/sqlcipher/CMakeFiles/qsqlcipher.dir/qsql_sqlite.cpp.
> o
> > >
>
/home/kodemonkey/git/kmymoney_jv/build/kmymoney/plugins/sqlcipher/qsq
> l_
> > > sqlite.cpp:63:10: fatal error:
> QtSql/private/qsqlcachedresult_p.h: No
> > > such file or directory
> > > 63 | #include <QtSql/private/qsqlcachedresult_p.h>
> > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > My guess is that you do not have sqlcipher installed, but you
> would
> > only need it if you wanted to save your KMM data as an encrypted
> sqlite
> > file. You can disable SQLCIPHER (and even SQLSTORAGE) to stop it
> from
> > looking for those files.
> > >
> > > Also, thanks Thomas, you answered a question I was not sure I
> asked
> > > yet. Whether the expectation is for us to download the AqBanking
> and
> > > Gwenhywfar software and compile it ourselves or if we are
> expecting
> > > the distribution to already include the latest and greatest.
>
> > In general, distributions should have the necessary dependencies
> > available as packages. However, some distributions (especially
> some
> > LTS versions) lag a bit. If you are compiling from git head
> (either
> > master or 5.0,) and especially if recent commits to KMM are using
> brand
> > new features in those other libraries, then it does often become
> > necessary for you to download and compile them yourself.
>
> I have nothing to add to this. Jack, very good explanation.
>
>
> --
>
> Regards
>
> Thomas Baumgart
>
> https://www.signal.org/ Signal, the better WhatsApp
> -------------------------------------------------------------
> Q: What does a house wear? A: Address
> -------------------------------------------------------------
>
