Hi David,
On 30 Oct 2016, at 11:08 , Christian Dávid wrote:
> the information that alkimia <= 6.0.0 fetches Qt 5 is wrong!
>
> Alkimia <= 5 is Qt 4 based, it is fetched indirectly over the line
>
> find_package(KDE4 4.6.0 REQUIRED)
>
> As written in another thread, the issue is that alkimia 4.
Hi timothy,
the information that alkimia <= 6.0.0 fetches Qt 5 is wrong!
Alkimia <= 5 is Qt 4 based, it is fetched indirectly over the line
find_package(KDE4 4.6.0 REQUIRED)
As written in another thread, the issue is that alkimia 4.x shippes a find
module which just finds any version of alkimi
Thanks, I have also built the latest Version 4.8.0-485aea8e20 from git.
It seems to be running fine so far.
Will this be the default for some time or will there be an option to
compile with libalkimia 4.3.2. until Debian gets 5.0 in the repository?
Regards
Timothy
On Sun, 2016-10-23 at 01:23 +0
Hi devs,
On 18 Oct 2016, at 09:42 , timothy wrote:
> If consideration is being given to the latter option, would not
> reverting to alkimia 4.3.2 achieve the same purpose. Or at least a
> compile/make option for this version of libalkimia. This would allow
> people with my predicament to get bugs
Hi
I am using LMDE2 Mint Debian and cannot add libalkimia >= 5.0 without
major changes to my whole system. A recent post from Alan mentions:-
>> alkimia >= 5.0.0 fetches Qt5 dependencies into a project using it.
You
>> need to revert alkimia to version <= 4.3.2. Another option would be
to
>> (re)
Hi
I am using LMDE2 Mint Debian and cannot add libalkimia >= 5.0 without
major changes to my whole system. A recent post from Alan mentions:-
>> alkimia >= 5.0.0 fetches Qt5 dependencies into a project using it.
>> You need to revert alkimia to version <= 4.3.2. Another option would be
>> to (re)
