10-09-2012
If you build from source, you can hang libraries anywhere you want. I suggest $HOME/myroot/. Developers are allowed to compile open source, right?
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Howdie everyone...
I have a shell script RemoveFiles.sh
Inside this file, it only has two commands as below:
rm -f ../../reportToday/temp/*
rm -f ../../report/*
My problem is that when i execute this script, nothing happened. Files remained unremoved. I don't see any error message as it... (2 Replies)
Discussion started by: cheongww
2 Replies
2. Shell Programming and Scripting
Hi,
I have a challenging task,in which i have to find the duplicate files by its name and size,then i need to take anyone of the file.Then i need to open the file and find for more than one pattern and count of that pattern.
Note:These are the samples of two files,but i can have more... (2 Replies)
Discussion started by: jerome Sukumar
2 Replies
3. UNIX and Linux Applications
Hello all,
I need help for build server call as Password management / centralized password management server.
My situation and example:
I have 600 server in my server room running on Linux then I need 1 server only can create login/password and then user can login to all 600 server no... (2 Replies)
Discussion started by: sheikh76
2 Replies
4. IP Networking
I have a client machine that was built and loaded with SCO UNIX 2.1.3, (yes it is old). The machine worked fine on the closed network that I tested on in my shop. I then had to change it to the network that it would be connected to. Below is the host file, router and subnet mask file that I usually... (0 Replies)
Discussion started by: NC user
0 Replies
5. IP Networking
Hello all,
I was wondering which way do you use to manage you IPs?
For example in our case we have excel sheets and we export them in html first and import it to a server running apache, so to be visible from all.
But i was wondering if there are any way (prefer a way running in web server)... (2 Replies)
Discussion started by: @dagio
2 Replies
6. Shell Programming and Scripting
My script work on Linux but not work in sun os.
my script.
logFiles="sentLog1.log sentLog2.log"
intial_time="0 0"
logLocation="/usr/local/tomcat/logs/"
sleepTime=600
failMessage=":: $(tput bold)Log not update$(tput rmso) = "
successMessage="OK"
arr=($logFiles)... (7 Replies)
Discussion started by: ooilinlove
7 Replies
7. IP Networking
hi all. and sorry for the random question, but this sparkled a raging flame-war at work and i want more points of view
situation
a router, with linux of some sort,
dhcp client requesting for ip in wan1 (as usual with wan ports)
dhcp server listening in lan1, and assigning ip (as usual... (9 Replies)
Discussion started by: broli
9 Replies
8. What is on Your Mind?
Original post from this thread on browser caching.
To add to this, it is an effective security measure to clear absolutely all cached data (cookies, web content, ....) when closing the browser - i.e. in case of a shutdown. It takes a bit of work to re-login to all the sites but websites will not... (7 Replies)
Discussion started by: bakunin
7 Replies
LEARN ABOUT REDHAT
makekdedoc
MAKEKDEDOC(1) KDOC Documentation System MAKEKDEDOC(1)
NAME
makekdedoc -- Generates HTML documentation for KDE libraries using KDOC.
SYNOPSIS
makekdedoc [--rule-file=<rulefile>] [--libdir=<libdir>]
[--outputdir=<outputdir>] [--url=<url>]
[--srcdir=<kdelibs src dir>]
[--kdoc=<path to kdoc>] [<library>...]
makekdedoc --help
DESCRIPTION
This is a perl script that uses KDOC to generate documentation for kdelibs. A "rule" file is used to figure out the libraries to document,
the order in which to document them and the libraries with which each one will be cross-referenced (eg kdeui uses -lkdecore). See "FILES"
for more info.
NOTE: The script assumes that you have already generated a Qt cross-reference using qt2kdoc[1].
OPTIONS
Defaults for each option are in square brackets.
library...
Specify the libraries to document. By default, all libraries defined by the rule file are documented.
--outputdir <path>, -d <path>
The directory where the output will be written. [`cwd`/srcdoc]
--url <url>, -u <url>
The base URL by which the generated docs will be accessed. For example, if your web server is configured to use $HOME/public_html for
your home page, you could set the outputdir to $HOME/public_html/srcdoc and the url to http://myhost/~mylogin/srcdoc. [output dir]
--rule-file <path>, -r <path>
The path to the rule file to use for generating the documentation. [<srcdir>/kdoc.rules]
--libdir <path>, -L <path>
The directory in which the KDOC cross-reference files are stored. [$KDOCLIBS if set, otherwise $HOME/.kdoc]
--kdoc <path>, -k <path>
The path to the kdoc program. [kdoc]
--kdocopt <options>, -p <options>
Extra options to be passed to kdoc.
--srcdir <path>, -b <path>
The path to the kdelibs source, eg "$HOME/baseline/kdelibs". [`cwd`]
--help, -h
Quit with a usage message.
EXAMPLES
makekdedoc --srcdir $HOME/baseline/kdelibs
--outputdir $HOME/public_html/src/kdelibs/
--url "http://www.ph.unimelb.edu.au/~ssk/src/kdelibs"
FILES
Rule file
This file lists the directories in the source directory to document. It also lists the files to document from each directory, and the
libraries with which to cross-reference the generated documentation. Here is a small example that documents two libraries and links the
second to the first.
# makekdedoc rule file
doc_MODULES = eenie meenie
# rules for eenie
eenie_FILES = *.h
eenie_LIBS = -lqt
# rules for meenie
meenie_FILES = a.h b.h
meenie_LIBS = -leenie -lqt
In this example, all files in "eenie/*.h" will be documented then two files from "meenie/" will be documented, in the order declared in
"doc_MODULES".
SEE ALSO
See kdoc[1] and qt2kdoc[1].
VERSION
makekdedoc $Revision: 1.2 $
AUTHOR
The script and this documentation were written by Sirtaj Singh Kang <taj@kde.org> in April 1999.
2.0a54 2000-10-10 MAKEKDEDOC(1)