Re: Where to find this code

2019-12-28 Thread Brendan Coupe
Jesus,

I created build scripts that I use several times a month to build and
install KMM from the 3 branches (including 4.8). You can also build
from a released source file. Feel free to download them from the link
below, they may help explain the process even if you do not wish to
use them. I always download a fresh source tree rather than patching
an existing tree. I had some issues when I first started compiling
from source more than 10 years ago and decided not to mess updates.
This was back in the cvs days.

I can easily put diff files in the Patches folder that will be applied
to any new builds. I've attached a sample below. This patch shortens
the text in the scheduled transaction tab. I was annoyed by it not
fitting in the tab in tabbed view so I found a way to abbreviate it.
Pretty simple patch.

As far as which branch is stable, good luck with that:-) Every time I
ask for an explanation I get more confused. I normally compile the
Master branch unless I know a change is only in the 5.0 branch. You
can reorder the branches in the ScriptsKMM.conf file to make your
chosen default branch first (GitBranches="MASTER 5.0 4.8").

If you have any feedback or suggestions for my scripts please let me know.


Brendan Coupe
KMyMoney Build Scripts - Easily Build KMyMoney From Source Code
https://drive.google.com/drive/folders/1sfo2HgzaCCSb3d7pjl3To50yoQT5BaXM


Brendan Coupe



Brendan Coupe


On Sat, Dec 28, 2019 at 3:48 PM  wrote:
>
> Thanks Thomas.
>
> I am trying to read between the lines. So if I miss something, please let me 
> know.
>
> Here is what I did:
>
> git clone --single-branch --branch master git://anongit.kde.org/kmymoney.git 
> kmy/master
> git clone --single-branch --branch 5.0 git://anongit.kde.org/kmymoney.git 
> kmy/stable
>
> Is that what you meant by master and stable? Why do you all see 5.0 as 
> stable? Is that the base release that all current security and other patches 
> are going towards for the current release, and Master is the new source for 
> the next release? (so you apply the patches to both)
>
> Regarding Step C... So then, we have to do a(n) (re)installation to make sure 
> all the plugins get pulled correctly.. otherwise, I won't see the changes. 
> This makes sense, although.. I am wondering, are the Reports modules 
> considered a plugin or part of the core of KMyMoney? Also, do you happen to 
> know if Kdevelop runs a re-install behind the scenes when I hit the Debug 
> button?
>
> thanks again. I know you have mentioned some of this in the past and some of 
> it is just now sinking in. I promise once I get going, I will try to help you 
> all instead of just slowing you guys down. I just finally have some down time 
> from my regular work that I can focus on this.
>
> JV
>
>
> On Fri, 2019-12-27 at 10:53 +0100, Thomas Baumgart wrote:
>
> Jesus,
>
> the whole process of generation of the KMyMoney artifacts is divided into 
> these parts:
>
> a) configuration
> b) compilation / linkage
> c) installation
>
> Step a) is where cmake comes into play. Its job is to convert the meta 
> information provided in CMakeLists.txt files into lower level Makefiles 
> (depending on the build tool/generator used). This step caches some 
> information which will not be re-evaluated if you re-run cmake. To get a full 
> scan remove build/CMakeCache.txt and re-run cmake. Removing CMakeCache.txt 
> also wipes all the settings you have made using ccmake.
>
> Step b) is invoked by calling 'make' and compiles and links the artifacts 
> comprising the application, that is the executables (yes, the testcases as 
> well), shared libs and plugins. At the end they are all located in build/bin.
>
> Step c) moves all the necessary files (executable, shared libs, plugins, 
> icons, templates, etc.) into the location of your KDE install. This is 
> performed by running 'sudo make install/fast'.
>
> To remove an installed version, I simply use this the following sequence in 
> the build sub-directory:
>
>   sudo -s
>   xargs rm < install_manifest.txt
>   exit
>
> Having two sandboxes (one with master and one with 5.0) and can easily switch 
> between the two of them. E.g. from stable to master:
>
>   cd stable/build
>   sudo -s
>   xargs rm < install_manifest.txt
>   exit
>   cd ../../master/build
>   sudo make install/fast
>
> This will make sure that all the files are recent. Especially for plugins, 
> step c) is very important. If you omit it, the debugger will use the newly 
> compiled executable and shared objects from the build/bin directory, but not 
> the plugins. It will use the old ones found installed. As Jack pointed out, 
> not having the most recent plugin installed may be the cause to the problem 
> you encounter.
>
> BTW: KMyMoney tells you on the command line where it picks up the plugins 
> during startup, e.g.
>
> Located plugin "/usr/lib64/qt5/plugins/kmymoney/konlinetasks_sepa.so" 
> Validity true
> Located plugin "/usr/lib64/qt5/plugins/kmymoney/csvimporter.so" Validi

