Browse Source

Drop automake build support.

Add basic cmake build instructions.
Remove empty files: NEWS and TODO.
Rework of the README, INSTALL and help page.

Signed-off-by: gregory guy <>
Gregory Guy 2 months ago
Signed by: cethyel <> GPG Key ID: 3BCCA0F7AB4536F4
19 changed files with 49 additions and 11771 deletions
  1. +0
  2. +11
  3. +0
  4. +0
  5. +0
  6. +26
  7. +0
  8. +0
  9. +0
  10. +0
  11. +0
  12. +0
  13. +0
  14. +0
  15. +0
  16. +12
  17. +0
  18. +0
  19. +0

+ 0
- 3
.gitmodules View File

@@ -1,6 +1,3 @@
[submodule "admin"]
path = admin
url =
[submodule "cmake"]
path = cmake
url =

+ 11
- 173

@@ -1,178 +1,16 @@
For the impatient

make install

Dont blame me if your impatience f**ks up your machine. But
please email me with your tale of woe. I always enjoy a good belly
laugh! ;)

Basic Installation

These are generic installation instructions.

The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

The file `' is used to create `configure' by a program
called `autoconf'. You only need `' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.

The simplest way to compile this package is:

1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.

Running `configure' takes a while. While running, it prints some
messages telling which features it is checking for.

2. Type `make' to compile the package.

3. Type `make install' to install the programs and any data files and

4. You can remove the program binaries and object files from the
source code directory by typing `make clean'.

Compilers and Options

Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

Compiling For Multiple Architectures

You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another

Installation Names

By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features

Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type

There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:

See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.

If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

Sharing Defaults

If you want to set default values for `configure' scripts to share,
you can create a site shell script called `' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/' if it exists, then
`PREFIX/etc/' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Operation Controls

`configure' recognizes the following options to control how it

Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.

Print a summary of the options to `configure', and exit.

Do not print messages saying which checks are being made.

Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.

Print the version of Autoconf used to generate the `configure'
script, and exit.
Knmap relies on cmake to build.

`configure' also accepts some other, not widely useful, options.
Here are suggested default options:

-DCMAKE_INSTALL_PREFIX="/opt/trinity" \
-DCONFIG_INSTALL_DIR="/etc/trinity" \
-DSYSCONF_INSTALL_DIR="/etc/trinity" \
-DXDG_MENU_INSTALL_DIR="/etc/xdg/menus" \

+ 0
- 22 View File

@@ -1,22 +0,0 @@

$(top_srcdir)/ $(top_srcdir)/subdirs
cd $(top_srcdir) && $(MAKE) -f admin/Makefile.common ;

cd $(top_srcdir) && $(MAKE) -f admin/Makefile.common subdirs

$(top_srcdir)/acinclude.m4: $(top_srcdir)/admin/ $(top_srcdir)/admin/
@cd $(top_srcdir) && cat admin/ admin/ > acinclude.m4

MAINTAINERCLEANFILES = subdirs acinclude.m4 configure.files

cd $(top_srcdir) && $(MAKE) -f admin/Makefile.common package-messages
$(MAKE) -C po merge


cd $(top_distdir) && perl admin/am_edit -padmin
cd $(top_distdir) && $(MAKE) -f admin/Makefile.common subdirs

+ 0
- 10
Makefile.cvs View File

@@ -1,10 +0,0 @@
@echo "This Makefile is only for the CVS repository"
@echo "This will be deleted before making the distribution"
@echo ""
$(MAKE) -f admin/Makefile.common cvs

$(MAKE) -f admin/Makefile.common dist


+ 0
- 0
NEWS View File

+ 26
- 3
README View File

@@ -1,4 +1,27 @@
If you've got time to read this file you've got
too much time on your hands.

Go get a life!
Knmap – a nmap graphical interface for TDE.
Knmap is a graphical front end to "nmap" (Network exploration tool
and security scanner).

The main Knmap window provides for the entry of nmap options and the
display of nmap-generated output.
Nmap is an open source tool for network exploration and security


If you wish to contribute to knmap (TDE), you might do so:

- TDE Gitea Workspace (TGW) collaboration tool.

- TDE Weblate Translation Workspace (TWTW) collaboration tool.

+ 0
- 0
TODO View File

+ 0
- 11179
File diff suppressed because it is too large
View File

+ 0
- 1

@@ -1 +0,0 @@
Subproject commit 68f23556e638353e46b444d3a4863a64936bd36a

+ 0
- 219 View File

@@ -1,219 +0,0 @@
/* Generated from by autoheader. */

/* Define if you have the CoreAudio API */

/* Define to 1 if you have the <crt_externs.h> header file. */

/* Defines if your system has the crypt function */

/* Define to 1 if you have the <dlfcn.h> header file. */

/* Define to 1 if you have the <inttypes.h> header file. */

/* Define if you have libjpeg */

/* Define if you have libpng */

/* Define if you have a working libpthread (will enable threaded code) */

/* Define if you have libz */
#undef HAVE_LIBZ

/* Define to 1 if you have the <memory.h> header file. */

/* Define if your system needs _NSGetEnviron to set up the environment */

/* Define if you have the res_init function */

/* Define if you have a STL implementation by SGI */

/* Define to 1 if you have the `snprintf' function. */

