Overview
setup - Instructions on how to compile and install Vitalnix Preface
There are three ways of getting Vitalnix installed. In the following descriptions, replace %version and %arch appropriately. But before we can get to the install instructions, reading the next paragraph is obligatory. Conflicting files
The Vitalnix package actually does "conflict" with other installed packages, as it provides some tools itself, which may already be installed by other -- possibly base system -- packages. This currently includes shadow[.rpm], and in near future coreutils, and possibly util-linux. The Vitalnix RPM has no "Conflict" or "Obsolete" tag set, as these issues are not resolved yet. Any files installed -- either by RPM or source tree -- are called different; they have been prepended a V, i.e. vgroupadd instead of just groupadd. Prerequisites
Vitalnix depends on some libraries, popt, libHX and libxml2.
Installing
From precompiled RPM
One is to install the precompiled RPM package; I recommend this for anyone just wishing to "get it run", however I reserve this for when Vitalnix is stable :-).
This single command installs the RPM. Unless rpm returns some error, this is all there is to do. Precompiled RPM packages for i586 and i686 can be found on the Vitalnix Homepage. From source
The second way is to compile from source. It is for those purists and, of course, developers. If you intend to install from self-compiled source, I still point to RPM specfile. If you want to play around with it and keep it in your own directory, this one is ideal.
Extract the source tree and run Makefile.generate.
(You may add any GNU make relevant flags, like -j2.) If everything
went well, ACCDB, its back-ends, system programs and C-spark will be compiled,
lying in the current directory (the root of the Vitalnix tree). Note that
"." is added to the library search paths for all of Vitalnix, so if
you happen to run any of the utilities from a directory which has a different
libaccdb.so.0.0, that one will be used instead. To install the compiled binaries to system folders, run Makefile.generate install. The default paths to which the binaries and modules will be installed are the ones listed below. To change this behavior, you can pass some variables to gmake (or edit the Makefile). Specifying PREFIX prepends that path to all directories listed below. Any of the variables BINDIR (default /bin), ETCDIR (/etc), USRINC (/usr/include), USRBIN (/usr/bin), USRSBIN (/usr/sbin) and VARLIB (/var/lib) override PREFIX. From RPM specfile
The third method, is to compile from source using the spec file for RPM (maybe APT?). It is better than method #2, as RPM will keep track of what files were installed. That info would not be recorded otherwise. You will also be interested in this one when there is no precompiled RPM for your architecture and/or target OS.
You can then install the RPM found in $RPMBUILD_PATH/RPMS/%arch/. File locations
Program files will be installed in these paths:
Debugging
You can pass DEBUG=1 to gmake (or edit the Makefile) to enable debugging support for GDB.
|