Re: Where to find this code

2019-12-28 Thread jvapr27
Thanks Thomas. 
I am trying to read between the lines. So if I miss something, please
let me know. 
Here is what I did: 
git clone --single-branch --branch master
git://anongit.kde.org/kmymoney.git kmy/master   git clone --single-
branch --branch 5.0 git://anongit.kde.org/kmymoney.git kmy/stable
Is that what you meant by master and stable? Why do you all see 5.0 as
stable? Is that the base release that all current security and other
patches are going towards for the current release, and Master is the
new source for the next release? (so you apply the patches to both)
Regarding Step C... So then, we have to do a(n) (re)installation to
make sure all the plugins get pulled correctly.. otherwise, I won't see
the changes. This makes sense, although.. I am wondering, are the
Reports modules considered a plugin or part of the core of KMyMoney?
Also, do you happen to know if Kdevelop runs a re-install behind the
scenes when I hit the Debug button? 
thanks again. I know you have mentioned some of this in the past and
some of it is just now sinking in. I promise once I get going, I will
try to help you all instead of just slowing you guys down. I just
finally have some down time from my regular work that I can focus on
this.  
JV

On Fri, 2019-12-27 at 10:53 +0100, Thomas Baumgart wrote:
> Jesus,
> the whole process of generation of the KMyMoney artifacts is divided
> into these parts:
> a) configurationb) compilation / linkagec) installation
> Step a) is where cmake comes into play. Its job is to convert the
> meta information provided in CMakeLists.txt files into lower level
> Makefiles (depending on the build tool/generator used). This step
> caches some information which will not be re-evaluated if you re-run
> cmake. To get a full scan remove build/CMakeCache.txt and re-run
> cmake. Removing CMakeCache.txt also wipes all the settings you have
> made using ccmake.
> Step b) is invoked by calling 'make' and compiles and links the
> artifacts comprising the application, that is the executables (yes,
> the testcases as well), shared libs and plugins. At the end they are
> all located in build/bin.
> Step c) moves all the necessary files (executable, shared libs,
> plugins, icons, templates, etc.) into the location of your KDE
> install. This is performed by running 'sudo make install/fast'.
> To remove an installed version, I simply use this the following
> sequence in the build sub-directory:
>   sudo -s  xargs rm < install_manifest.txt  exit
> Having two sandboxes (one with master and one with 5.0) and can
> easily switch between the two of them. E.g. from stable to master:
>   cd stable/build  sudo -s  xargs rm < install_manifest.txt  exit  cd
> ../../master/build  sudo make install/fast
> This will make sure that all the files are recent. Especially for
> plugins, step c) is very important. If you omit it, the debugger will
> use the newly compiled executable and shared objects from the
> build/bin directory, but not the plugins. It will use the old ones
> found installed. As Jack pointed out, not having the most recent
> plugin installed may be the cause to the problem you encounter.
> BTW: KMyMoney tells you on the command line where it picks up the
> plugins during startup, e.g.
> Located plugin "/usr/lib64/qt5/plugins/kmymoney/konlinetasks_sepa.so"
> Validity trueLocated plugin
> "/usr/lib64/qt5/plugins/kmymoney/csvimporter.so" Validity
> true..Loading "/usr/lib64/qt5/plugins/kmymoney/budgetview.so"Plugins:
> budgetview loadedLoading
> "/usr/lib64/qt5/plugins/kmymoney/checkprinting.so"Plugins:
> checkprinting loaded..
> Hope that helps.
> Thomas
> 
>  On Freitag, 27. Dezember 2019 01:42:38 CET Jack wrote:
> > Hi JV,
> > I begin to wonder if the problem is that you are trying to debug a
> > KMM plugin.  It is easy enough to debug a newly compiled kmymoney
> > file, but KDE/QT has its own way of finding plugins.  As an
> > experiment, after you have run "make" find where the newly compiled
> > plugins are.  For this example assume you ran make in .../kmm/build
> > and the compiled plugins are in the lib dir below that.  Try
> > running 'QT_PLUGIN_PATH=.../kmm/build/lib" kdevelop'.
> > Note I'm doing this mostly from memory, so if it doesn't work,
> > someone will have to confirm whether some of my details are
> > wrong.  I just don't know if kdevelop accounts for that
> > On 12/26/19 11:46 AM, jvap...@gmail.com wrote:
> > > Thanks Jack!
> > > This is what I see in the ccmake:
> > >   CMAKE_BUILD_TYPE Debugfull 
> > > CMAKE_COLOR_MAKEFILE ON 
> > > CMAKE_CXX_COMPILER   /usr/bin/c++ 
> > > CMAKE_CXX_COMPILER_AR/usr/bin/gcc-ar 
> > > CMAKE_CXX_COMPILER_RANLIB/usr/bin/gcc-ranlib 
> > > CMAKE_CXX_FLAGS  CMAKE_CXX_FLAGS_DEBUG-g 
> > > CMAKE_CXX_FLAGS_DEBUGFULL  CMAKE_CXX_FLAGS_MINSIZEREL   -Os
> > > -DNDEBUG  CMAKE_CXX_FLAGS_RELEASE  -O2 -DNDEBUG 
> > > CMAKE_CXX_FLAGS_RELWITHDEBINFO   -O2 -g -DNDEBUG 
> > > CMAKE_DLLTOOL   