/* Define to 1 if you have the <stdint.h> header file. */

/* Define to 1 if you have the <stdlib.h> header file. */

/* Define to 1 if you have the <strings.h> header file. */

/* Define to 1 if you have the <string.h> header file. */

/* Define if you have strlcat */

/* Define if you have the strlcat prototype */

/* Define if you have strlcpy */

/* Define if you have the strlcpy prototype */

/* Define to 1 if you have the <sys/stat.h> header file. */

/* Define to 1 if you have the <sys/types.h> header file. */

/* Define to 1 if you have the <unistd.h> header file. */

/* Define to 1 if you have the `vsnprintf' function. */

/* Suffix for lib directories */

/* Define a safe value for MAXPATHLEN */

/* Name of package */
#undef PACKAGE

/* Define to the address where bug reports for this package should be sent. */

/* Define to the full name of this package. */

/* Define to the full name and version of this package. */

/* Define to the one symbol short name of this package. */

/* Define to the version of this package. */

/* The size of a `char *', as computed by sizeof. */

/* The size of a `int', as computed by sizeof. */

/* The size of a `long', as computed by sizeof. */

/* The size of a `short', as computed by sizeof. */

/* The size of a `size_t', as computed by sizeof. */

/* The size of a `unsigned long', as computed by sizeof. */

/* Define to 1 if you have the ANSI C header files. */

/* Version number of package */
#undef VERSION

/* Define to 1 if your processor stores words with the most significant byte
first (like Motorola and SPARC, unlike Intel and VAX). */

* jpeg.h needs HAVE_BOOLEAN, when the system uses boolean in system
* headers and I'm too lazy to write a configure test as long as only
* unixware is related
#ifdef _UNIXWARE

* AIX defines FD_SET in terms of bzero, but fails to include <strings.h>
* that defines bzero.

#if defined(_AIX)
#include <strings.h>

# include <sys/time.h>
# include <crt_externs.h>
# define environ (*_NSGetEnviron())

