Difference between revisions of "Cutecash"
m (→Windows / MSVC) |
|||
| Line 7: | Line 7: | ||
all of the other achievments in the "engine" and xml-backend and eventually | all of the other achievments in the "engine" and xml-backend and eventually | ||
other backends can be re-used. But the GUI is rewritten completely new, from | other backends can be re-used. But the GUI is rewritten completely new, from | ||
| − | scratch, in C++ and using the Qt toolkit. Fun again. The build system is CMake | + | scratch, in C++ and using the Qt toolkit. Fun again. The build system is [[CMake]] |
because its configuration runs magnitudes faster. Fun again. And as a final | because its configuration runs magnitudes faster. Fun again. And as a final | ||
bonus, for MS windows more compiler than before are supported, namely this | bonus, for MS windows more compiler than before are supported, namely this | ||
| Line 14: | Line 14: | ||
==Build Instructions== | ==Build Instructions== | ||
===Linux=== | ===Linux=== | ||
| − | On Linux, install qt4 (>= 4.5.0) and | + | On Linux, install qt4 (>= 4.5.0) and [[CMake]] (>= 2.6.0), grab the gnucash sources from [[SVN]], change into its top-level directory and run |
mkdir build-cutecash | mkdir build-cutecash | ||
| Line 21: | Line 21: | ||
make | make | ||
./src/gnc/cutecash | ./src/gnc/cutecash | ||
| + | |||
| + | The qt4 development package is called libqt4-dev on Debian-related distributions. | ||
===Windows / MSVC=== | ===Windows / MSVC=== | ||
| Line 27: | Line 29: | ||
The recommended process goes as follows: | The recommended process goes as follows: | ||
* Let the dependencies be build by the mingw installation process which is being used for the "normal" gnucash, explained here: [[Windows]], in particular [[Windows#Instructions_for_an_.28almost.29_automated_build]] | * Let the dependencies be build by the mingw installation process which is being used for the "normal" gnucash, explained here: [[Windows]], in particular [[Windows#Instructions_for_an_.28almost.29_automated_build]] | ||
| − | * Once all of this is built, you | + | * Once all of this is built, you start [[CMake]] from http://www.cmake.org. Select the top-level folder of the gnucash source code as source folder; select some new empty folder as build folder. Then click "Generate" and choose a "Visual Studio 2008 project". Subsequently, you will have to select some header file locations and library locations until CMake does not complain about anything anymore, but those have all been installed by the automatic build from [[Windows#Instructions_for_an_.28almost.29_automated_build]] |
* Next, you open the MSVC2008 project file that was created by CMake, then build this project. The resulting executable can be run and built again and debugged and developed in the normal Visual Studio way. | * Next, you open the MSVC2008 project file that was created by CMake, then build this project. The resulting executable can be run and built again and debugged and developed in the normal Visual Studio way. | ||
Revision as of 21:22, 4 March 2010
Announcing a new sub-project in gnucash: GUI in C++, Qt, CMake.
Cutecash. Easy to develop, easy to use
Announcing a new sub-project in gnucash: The non-GUI parts are re-used in the state they are, in the C language. This means the double-entry principles and all of the other achievments in the "engine" and xml-backend and eventually other backends can be re-used. But the GUI is rewritten completely new, from scratch, in C++ and using the Qt toolkit. Fun again. The build system is CMake because its configuration runs magnitudes faster. Fun again. And as a final bonus, for MS windows more compiler than before are supported, namely this whole new project can be compiled by MS Visual Studio as well.
Build Instructions
Linux
On Linux, install qt4 (>= 4.5.0) and CMake (>= 2.6.0), grab the gnucash sources from SVN, change into its top-level directory and run
mkdir build-cutecash cd build-cutecash cmake .. make ./src/gnc/cutecash
The qt4 development package is called libqt4-dev on Debian-related distributions.
Windows / MSVC
The sub-project Cutecash can be developed with the Microsoft Visual Studio compiler (MSVC) as well. Visual Studio 2008 Express was tested, but others might work as well. However, the Cutecash project needs a large number of dependency libraries which are not built by MSVC, but by the Windows-Mingw compiler (gcc).
The recommended process goes as follows:
- Let the dependencies be build by the mingw installation process which is being used for the "normal" gnucash, explained here: Windows, in particular Windows#Instructions_for_an_.28almost.29_automated_build
- Once all of this is built, you start CMake from http://www.cmake.org. Select the top-level folder of the gnucash source code as source folder; select some new empty folder as build folder. Then click "Generate" and choose a "Visual Studio 2008 project". Subsequently, you will have to select some header file locations and library locations until CMake does not complain about anything anymore, but those have all been installed by the automatic build from Windows#Instructions_for_an_.28almost.29_automated_build
- Next, you open the MSVC2008 project file that was created by CMake, then build this project. The resulting executable can be run and built again and debugged and developed in the normal Visual Studio way.
