I have managed to get most of the way to fixing the problem. I added
QT_PLUGIN_PATH to the environment variables and pointed to the plugin
directory in my build folder. I put my build folder first so it finds the
correct plugin (just compiled) to use.
Now I am able to load a kmy file and a
Am 08.04.22 um 08:59 schrieb Thomas Baumgart via KMyMoney-devel:
That shows, that you build the application and plugins but did not install them.
For KMyMoney to pick them up, you need to install the application in your KDE
environment (my preferred way) or modify settings (env variables) so that
Hi,
On Freitag, 8. April 2022 01:14:06 CEST Chris via KMyMoney-devel wrote:
> Hi
>
> I am compiling kmymoney to run the debugger over a couple of plugins. When I
> do so setting a breakpoint fails in the source code of the plugin I want to
> debug (csv import).
>
> I read that its best to sta
o plugins shown
As these plugins (including csv import) all get compiled along with the
rest of KMM, I'm not convinced static linking is necessary, or even
helpful. The one thing I can say from debugging plugins in other
programs is that the debugger won't know anything about the p
Hi
I am compiling kmymoney to run the debugger over a couple of plugins. When I
do so setting a breakpoint fails in the source code of the plugin I want to
debug (csv import).
I read that its best to statically link the plugins for debugging purposes
so I recompiled using -DBUILD_SHARED=OFF
On 2014.09.11 14:09, Christian Dávid wrote:
Am Samstag, 6. September 2014, 10:01:54 schrieb Jack:
[snip]
I don't think I ever clarified that I'm only working on Linux
(Gentoo). […]
Good, everything is easier then ;)
> > # Run cmake and set an install prefix
> > # "make install" will co
Am Samstag, 6. September 2014, 10:01:54 schrieb Jack:
> I've just tried this again, and it's still not working quite as I
> want/expect. Hopefully I'm just missing some step or environment
> variable.
> I don't think I ever clarified that I'm only working on Linux
> (Gentoo). […]
Good, everything
I've just tried this again, and it's still not working quite as I
want/expect. Hopefully I'm just missing some step or environment
variable.
On 2014.03.31 05:32, Christian Dávid wrote:
As this comes up quite often I retried my approach from scratch. You
"just" need all build dependencies i
On 2014.03.31 05:32, Christian Dávid wrote:
Am Sonntag, 30. März 2014, 19:08:08 schrieb Jack:
It would appear in KDE you need to pollute your application name
space to debug a plugin which means you cannot simultaneously have
a devel version and a release version running at the same time.
Ah,
It checks every file to see if it needs rebuilding and I haven't worked out
how to stop that. Of course it doesnt take overly long. probably less than 1
minute but I find it annoying. I did say I was impatient.
The symlink solution solves it though, I just deploy once, create the
symlink to
On 01/04/14 10:35, Chris wrote:
Yes Thank you for all your information
I have chewed it over and decided that the best bet for me is to trash
my entire install and start over once again. I shall have to see how it
goes once the environment is rebuilt. I could not get QTCreator to
properly debug
Yes Thank you for all your information
I have chewed it over and decided that the best bet for me is to trash my
entire install and start over once again. I shall have to see how it goes
once the environment is rebuilt. I could not get QTCreator to properly debug
the plugin It simply would no
Hi Christian,
A big thanks for providing this detailed information. I hope that this ends
the debate over the "supposed lack of developer/user mixing support" in the
platform and the application.
Regards,
Cristian
2014-03-31 12:32 GMT+03:00 Christian Dávid :
> Hello!
>
> Am Sonntag, 30. März 2
Hello!
Am Sonntag, 30. März 2014, 19:08:08 schrieb Jack:
> > It would appear in KDE you need to pollute your application name
> > space to debug a plugin which means you cannot simultaneously have a
> > devel version and a release version running at the same time.
>
> Ah, you have run into on
Hi Jack
Thanks for the reply.
I suspect most developers work in a VM, under windows that means a slow
machine and the cost of a license. So I wont be doing that. I could just
develop in a kde linux platform but as I want to make specific changes to
suit Aussie small businesses who mostly work
On 2014.03.29 18:53, Chris wrote:
[snip]
It would appear in KDE you need to pollute your application name
space to debug a plugin which means you cannot simultaneously have a
devel version and a release version running at the same time.
Ah, you have run into one of my recurring rants. I h
I have been able to set it up so I can debug the plugin but it is far from a
satisfactory solution and there is an oddity.
Firstly I did a full install from an nmake version of the build system (for
some reason the msvc2010 build doesn't install properly. I haven't
determined why)
Then I c
On 29/03/14 23:35, Chris wrote:
Hmm
Perhaps dejavu sans needs to be included in the install package as its
not an installed font in mswin7, by including it in the install some of
these inconstancies may be ironed out.
It now appears that my choice of DejaVu Sans doesn't get into the build
any
On 29/03/14 23:04, Chris wrote:
Hi Allan
If you look at the source of the ui file there is no font specified. So
you are picking up the font *QT* chooses as the default.
Yes, neither the UI file, nor the built ui.h file give a font name.
As it shows in QtDesigner, it appears that it gets
Hmm
Perhaps dejavu sans needs to be included in the install package as its not
an installed font in mswin7, by including it in the install some of these
inconstancies may be ironed out.
if installing a font is a bit over the top QT includes...
int QFontDatabase::addApplicationFont ( const QSt
Hi Allan
If you look at the source of the ui file there is no font specified. So you
are picking up the font *QT* chooses as the default.
Original csvimport ui file..
modified using qtdesigner file...
Arial
Like you I have found fonts are not the only problems. Now
Hi
Yes I worked out that kmymoney wasn't using QT's plugin mechanism but
instead KDE's
I was just trying to workout the desktop files and where they are kept when
I got this email. So thanks for that.
Can I say this appears crazy. KDE appears to be trying to make itself
as complex as wind
On 29/03/14 22:19, Chris wrote:
Hi Allen
With the font issues I found that the font was not specified in the ui
file so defaults where applied. Those defaults caused problems. So it
may be the defaults on your machine are more suited to your desktop
environment than the default on other desktops
Hi Allen
With the font issues I found that the font was not specified in the ui file
so defaults where applied. Those defaults caused problems. So it may be the
defaults on your machine are more suited to your desktop environment than
the default on other desktops. On windows, QT uses an inter
On 29/03/14 01:21, Chris wrote:
Hi Guys
I am trying to debug the csv import plugin layout problem. It appears
the default font may be a large part of the problem but not all of it.
Hi Cristian
Coming in here from a different angle. Here, I've sorted out the layout
problem with Ubuntu-type
Hi Chris,
@Cristian: please read very last sentence of this mail. TIA.
On Saturday 29 March 2014 11:51:31 Chris wrote:
> Hi Guys
>
> I am trying to debug the csv import plugin layout problem. It appears the
> default font may be a large part of the problem but not all of it.
>
> What I can't
Am Samstag, 29. März 2014, 11:51:31 schrieb Chris:
> I have added the path to the bin folder to QT_PLUGIN_PATH I have also tried
> adding the application path by calling
> QCoreApplication::addLibraryPath(QCoreApplication::applicationDirPath());
> inside the KApplication Constructor
[…]
> Without c
Hi Guys
I am trying to debug the csv import plugin layout problem. It appears the
default font may be a large part of the problem but not all of it.
What I can't work out is to how to actually debug the plugin inside of
msvc2010. KMyMoney does not load the plugin at all when run from the buil
28 matches
Mail list logo