#if !defined(HAVE_STRLCAT_PROTO)
#ifdef __cplusplus
extern "C" {
unsigned long strlcat(char*, const char*, unsigned long);
#ifdef __cplusplus

#if !defined(HAVE_STRLCPY_PROTO)
#ifdef __cplusplus
extern "C" {
unsigned long strlcpy(char*, const char*, unsigned long);
#ifdef __cplusplus

* On HP-UX, the declaration of vsnprintf() is needed every time !

#if !defined(HAVE_VSNPRINTF) || defined(hpux)
#if __STDC__
#include <stdarg.h>
#include <stdlib.h>
#include <varargs.h>
#ifdef __cplusplus
extern "C"
int vsnprintf(char *str, size_t n, char const *fmt, va_list ap);
#ifdef __cplusplus
extern "C"
int snprintf(char *str, size_t n, char const *fmt, ...);

#if defined(__SVR4) && !defined(__svr4__)
#define __svr4__ 1

/* Compatibility define */
#undef ksize_t

/* Define the real type of socklen_t */
#undef socklen_t

+ 0
- 2
configure.files View File

@@ -1,2 +0,0 @@

+ 0
- 82 View File

@@ -1,82 +0,0 @@
dnl This file is part of the KDE libraries/packages
dnl Copyright (C) 2001 Stephan Kulow (
dnl This file is free software; you can redistribute it and/or
dnl modify it under the terms of the GNU Library General Public
dnl License as published by the Free Software Foundation; either
dnl version 2 of the License, or (at your option) any later version.
dnl This library is distributed in the hope that it will be useful,
dnl but WITHOUT ANY WARRANTY; without even the implied warranty of
dnl Library General Public License for more details.
dnl You should have received a copy of the GNU Library General Public License
dnl along with this library; see the file COPYING.LIB. If not, write to
dnl the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
dnl Boston, MA 02111-1307, USA.

# Original Author was
# I lifted it in some mater. (Stephan Kulow)
# I used much code from Janos Farkas

dnl Process this file with autoconf to produce a configure script.

AC_INIT(acinclude.m4) dnl a source file from your sub dir

dnl This is so we can use kde-common

dnl This ksh/zsh feature conflicts with `cd blah ; pwd`
unset CDPATH

dnl Checking host/target/build systems, for make, install etc.
dnl Perform program name transformation

dnl Automake doc recommends to do this only here. (Janos)
AM_INIT_AUTOMAKE(knmap, 0.1) dnl searches for some needed programs


dnl generate the config header
AM_CONFIG_HEADER(config.h) dnl at the distribution this done

dnl Checks for programs.

dnl for NLS support. Call them in this order!
dnl WITH_NLS is for the po files


dnl PACKAGE set before

AC_CONFIG_FILES([ Makefile ])
AC_CONFIG_FILES([ doc/Makefile ])
AC_CONFIG_FILES([ doc/en/Makefile ])
AC_CONFIG_FILES([ po/Makefile ])
AC_CONFIG_FILES([ src/Makefile ])
if test "$all_tests" = "bad"; then
if test ! "$cache_file" = "/dev/null"; then
echo ""
echo "Please remove the file $cache_file after changing your setup"
echo "so that configure will find the changes next time."
echo ""
echo ""
echo "Good - your configure finished. Start make now"
echo ""

+ 0
- 6 View File

@@ -1,6 +0,0 @@

AM_INIT_AUTOMAKE(knmap, 0.1)

+ 0
- 6
doc/ View File

@@ -1,6 +0,0 @@
# the SUBDIRS is filled automatically by am_edit. If files are
# in this directory they are installed into the english dir

KDE_DOCS = knmap

+ 0
- 3
doc/en/ View File

@@ -1,3 +0,0 @@
KDE_DOCS = knmap
kde_docs_KDEDOCS = new_scan.png

+ 12
- 15
doc/en/index.docbook View File

@@ -57,7 +57,7 @@

The icons used in this application are from the Open Clip Art Library. I am indebted to those damn fine folk as my artistic ability is zero - which is marginally above my programming ability. :-(
The icons used in this application are from the Open Clip Art Library. I am indebted to those fine folk as my artistic ability is zero - which is marginally above my programming ability.

@@ -163,7 +163,7 @@

The <computeroutput>Start nmap</computeroutput> and <computeroutput>Stop nmap</computeroutput> buttons should require no explanation. (No - I wont now launch into a multi-thousand word explanation of the bloody obvious.)
The <computeroutput>Start nmap</computeroutput> and <computeroutput>Stop nmap</computeroutput> buttons should require no explanation.

@@ -721,7 +721,10 @@
<chapter id="developers">
<title>Developer's Guide to &knmap;</title>
The only item worthy of mention here is the file <computeroutput>nmap_manpage.html.diff</computeroutput>. This file contains a <computeroutput>diff</computeroutput> of the <computeroutput>nmap</computeroutput> version 3.93 HTML formatted <computeroutput>man</computeroutput> page and that distributed with &knmap;. You can use this to update your version of that <computeroutput>man</computeroutput> page.
One file is worth mentioning<computeroutput>nmap_manpage.html.diff</computeroutput>. This file contains a <computeroutput>diff</computeroutput> of the <computeroutput>nmap</computeroutput> version 3.93 HTML formatted <computeroutput>man</computeroutput> page and that distributed with &knmap;. You can use this to update your version of that <computeroutput>man</computeroutput> page.
You may find the source code as well as the current development at <ulink url=""></ulink> .

@@ -750,32 +753,26 @@
<title>How to obtain &knmap;</title>

Now let me see... You're reading this documentation - which come packaged with &knmap;, which means that you have &knmap; installed, which means that you have somehow obtained &knmap;, and now you want to know how to obtain &knmap;?

You have _way_ too much time on your hands! ;-)

Okay, Okay. Go to <ulink url=""></ulink> and follow the download links.
Knmap is part of the Trinity Desktop Project. For further information, please go to <ulink url=""></ulink> .

<sect1 id="requirements">
&knmap; was developed and tested under Qt 3.3.4 / KDE 3.4 &amp; 3.5. YMMV vary if your configuration differs from this.
&knmap; will need the tqt3 and the tdelibs libraries.

And, of course, you will need <computeroutput>nmap</computeroutput>. Go to <ulink url=""></ulink> for details on how to download <computeroutput>nmap</computeroutput>.
You will need <computeroutput>nmap</computeroutput>. Go to <ulink url=""></ulink> for details on how to download <computeroutput>nmap</computeroutput>.

<sect1 id="compilation">
<title>Compilation and Installation</title>
&knmap; relies on cmake to build, please read the INSTALL file for basic instructions.

+ 0
- 1
po/ View File

@@ -1 +0,0 @@

+ 0
- 46
src/ View File

@@ -1,46 +0,0 @@
# set the include path for X, qt and TDE
INCLUDES = $(all_includes)

# these are the headers for your project
noinst_HEADERS = knmap.h global.h mainwidget.h outputwidget.h commonwidget.h \
timingwidget.h compoundwidget.h htmlwidget.h stylesheetdialog.h profiledialog.h \
loggingoptions.h simpleoptions.h pandsoptions.h whatsthis.h tabwidgetptrlist.h \
tabwidgetdata.h scanwidget.h indexwidget.h scannamedialog.h scanstack.h scanmonitor.h \
scanmonitorevent.h nmapoutputbuffer.h

# let automoc handle all of the meta source files (moc)

messages: rc.cpp
$(EXTRACTRC) `find . -name \*.ui -o -name \*.rc` > rc.cpp
$(XGETTEXT) *.cpp -o $(podir)/knmap.pot


# this is the program that gets installed. it's name is used for all
# of the other variables
bin_PROGRAMS = knmap

# the application source, library search path, and link libraries
knmap_SOURCES = main.cpp knmap.cpp mainwidget.cpp outputwidget.cpp \
commonwidget.cpp timingwidget.cpp compoundwidget.cpp htmlwidget.cpp stylesheetdialog.cpp \
profiledialog.cpp loggingoptions.cpp simpleoptions.cpp pandsoptions.cpp whatsthis.cpp \
tabwidgetptrlist.cpp tabwidgetdata.cpp scanwidget.cpp indexwidget.cpp scannamedialog.cpp \
scanstack.cpp scanmonitor.cpp scanmonitorevent.cpp nmapoutputbuffer.cpp
knmap_LDFLAGS = $(TDE_RPATH) $(all_libraries)

# this is where the desktop file will go
shelldesktopdir = $(kde_appsdir)/Internet
shelldesktop_DATA = knmap.desktop

# this is where the shell's XML-GUI resource file goes
shellrcdir = $(kde_datadir)/knmap
shellrc_DATA = knmapui.rc nmap_manpage.html nmap_manpage.html.diff

kde_icon_TDEICON = hi16-app-scanclose.png hi32-app-scanclose.png \
hi16-app-scannew.png hi32-app-scannew.png hi16-app-scanrename.png hi32-app-scanrename.png \
hi16-app-scanduplicate.png hi32-app-scanduplicate.png hi16-app-manpage.png hi32-app-manpage.png

+ 0
- 0 View File