Drop automake build support.

Delete empty file NEWS.
Add basic cmake build instructions.
Rework of the README file.

Signed-off-by: gregory guy <gregory-tde@laposte.net>

13 files changed, 37 insertions, 270 deletions

diff --git a/.gitmodules b/.gitmodules
deleted file mode 100644
index 934def7..0000000
--- a/.gitmodules
+++ /dev/null
@@ -1,3 +0,0 @@
-[submodule "admin"]
-	path = admin
-	url = https://system@scm.trinitydesktop.org/scm/git/tde-common-admin
diff --git a/INSTALL b/INSTALL
index 28fadaa..8c82cfb 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,181 +1,26 @@
 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').
+tde-style-domino relies on cmake to build.
 
-   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.
+Here are suggested default options:
 
-   The file `configure.in' is used to create `configure' by a program
-called `autoconf'.  You only need `configure.in' if you want to change
-it or regenerate `configure' using a newer version of `autoconf'.
+ -DCMAKE_EXPORT_COMPILE_COMMANDS="ON" \
+ -DCMAKE_INSTALL_PREFIX="/opt/trinity" \
+ -DCONFIG_INSTALL_DIR="/etc/trinity" \
+ -DSYSCONF_INSTALL_DIR="/etc/trinity" \
+ -DXDG_MENU_INSTALL_DIR="/etc/xdg/menus" \
+ -DCMAKE_BUILD_TYPE=RelWithDebInfo \
+ -DCMAKE_VERBOSE_MAKEFILE="ON" \
+ -DCMAKE_SKIP_RPATH="OFF" \
+ -DBUILD_ALL="ON" \
+ -DWITH_ALL_OPTIONS="ON"
 
