=========================================
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-1.2.0.tar.gz
	untar it:

$ tar xvzf vdkbuilder-1.2.0.tar.gz

	To compile builder you need to have installed:
	- glib/gtk+ libraries version 1.2.0 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://www.programmers.net/artic/Motta/vdk/index.htm
	or
	http://www.guest.net/homepages/mmotta/vdkhome/index.htm

#=========================================
# 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 1.5 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
	
	** IMPORTANT INSTALLATION NOTES **
	=================================

-	On the first run VDKBuilder will prepare a
	~/.vdkb directory where some resource files will be copied.
	Those are local copies at user hand. For instance editing
	~/.vdkb/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/localand run (as root)
	# /sbin/ldconfig
	in order to update loader for plugins libraries.
	
	For those that upgrade from previous versions:
	On the first run a warning message will appear:
	"local file <your home>/.vdkb/res/plugins.db not found,
	using default"
	Use "Components" menu and "save" to copy such file into
	your local .vdkb directory.

	If you install vdkbuilder into a dir other than /usr/local
	vdkbuilder will complain about missing plugins lib files.
	In such case edit <your home>/.vdkb/res/plugins.db
	and <prefix>/share/vdkb/res/plugins.db to change lib path.
	Run again builder to see if it see the correct path.

	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
	During configuration vdkbuilder will automatically detect
	the presence of vdkxdb version 0.2.0 and will build vdkxdb
	support. Thus vdkxdb must be compiled and installed before
	vdkbuilder. 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-1.2.0/example there are
example projects that can be runned.

#==============
FOR CVS HACKERS
#==============
You can stay on bleeding edge using cvs snapshots.
To access cvs operate like this:

$ export
CVSROOT=":pserver:anonymous@borco-ei.eng.hokudai.ac.jp:/usr/local/cvsroot"
$ cvs login
(passwd anonymous)
And then, the first time do
$ cvs -z3 checkout vdkbuilder
Next times, do
$ cvs -z3 update vdk vdkbuilder

Once downloaded vdkbuilder tree you have to build autoconf/automake
environment (requires autoconf/automake):

$ ./autogen.sh
or you may want
$ ./autogen.sh --help
$ make
# make install






