Am 05.11.2016 um 12:42 schrieb Christian David:
> Hi Ralf,
>
> I still do not like this. The reason is that this just fixes the symptom, not
> the problem. With these changes we make a huge technical dept. Exept for
> version 4.8 we solved nearly all problems mentioned here already.
Except coin
Hi Ralf,
I still do not like this. The reason is that this just fixes the symptom, not
the problem. With these changes we make a huge technical dept. Exept for
version 4.8 we solved nearly all problems mentioned here already. So all
changes are only a workaround to enable coinstallablity with a
Am 03.11.2016 um 15:33 schrieb Jack:
> It took me a while to see it, but Alan is asking if LibAalkimia is correct or
> if each call should be LibAlkimia. I can see how the double a could either
> jump out at you or simply be not noticed.
no, the name is LibAlkimia. Sorry for confusing.
Ralf
It took me a while to see it, but Alan is asking if LibAalkimia is correct or
if each call should be LibAlkimia. I can see how the double a could either
jump out at you or simply be not noticed.
On Nov 3, 2016 3:24 AM, Ralf Habacker wrote:
>
> Am 03.11.2016 um 00:25 schrieb aga:
> > I don't k
I replied earlier to this but it seems not to have survived, so here it
is again. And I hope I'm not confused here.
"
Sorry,it was the duplication 'Aa' I was referring to. It jumps out at me
so I didn't make it clearer."
Allan
On 03/11/16 07:24, Ralf Habacker wrote:
> Am 03.11.2016 um 00:25 sch
bject: Re: More libalkimia problems/questions was: problems compiling 4.8 on
system with both qt4 and qt5
Am 03.11.2016 um 00:25 schrieb aga:
> I don't know if this is/these are typos or deliberate, or even if
> they're important, or fixed already, but, in this chunk, there are four
&
Am 03.11.2016 um 00:25 schrieb aga:
> I don't know if this is/these are typos or deliberate, or even if
> they're important, or fixed already, but, in this chunk, there are four
> LibAalkimiaxx's.
These are two variants to show how it could be performed:
variant 1:
> if(QT4_FOUND)
>>find_packa
I don't know if this is/these are typos or deliberate, or even if
they're important, or fixed already, but, in this chunk, there are four
LibAalkimiaxx's.
if(QT4_FOUND)
>find_package(LibAalkimia4)
>if(NOT LIBALKIMIA4_FOUND)
> find_package(LibAalkimia)
>endif()
> else()
>find_
On 2016.11.02 14:35, Ralf Habacker wrote:
Am 01.11.2016 um 00:05 schrieb Jack:
For Gentoo, if two versions are coinstallable, they get assigned to
different "slots" and in this case, I think the slot number would
easily correspond to the qt version (4 or 5) to align with other qt
and kde
Am 01.11.2016 um 00:05 schrieb Jack:
> For Gentoo, if two versions are coinstallable, they get assigned to
> different "slots" and in this case, I think the slot number would
> easily correspond to the qt version (4 or 5) to align with other qt
> and kde packages. Also, as Gentoo is a source base
On 2016.10.31 18:23, Ralf Habacker wrote:
Am 31.10.2016 um 19:45 schrieb Christian David:
> Thanks for this perfect overview! I notice that Alkimia 5 should
install its
> cmake files into .../cmake/LibAlkimia-5.0/..., everything else
looks okay. The
> cmake files should be in seperate directo
Am 31.10.2016 um 19:45 schrieb Christian David:
> Thanks for this perfect overview! I notice that Alkimia 5 should install its
> cmake files into .../cmake/LibAlkimia-5.0/..., everything else looks okay.
> The
> cmake files should be in seperate directories because cmake expects it that
> way.
Hi Ralf,
Thanks for this perfect overview! I notice that Alkimia 5 should install its
cmake files into .../cmake/LibAlkimia-5.0/..., everything else looks okay. The
cmake files should be in seperate directories because cmake expects it that
way.
However, we could rename the include directory i
Am 30.10.2016 um 19:03 schrieb Christian David:
> Am Sonntag, 30. Oktober 2016, 18:49:51 schrieb Ralf Habacker:
> […]
>> Your approach also includes the case of a coinstallation, say a stable
>> 4.8.x version for real work and kf5 based version for development ?
> […]
>
> Hi Ralf,
>
> If you mean K
Am Sonntag, 30. Oktober 2016, 18:49:51 schrieb Ralf Habacker:
[…]
> Your approach also includes the case of a coinstallation, say a stable
> 4.8.x version for real work and kf5 based version for development ?
[…]
Hi Ralf,
If you mean KMyMoney 4.8.x and KF5 then yes. We only need to add the requir
Am 30.10.2016 um 10:59 schrieb Christian Dávid:
> My current suggestion to solve this issue is:
>
> 1) Let alkimia 4 die. Alkimia 5 is a perfect replacement. The only reason for
> the version jump was a really tiny change which caused ABI incompatibility.
> Any code that compiles with alkimia 4 s
Hello All,
I am sorry that I answer this late. Hopefully I can still help.
The cause of all trouble in alkimia is that the version checking is not done
correctly. Pre alkimia 5 had a find module (which is wrong in the first place)
which did not check any version. Also it would find any alkimia
Hi Ralf,
are you sure? Alkimia 5 is Qt4 & KDE4 based! The first alkimia version with Qt
5 is/will be alkimia 6. There should be no reason to use 4.x anymore.
Greetings
Christian
> Ralf Habacker hat am 17. Oktober 2016 um 08:44
> geschrieben:
>
>
> Am 17.10.2016 um 00:52 schrieb Jack:
> > So
Am 25.10.2016 um 19:12 schrieb Marko Käning:
>
> is ECM needed for Qt4? I always thought that it would only be needed for
> Qt5/KF5…
ECM is part of the former only Qt5 supporting alkimia build system.
There are several ecm related macros used:
autotests/CMakeLists.txt:5:ecm_mark_as_test(alkvalu
On 25 Oct 2016, at 19:20 , Ralf Habacker wrote:
> ECM is part of the former only Qt5 supporting alkimia build system.
> There are several ecm related macros used:
>
> autotests/CMakeLists.txt:5:ecm_mark_as_test(alkvaluetest)
> autotests/CMakeLists.txt:11:ecm_mark_as_test(alkquoteitemtest)
> autot
Hi Ralf,
On 25 Oct 2016, at 14:44 , timothy wrote:
> However find_package(ECM 0.0.11 REQUIRED NO_MODULE). I downloaded ECM
> 0.0.11 and built it. But it also has qt5 dependencies.
is ECM needed for Qt4? I always thought that it would only be needed for
Qt5/KF5…
Greets,
Marko
Updated to the latest ECM Debian version 5.27.
Result is now successful as expected. Sorry for the inconvenience.
Perhaps the minimum required version of ECM should be upped in the
CMakeLists.txt file.
I actually thought that version 0.0.11 was the specific required version
and looked only for
Am 25.10.2016 um 15:05 schrieb timothy:
>>> However find_package(ECM 0.0.11 REQUIRED NO_MODULE). I downloaded ECM
>>> 0.0.11 and built it. But it also has qt5 dependencies.
I see. 0.0.11 is very old -> mentioned as "alpha2 preparation: ECM is
now 0.0.11"
You should update to a more recent version
I did not clone, but downloaded the ZIP file if that makes any
difference.
Timothy
On Tue, 2016-10-25 at 14:51 +0200, Ralf Habacker wrote:
> Am 25.10.2016 um 14:44 schrieb timothy:
> > Hi Ralf
> >
> > I have tried building alkimia from your code with the qt4 option.
> >
> > However find_package(
timothy@tim
~/data/Downloads/git/libalkimia/ralf_habacker/alkimia-master/build $
cmake .. -DBUILD_QT4=1
CMake Error at /usr/share/ECM/cmake/ECMConfig.cmake:45 (find_package):
By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project
has
asked CMake to find a package configuration f
Am 25.10.2016 um 14:44 schrieb timothy:
> Hi Ralf
>
> I have tried building alkimia from your code with the qt4 option.
>
> However find_package(ECM 0.0.11 REQUIRED NO_MODULE). I downloaded ECM
> 0.0.11 and built it. But it also has qt5 dependencies.
After cloning relatee git repo and running
cd a
Hi Ralf
I have tried building alkimia from your code with the qt4 option.
However find_package(ECM 0.0.11 REQUIRED NO_MODULE). I downloaded ECM
0.0.11 and built it. But it also has qt5 dependencies.
I am not sure if I am doing something stupid.
Regards
Timothy
On Tue, 2016-10-25 at 09:00 +020
Hi Jack, hi Thomas,
I fixed the addressed issues and updated an improved implementation, see
https://github.com/rhabacker/alkimia
Please take a look and report any issues. If there are no one left I can
add a review request for inclusion into public alkamia git repo.
Ralf
Am 24.10.2016 um 18:07 schrieb Jack:
>
> Unless I am missing something (which is quite possible) once you make
> this change, one version or the other is going to have to change the
> name of it's header, pkgconfig, and cmake files, and any user of that
> version will also have to adapt. It's not
On 2016.10.24 11:59, Ralf Habacker wrote:
Am 24.10.2016 um 17:10 schrieb Jack:
> I do agree it is a good idea, but it is just a bit difficult since
> there has already been a release of a qt5 version with the old name.
Technical this could be solved by incrementing the so number of the
library. R
Am 24.10.2016 um 17:10 schrieb Jack:
> I do agree it is a good idea, but it is just a bit difficult since
> there has already been a release of a qt5 version with the old name.
Technical this could be solved by incrementing the so number of the
library. Recent Qt4 based releases provides libalkimia
On 2016.10.24 11:20, Ralf Habacker wrote:
Am 24.10.2016 um 17:10 schrieb Jack:
> Not only must the package name not conflict, but they must not both
> install the same files.
yes
> I know all the .so files would be different, but right now, things
> like the pkgconfig, cmake, and header files are
Am 24.10.2016 um 17:10 schrieb Jack:
> Not only must the package name not conflict, but they must not both
> install the same files.
yes
> I know all the .so files would be different, but right now, things
> like the pkgconfig, cmake, and header files are identically named. If
> you change the q
On 2016.10.24 05:43, Ralf Habacker wrote:
Am 23.10.2016 um 10:46 schrieb Thomas Baumgart:
> I took a glimpse and this seems to make sense. Would then in
KMyMoney 4.8
> something like
>
> find_package(LibAlkimiaQt4)
> if (not found)
> find_package(LibAlkimia REQUIRED)
> endif()
>
> be
Am 23.10.2016 um 10:46 schrieb Thomas Baumgart:
> I took a glimpse and this seems to make sense. Would then in KMyMoney 4.8
> something like
>
> find_package(LibAlkimiaQt4)
> if (not found)
> find_package(LibAlkimia REQUIRED)
> endif()
>
> be possible to further automate for both scenari
Hi,
On Saturday 22 October 2016 23:20:14 Ralf Habacker wrote:
> Am 22.10.2016 um 20:02 schrieb Jack:
[...]
> > Am I just trying the impossible?
>
> No, I just pushed a commit to a personal repo at
> https://github.com/rhabacker/alkimia, which readd's Qt4 support to
> latest version of alkimia
First, the good news: I have reverted to libalkimia 4.3.2 and created a
successful gentoo ebuild for 4.8 git head. I have successfully
remapped my Chase credit card usingn the Client-UUID. Now, at least I
can catch up on actually tracking my finances separate from working on
all the below
Am 22.10.2016 um 20:02 schrieb Jack:
> On 2016.10.17 02:44, Ralf Habacker wrote:
>> Am 17.10.2016 um 00:52 schrieb Jack:
>> > Something Alan sent me made me look and think it might have been
>> > because alkimia was compiled with qt5, but I'm no longer sure about
>> that.
>> alkimia >= 5.0.0 fetch
On 2016.10.17 02:44, Ralf Habacker wrote:
Am 17.10.2016 um 00:52 schrieb Jack:
> Something Alan sent me made me look and think it might have been
> because alkimia was compiled with qt5, but I'm no longer sure about
that.
alkimia >= 5.0.0 fetches Qt5 dependencies into a project using it. You
n
Am 18.10.2016 um 02:29 schrieb Jack:
> On 2016.10.17 02:44, Ralf Habacker wrote:
>> Am 17.10.2016 um 00:52 schrieb Jack:
>> > Something Alan sent me made me look and think it might have been
>> > because alkimia was compiled with qt5, but I'm no longer sure about
>> that.
>> alkimia >= 5.0.0 fetche
On 2016.10.17 02:44, Ralf Habacker wrote:
Am 17.10.2016 um 00:52 schrieb Jack:
> Something Alan sent me made me look and think it might have been
> because alkimia was compiled with qt5, but I'm no longer sure about
that.
alkimia >= 5.0.0 fetches Qt5 dependencies into a project using it. You
n
Am 17.10.2016 um 00:52 schrieb Jack:
> Something Alan sent me made me look and think it might have been
> because alkimia was compiled with qt5, but I'm no longer sure about that.
alkimia >= 5.0.0 fetches Qt5 dependencies into a project using it. You
need to revert alkimia to version <= 4.3.2. Ano
On 2016.10.16 12:08, Thomas Baumgart wrote:
Jack
On Saturday 15 October 2016 16:14:00 Jack Ostroff wrote:
> I think this is at least part of my problem trying to build from 4.8
> branch on both my home Gentoo system and a VirtualBox Kubuntu
16.10. I
> know I have enough of qt5 installed, as
Jack
On Saturday 15 October 2016 16:14:00 Jack Ostroff wrote:
> I think this is at least part of my problem trying to build from 4.8
> branch on both my home Gentoo system and a VirtualBox Kubuntu 16.10. I
> know I have enough of qt5 installed, as I have successfully compiled
> from git head. I
I think this is at least part of my problem trying to build from 4.8
branch on both my home Gentoo system and a VirtualBox Kubuntu 16.10. I
know I have enough of qt5 installed, as I have successfully compiled
from git head. I'm pretty sure I have enough of qt4 installed, but it
seems that the
45 matches
Mail list logo