-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 awhile.  While running, it prints some
-     messages telling which features it is checking for.
-
-  2. Type `make' to compile the package.
-
-  3. Optionally, type `make check' to run any self-tests that come with
-     the package.
-
-  4. Type `make install' to install the programs and any data files and
-     documentation.
-
-  5. You can remove the program binaries and object files from the
-     source code directory by typing `make clean'.  To also remove the
-     files that `configure' created (so you can compile the package for
-     a different kind of computer), type `make distclean'.  There is
-     also a `make maintainer-clean' target, but that is intended mainly
-     for the package's developers.  If you use it, you may have to get
-     all sorts of other programs in order to regenerate files that came
-     with the distribution.
-
-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
-this:
-     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
-architecture.
-
-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.
-
-   In addition, if you use an unusual directory layout you can give
-options like `--bindir=PATH' to specify different values for particular
-kinds of files.  Run `configure --help' for a list of the directories
-you can set and what kinds of files go in them.
-
-   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:
-     CPU-COMPANY-SYSTEM
-
-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 `config.site' that gives
-default values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' 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
-operates.
-
-`--cache-file=FILE'
-     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'.
-
-`--help'
-     Print a summary of the options to `configure', and exit.
-
-`--quiet'
-`--silent'
-`-q'
-     Do not print messages saying which checks are being made.
-
-`--srcdir=DIR'
-     Look for the package's source code in directory DIR.  Usually
-     `configure' can determine that directory automatically.
-
-`--version'
-     Print the version of Autoconf used to generate the `configure'
-     script, and exit.
-
-`configure' also accepts some other, not widely useful, options.
+Requirements:
+=============
 
+- libXft
+- libXext
+- FreeType
diff --git a/Makefile.am b/Makefile.am
deleted file mode 100644
index 55d4b5d..0000000
--- a/Makefile.am
+++ /dev/null
@@ -1,11 +0,0 @@
-
-AUTOMAKE_OPTIONS = foreign 1.5
-DISTCLEANFILES = inst-apps
-MAINTAINERCLEANFILES = subdirs configure.in acinclude.m4 configure.files
-
-include admin/deps.am
-
-include admin/Doxyfile.am
-
-#SUBDIRS=$(TOPSUBDIRS)
-SUBDIRS = domino dominoConfig client
diff --git a/Makefile.cvs b/Makefile.cvs
deleted file mode 100644
index 4c0afd1..0000000
--- a/Makefile.cvs
+++ /dev/null
@@ -1,10 +0,0 @@
-all: 
-	@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
-
-dist:
-	$(MAKE) -f admin/Makefile.common dist
-
-.SILENT:
diff --git a/NEWS b/NEWS
deleted file mode 100644
index e69de29..0000000
--- a/NEWS
+++ /dev/null
diff --git a/README b/README
index e69de29..1a91bb4 100644
--- a/README
+++ b/README
@@ -0,0 +1,20 @@
+
+ tde-style-domino - a custom widget style and twin decoration for TDE.
+
+
+tde-style-domino is a style (theme) with a soft look.
+It allows to fine adjust the shininess of the widgets by customizable
+color gradients.
+
+
+
+ CONTRIBUTING
+==============
+
+If you wish to contribute to tde-style-domino, you might do so:
+
+- TDE Gitea Workspace (TGW) collaboration tool.
+  https://mirror.git.trinitydesktop.org/gitea
+
+- TDE Weblate Translation Workspace (TWTW) collaboration tool.
+  https://mirror.git.trinitydesktop.org/weblate
diff --git a/admin b/admin
deleted file mode 160000
-Subproject 8c7e0d40de084fe5d54e173918756639e0d4d63
diff --git a/client/Makefile.am b/client/Makefile.am
deleted file mode 100644
index 8897278..0000000
--- a/client/Makefile.am
+++ /dev/null
@@ -1,16 +0,0 @@
-
-INCLUDES = $(all_includes) -I$(kde_includes)/twin
-
-SUBDIRS = . config
-
-kde_module_LTLIBRARIES = twin3_domino.la
-
-twin3_domino_la_SOURCES = dominoclient.cpp
-twin3_domino_la_LDFLAGS = $(all_libraries) $(KDE_PLUGIN) -module -L/usr/X11R6/lib 
-twin3_domino_la_LIBADD  = $(LIB_TDECORE) $(kde_libraries)/libtdecorations.la -lXext -lX11 $(LIB_TQT)
-
-METASOURCES = AUTO
-noinst_HEADERS = dominoclient.h
-
-lnkdir = $(kde_datadir)/twin
-lnk_DATA = domino.desktop
diff --git a/client/config/Makefile.am b/client/config/Makefile.am
deleted file mode 100644
index 0e0c631..0000000
--- a/client/config/Makefile.am
+++ /dev/null
@@ -1,10 +0,0 @@
-INCLUDES = $(all_includes)
-
-kde_module_LTLIBRARIES = twin_domino_config.la
-
-twin_domino_config_la_SOURCES = config.cpp
-twin_domino_config_la_LDFLAGS = $(all_libraries) $(KDE_PLUGIN) -module
-twin_domino_config_la_LIBADD = $(LIB_TDEUI) $(LIB_TQT) $(LIB_TDECORE)
-
-METASOURCES = AUTO
-noinst_HEADERS = dominoConfig.h
diff --git a/configure.in.in b/configure.in.in
deleted file mode 100644
index 62cbc08..0000000
--- a/configure.in.in
+++ /dev/null
@@ -1,6 +0,0 @@
-#MIN_CONFIG
-
-PKG_CHECK_MODULES(FT2, freetype2, have_ft2=yes, have_ft2=no)
-if test "x$have_ft2" = "xno"; then
-  AC_MSG_ERROR([freetype2 library is needed but not found on our system])
-fi
diff --git a/domino/Makefile.am b/domino/Makefile.am
deleted file mode 100644
index 0e399b8..0000000
--- a/domino/Makefile.am
+++ /dev/null
@@ -1,24 +0,0 @@
-AUTOMAKE_OPTIONS = foreign
-
-KDE_CXXFLAGS = -DQT_PLUGIN $(FT2_CFLAGS)
-
-INCLUDES = $(all_includes)
-
-stylercdir = $(kde_datadir)/tdestyle/themes
-stylerc_DATA = domino.themerc
-schemedir = $(kde_datadir)/tdedisplay/color-schemes
-scheme_DATA = Domino.kcsrc
-
-noinst_HEADERS = domino.h misc.h data.h
-
-kde_style_LTLIBRARIES = domino.la
-domino_la_SOURCES = domino.cpp misc.cpp
-domino_la_LDFLAGS = $(all_libraries) $(KDE_PLUGIN) -module $(KDE_RPATH)
-domino_la_LIBADD = $(LIB_TDEUI) $(LIB_TDEUTILS) $(LIB_TQT) -ltdefx -lXrender -lXft $(LIB_TDECORE)
-domino_la_METASOURCES = AUTO
-
-noinst_LTLIBRARIES = libdomino_style.la
-libdomino_style_la_SOURCES =
-libdomino_style_la_LIBADD = $(domino_la_OBJECTS) $(domino_la_LIBADD)
-
-DISTCLEANFILES = $(domino_la_METASOURCES)
diff --git a/dominoConfig/Makefile.am b/dominoConfig/Makefile.am
deleted file mode 100644
index d4e26d1..0000000
--- a/dominoConfig/Makefile.am
+++ /dev/null
@@ -1,8 +0,0 @@
-INCLUDES = $(all_includes) $(FT2_CFLAGS)
-
-noinst_HEADERS = dominoconf.h
-kde_module_LTLIBRARIES = tdestyle_domino_config.la
-tdestyle_domino_config_la_LDFLAGS = $(all_libraries) $(KDE_PLUGIN) -module 
-tdestyle_domino_config_la_LIBADD  = $(LIB_TDEUI) ../domino/libdomino_style.la $(LIB_TQT) $(LIB_TDECORE) -ltdefx $(LIB_TDEIO)
-tdestyle_domino_config_la_SOURCES = dominoconf.cpp
-tdestyle_domino_config_la_METASOURCES = AUTO
diff --git a/getimages/getimages.pro b/getimages/getimages.pro
deleted file mode 100644
index 86e32ee..0000000
--- a/getimages/getimages.pro
+++ /dev/null
@@ -1,10 +0,0 @@
-######################################################################
-# Automatically generated by qmake (1.07a) Thu Jul 19 02:11:17 2007
-######################################################################
-
-TEMPLATE = app
-CONFIG -= moc
-INCLUDEPATH += .
-
-# Input
-SOURCES += getimages.cpp