1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
=========================================
VDKBUILDER INSTALLING INSTRUCTIONS
=========================================
please report any comment or bug to:
mmotta@guest.net
=====================
TO MAKE AND INSTALL
=====================
copy to your home directory the gzipped file: vdkbuilder-2.0.x.tar.gz
and unpack it:
$ tar xvzf vdkbuilder-2.0.x.tar.gz
To compile builder you need to have installed:
- glib/gtk+ libraries version 2.0.x or greater
you can find it at: http://www.gtk.org
- latest vdk library version, generally same
vdkbuilder version.
you can find it at: http://vdkbuilder.sourceforge.net
#=========================================
# some step are necessary:
#=========================================
# (1) Configuring
Go to vdkbuilder main dir and type
$ ./configure
(you may want type ./configure --help to see available options).
# (2) Making VDKBuilder
Go to vdkbuilder main dir and type:
$ make
by default builder will be compiled without -g option, this produces a 2 Mb executable file
If you want debug info's into executable reconfigure with --enable-devel=yes option
With debugging executable will be more than 10 Mb
# (3) Installing
Go to vdkbuilder main dir and type:
# make install (you may need su privilege)
** IMPORTANT INSTALLATION NOTES **
=================================
- On the first run VDKBuilder will prepare a
~/.vdkb2 directory where some resource files will be copied. Those are local copies at user hand.
For instance editing ~/.vdkb2/res/vdkbrc you can customize colors and fonts.
(this apply only for new users, upgrading users should already have them)
- PLUGINS LIBRARIES
By default VDKBuilder and plugins libraries will be installed into /usr/local/bin and /usr/local/lib,
resource files into /usr/local/share/vdkb
You may edit /etc/ld.so.conf to see if it has a line pointing to /usr/local and run (as root)
# /sbin/ldconfig
in order to update loader for plugins libraries.
For those that wants implement their own plugins for builder
recall that they need vdkbuilder .h files in order to compile
plugins. (See /plugins/plugins.txt file)
- Supporting languages
vdkbuilder supports NLS system
Actually languages supported are:
English (default)
Italian
German
Danish
- Supporting VDKXDB library
Add to ./configure --enable-vdkxdb=yes option
VDKXDB support let's the user to manage data-aware widgets provided by
vdxdb and see them working even at design-time.
VDKBuilder will generate the code to open xdb data files
and index as well. A "Project->xdbsupport" menu item lets the user
set which datafiles and indexes are to be used by the project itself.
A tool palette with data-aware widgets will be available on builder
main form as well.
* (4) Now you are ready to use vdkbuilder.
Run it with vdkb&
#==================
# running examples
#==================
into dir ./vdkbuilder-2.0.x/example there are
example projects that can be runned.
#==============
FOR CVS HACKERS
#==============
You can stay on bleeding edge using cvs snapshots available at vdkbuilder site
Once checked out vdkbuilder tree you have to build autoconf/automake
environment (requires autoconf/automake):
$ ./autogen.sh
or you may want
$ ./autogen.sh --help
$ make
# make install
|
