Diffstat (limited to 'noncore/apps/qashmoney/README') (more/less context) (ignore whitespace changes)
-rwxr-xr-x | noncore/apps/qashmoney/README | 35 |
1 files changed, 6 insertions, 29 deletions
diff --git a/noncore/apps/qashmoney/README b/noncore/apps/qashmoney/README index 1888ce6..ef004f7 100755 --- a/noncore/apps/qashmoney/README +++ b/noncore/apps/qashmoney/README | |||
@@ -1,45 +1,39 @@ | |||
1 | QashMoney - Budget Software for the Sharp Zaurus | 1 | QashMoney - Budget Software for the Sharp Zaurus |
2 | 2 | ||
3 | README | 3 | README |
4 | 4 | ||
5 | Welcome to the latest version of QashMoney! This app is designed to make your | ||
6 | budgeting fast, inuitive and easy. | ||
7 | |||
8 | This file lists all the important files in the qashmoney CVS directory and how | 5 | This file lists all the important files in the qashmoney CVS directory and how |
9 | to make the IPK file that goes on the Zaurus. When you checkout the | 6 | to make the IPK file that goes on the Zaurus. When you checkout the |
10 | qashmoney module from CVS, it will create a directory on your hard drive called | 7 | qashmoney-source module from CVS, it will create a directory on your hard drive called |
11 | qashmoney. These instructions assume you are in the directory. | 8 | qashmoney-source. These instructions assume you are in this directory. |
12 | 9 | ||
13 | The first thing you need to do is have all the necessary cross-compile software | 10 | The first thing you need to do is have all the necessary cross-compile software |
14 | and Qtopia installed on your system. I assume you have already done this since | 11 | and Qtopia installed on your system. I assume you have already done this since |
15 | you are downloading CVS, but if not, go to: | 12 | you are downloading CVS, but if not, go to: |
16 | 13 | ||
17 | http://docs.zaurus.com | 14 | http://docs.zaurus.com |
18 | 15 | ||
19 | and download the RPMS that you need for development. | 16 | and download the RPMS that you need for development. |
20 | 17 | ||
21 | You also must have sqlite installed on your system to successfully compile | 18 | You also must have sqlite installed on your system to successfully compile |
22 | QashMoney. Go to: | 19 | QashMoney. Go to: |
23 | 20 | ||
24 | http://www.sqlite.org | 21 | http://www.sqlite.org |
25 | 22 | ||
26 | to download this progam. The SQLite library has already been compiled for the | 23 | to download this progam. |
27 | IPK and is in the 'install' directory. So there is no need to compile SQLite | ||
28 | for ARM but you can if you want. There are instructions for that on the | ||
29 | website. | ||
30 | 24 | ||
31 | After that, set the correct environment variables for the package you | 25 | After that, set the correct environment variables for the package you |
32 | are developing.Two scripts in the qashmoney are used for that purpose: x86.sh | 26 | are developing. Two scripts in the qashmoney-source directory are used for that purpose: x86.sh |
33 | andarm.shIf you are buidling for x86 type: | 27 | and arm.sh. If you are building for x86 type: |
34 | 28 | ||
35 | source x86.sh | 29 | source x86.sh |
36 | 30 | ||
37 | and press enter. To make binaries that run on the Zaurus, type: | 31 | and press enter. To make binaries that run on the Zaurus, type: |
38 | 32 | ||
39 | source arm.sh | 33 | source arm.sh |
40 | 34 | ||
41 | Next, construct the makefile by typing: | 35 | Next, construct the makefile by typing: |
42 | 36 | ||
43 | tmake -o Makefile qashmoney.pro | 37 | tmake -o Makefile qashmoney.pro |
44 | 38 | ||
45 | tmake is Trolltech's program for constructing a typical GNU Makefile from the | 39 | tmake is Trolltech's program for constructing a typical GNU Makefile from the |
@@ -54,41 +48,24 @@ binary in this directory. If you compiled for x86, you can see the application | |||
54 | by using the Qt Virtual Frame Buffer which emulates the Qtopia environment on | 48 | by using the Qt Virtual Frame Buffer which emulates the Qtopia environment on |
55 | your computer. First, copy all the files from the databasefiles directory within the | 49 | your computer. First, copy all the files from the databasefiles directory within the |
56 | qashmoney directory. Otherwise, the program will not function. | 50 | qashmoney directory. Otherwise, the program will not function. |
57 | 51 | ||
58 | To run QashMoney in the Qtopia Virtual Frame Buffer, type: | 52 | To run QashMoney in the Qtopia Virtual Frame Buffer, type: |
59 | 53 | ||
60 | qvfb & | 54 | qvfb & |
61 | ./qashmoney -qws | 55 | ./qashmoney -qws |
62 | 56 | ||
63 | and QashMoney should appear in the frambuffer. You can use and test qashmoney | 57 | and QashMoney should appear in the frambuffer. You can use and test qashmoney |
64 | here as you would on the Zaurus. | 58 | here as you would on the Zaurus. |
65 | 59 | ||
66 | If you compile the binary file for the Zaurus, another script in this directory | 60 | If you want to compile the app and make the IPK file, check out the qashmoney-build module and see the README file in that module. |
67 | will come in handy. To automagically make the IPK file, type: | ||
68 | |||
69 | su | ||
70 | ./make_ipk | ||
71 | |||
72 | You need to be the root user to set the ownership of the binary and other | ||
73 | files correctly. The IPK file will appear in the qashmoney directory. Now put | ||
74 | this file onto the Zaurus and install! | ||
75 | |||
76 | Two other scripts in the directory may be of use. The make_x86 script cleans | ||
77 | the directory and makes the x86 qashmoney binary automatically. The make_arm | ||
78 | scripts makes the ARM binary. So you should really only have to type three | ||
79 | commands the make the IPK file: | ||
80 | |||
81 | ./make_arm | ||
82 | su | ||
83 | ./make_ipk | ||
84 | 61 | ||
85 | I hope the program can be useful. If you have any questions or comments, please | 62 | I hope the program can be useful. If you have any questions or comments, please |
86 | contact me at qashmoneyman@attbi.com | 63 | contact me at qashmoneyman@attbi.com |
87 | 64 | ||
88 | Thanks! | 65 | Thanks! |
89 | 66 | ||
90 | Allen | 67 | Allen |
91 | 68 | ||
92 | Disclaimer: Altough I've tried to make this application tight and well | 69 | Disclaimer: Altough I've tried to make this application tight and well |
93 | functioning, it comes with absolutely no warranty and I will not be liable for | 70 | functioning, it comes with absolutely no warranty and I will not be liable for |
94 | any damage it may cause. | 71 | any damage it may cause. |