[kmymoney] [Bug 415614] .kmy file contains invalid characters

2019-12-28 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=415614

Ralf Habacker  changed:

   What|Removed |Added

  Flags||Backport-
 CC||ralf.habac...@freenet.de

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmymoney] [Bug 415637] New: Backup is not working when trying to backup to network share folder

2019-12-28 Thread Tremi
https://bugs.kde.org/show_bug.cgi?id=415637

Bug ID: 415637
   Summary: Backup is not working when trying to backup to network
share folder
   Product: kmymoney
   Version: 5.0.5
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kmymoney-devel@kde.org
  Reporter: tremidk...@gmail.com
  Target Milestone: ---

SUMMARY
The backup is not succeeded when trying to back up to the network share. The
backup went well if the network share is mounted as a drive in the system.

SOFTWARE/OS VERSIONS
Windows: Windows 10

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmymoney] [Bug 412429] No display of transactions in the tags view when tags are specified in a split

2019-12-28 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=412429

--- Comment #17 from Ralf Habacker  ---
(In reply to Ralf Habacker from comment #15)
> *** Bug 412870 has been marked as a duplicate of this bug. ***
This has been reverted because tag view display has been fixed with bug 412429;
this bug is for the remaining ledger view.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmymoney] [Bug 415633] tagged splits not recognised in list of tagged transactions

2019-12-28 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=415633

Thomas Baumgart  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Thomas Baumgart  ---


*** This bug has been marked as a duplicate of bug 412429 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmymoney] [Bug 412429] No display of transactions in the tags view when tags are specified in a split

2019-12-28 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=412429

Thomas Baumgart  changed:

   What|Removed |Added

 CC||graham.ocon...@gmail.com

--- Comment #16 from Thomas Baumgart  ---
*** Bug 415633 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.