Add basic cmake build instructions. Delete empty folder doc. Delete empty files ChangeLog, NEWS and TODO. Write basic README file. Signed-off-by: gregory guy <gregory-tde@laposte.net>pull/2/head
gregory guy
parent
39ca4c1588
commit
38ac3d062e
GPG Key ID:
2A75B7CA8ADED5CF
@ -1,6 +1,3 @@
|
|||||||
[submodule "admin"]
|
|
||||||
path = admin
|
|
||||||
url = https://system@scm.trinitydesktop.org/scm/git/tde-common-admin
|
|
||||||
[submodule "cmake"]
|
[submodule "cmake"]
|
||||||
path = cmake
|
path = cmake
|
||||||
url = https://system@scm.trinitydesktop.org/scm/git/tde-common-cmake
|
url = https://system@scm.trinitydesktop.org/scm/git/tde-common-cmake
|
||||||
|
|||||||
@ -1,167 +1,23 @@
|
|||||||
Basic Installation
|
Basic Installation
|
||||||
==================
|
==================
|
||||||
|
|
||||||
These are generic installation instructions.
|
kcmldapmanager relies on cmake to build.
|
||||||
|
|
||||||
The `configure' shell script attempts to guess correct values for
|
Here are suggested default options:
|
||||||
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
|
-DCMAKE_INSTALL_PREFIX="/opt/trinity" \
|
||||||
to figure out how `configure' could check whether to do them, and mail
|
-DCONFIG_INSTALL_DIR="/etc/trinity" \
|
||||||
diffs or instructions to the address given in the `README' so they can
|
-DSYSCONF_INSTALL_DIR="/etc" \
|
||||||
be considered for the next release. If at some point `config.cache'
|
-DXDG_MENU_INSTALL_DIR="/etc/xdg/menus" \
|
||||||
contains results you don't want to keep, you may remove or edit it.
|
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
|
||||||
|
-DCMAKE_VERBOSE_MAKEFILE="ON" \
|
||||||
|
-DCMAKE_SKIP_RPATH="OFF" \
|
||||||
|
-DBUILD_ALL="ON" \
|
||||||
|
-DWITH_ALL_OPTIONS="ON"
|
||||||
|
|
||||||
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'.
|
|
||||||
|
|
||||||
The simplest way to compile this package is:
|
Requirements:
|
||||||
|
=============
|
||||||
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
|
|
||||||
documentation.
|
|
||||||
|
|
||||||
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
|
|
||||||
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.
|
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
|
- libtdeldap
|
||||||
|
- Heimdal
|
||||||
|
|||||||
@ -1,22 +0,0 @@
|
|||||||
SUBDIRS = $(TOPSUBDIRS)
|
|
||||||
|
|
||||||
$(top_srcdir)/configure.in: configure.in.in $(top_srcdir)/subdirs
|
|
||||||
cd $(top_srcdir) && $(MAKE) -f admin/Makefile.common configure.in ;
|
|
||||||
|
|
||||||
$(top_srcdir)/subdirs:
|
|
||||||
cd $(top_srcdir) && $(MAKE) -f admin/Makefile.common subdirs
|
|
||||||
|
|
||||||
$(top_srcdir)/acinclude.m4: $(top_srcdir)/admin/acinclude.m4.in $(top_srcdir)/admin/libtool.m4.in
|
|
||||||
@cd $(top_srcdir) && cat admin/acinclude.m4.in admin/libtool.m4.in > acinclude.m4
|
|
||||||
|
|
||||||
MAINTAINERCLEANFILES = subdirs configure.in acinclude.m4 configure.files
|
|
||||||
|
|
||||||
package-messages:
|
|
||||||
cd $(top_srcdir) && $(MAKE) -f admin/Makefile.common package-messages
|
|
||||||
$(MAKE) -C po merge
|
|
||||||
|
|
||||||
EXTRA_DIST = admin COPYING configure.in.in
|
|
||||||
|
|
||||||
dist-hook:
|
|
||||||
cd $(top_distdir) && perl admin/am_edit -padmin
|
|
||||||
cd $(top_distdir) && $(MAKE) -f admin/Makefile.common subdirs
|
|
||||||
@ -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:
|
|
||||||
@ -0,0 +1,21 @@
|
|||||||
|
|
||||||
|
|
||||||
|
kcmldapmanager - a Kerberos realm management module for the Trinity
|
||||||
|
control center.
|
||||||
|
|
||||||
|
|
||||||
|
Kcmldapmanager is a Trinity control center module to manage users,
|
||||||
|
groups and machines in Kerberos realms.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
CONTRIBUTING
|
||||||
|
=============
|
||||||
|
|
||||||
|
If you wish to contribute kcmldapmanager, 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
|
||||||
@ -1 +0,0 @@
|
|||||||
Subproject commit 68f23556e638353e46b444d3a4863a64936bd36a
|
|
||||||
@ -1,10 +0,0 @@
|
|||||||
INCLUDES= $(all_includes) $(KDE_INCLUDES)/tde $(KRB5_CFLAGS)
|
|
||||||
|
|
||||||
bin_PROGRAMS = tdeldapmanager
|
|
||||||
|
|
||||||
tdeldapmanager_SOURCES = main.cpp
|
|
||||||
|
|
||||||
tdeldapmanager_METASOURCES = AUTO
|
|
||||||
tdeldapmanager_LDFLAGS = $(all_libraries) $(KDE_RPATH) $(LIB_TQT) -lDCOP $(LIB_TDECORE) $(LIB_TDEUI) -ltdefx $(LIB_TDEIO) -ltdetexteditor -ltdeldap $(KRB5_LIBS)
|
|
||||||
|
|
||||||
KDE_OPTIONS = nofinal
|
|
||||||
@ -1,2 +0,0 @@
|
|||||||
./admin/configure.in.min
|
|
||||||
configure.in.in
|
|
||||||
@ -1,43 +0,0 @@
|
|||||||
#MIN_CONFIG(3.2.0)
|
|
||||||
|
|
||||||
AM_INIT_AUTOMAKE(autostart, 0.1)
|
|
||||||
AC_C_BIGENDIAN
|
|
||||||
AC_CHECK_KDEMAXPATHLEN
|
|
||||||
|
|
||||||
|
|
||||||
PKG_CHECK_MODULES(KRB5, krb5, have_krb5=yes, have_krb5=no)
|
|
||||||
if test "x$have_krb5" = "xno"; then
|
|
||||||
# Try to find krb5 without pkg-config file
|
|
||||||
AC_MSG_CHECKING(krb5)
|
|
||||||
AC_FIND_FILE(krb5.h, [\
|
|
||||||
/usr/local/include/heimdal /usr/local/include \
|
|
||||||
/usr/include/heimdal /usr/include \
|
|
||||||
], krb5_includes)
|
|
||||||
if test "x$krb5_includes" != "xNO"; then
|
|
||||||
krb5_multiarch="`gcc -print-multiarch 2>/dev/null`"
|
|
||||||
AC_FIND_FILE(libkrb5.so, [\
|
|
||||||
/usr/local/lib/$krb5_multiarch/heimdal /usr/local/lib64/heimdal /usr/local/lib/heimdal \
|
|
||||||
/usr/local/lib/$krb5_multiarch /usr/local/lib64 /usr/local/lib \
|
|
||||||
/usr/lib/$krb5_multiarch/heimdal /usr/lib64/heimdal /usr/lib/heimdal \
|
|
||||||
/usr/lib/$krb5_multiarch /usr/lib64 /usr/lib \
|
|
||||||
], krb5_libs)
|
|
||||||
if test "x$krb5_libs" != "xNO"; then
|
|
||||||
AC_MSG_RESULT([libraries $krb5_libs, headers $krb5_includes])
|
|
||||||
CPPFLAGS="$CPPFLAGS -I$krb5_includes"
|
|
||||||
CFLAGS="$CFLAGS -I$krb5_includes"
|
|
||||||
LDFLAGS="$LDFLAGS -L$krb5_libs"
|
|
||||||
AC_CHECK_HEADER(krb5.h, have_krb5=yes)
|
|
||||||
fi
|
|
||||||
fi
|
|
||||||
if test "x$have_krb5" != "xno"; then
|
|
||||||
KRB5_CFLAGS="-I$krb5_includes"
|
|
||||||
KRB5_LIBS="-L$krb5_libs -lkrb5"
|
|
||||||
AC_SUBST(KRB5_CFLAGS)
|
|
||||||
AC_SUBST(KRB5_LIBS)
|
|
||||||
else
|
|
||||||
AC_MSG_RESULT(no)
|
|
||||||
fi
|
|
||||||
fi
|
|
||||||
if test "x$have_krb5" = "xno"; then
|
|
||||||
AC_MSG_ERROR([krb5 library is needed but not found on our system])
|
|
||||||
fi
|
|
||||||
@ -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_LANG = en
|
|
||||||
KDE_DOCS = autostart
|
|
||||||
SUBDIRS = $(AUTODIRS)
|
|
||||||
@ -1,2 +0,0 @@
|
|||||||
KDE_DOCS = ldap
|
|
||||||
KDE_LANG = en
|
|
||||||
@ -1,2 +0,0 @@
|
|||||||
POFILES = AUTO
|
|
||||||
# noinst_HEADERS = ldap.pot
|
|
||||||
@ -1,19 +0,0 @@
|
|||||||
INCLUDES = $(all_includes) $(KDE_INCLUDES)/tde $(KRB5_CFLAGS)
|
|
||||||
METASOURCES = AUTO
|
|
||||||
|
|
||||||
# Install this plugin in the KDE modules directory
|
|
||||||
kde_module_LTLIBRARIES = kcm_ldapmanager.la
|
|
||||||
|
|
||||||
kcm_ldapmanager_la_SOURCES = ldapmgr.cpp ldapconfigbase.ui userconfigbase.ui groupconfigbase.ui machineconfigbase.ui serviceconfigbase.ui userconfigdlg.cpp groupconfigdlg.cpp machineconfigdlg.cpp serviceconfigdlg.cpp
|
|
||||||
kcm_ldapmanager_la_LIBADD = -ltdeio $(LIB_TDEUI) -lldap -ltdeldap
|
|
||||||
kcm_ldapmanager_la_LDFLAGS = -avoid-version -module -no-undefined \
|
|
||||||
$(all_libraries) $(KRB5_LIBS)
|
|
||||||
|
|
||||||
|
|
||||||
xdg_apps_DATA = ldapmanager.desktop
|
|
||||||
|
|
||||||
|
|
||||||
messages: rc.cpp
|
|
||||||
$(EXTRACTRC) `find -name \*.ui -o -name \*.rc` > rc.cpp
|
|
||||||
$(XGETTEXT) *.cpp -o $(podir)/kcmldapmanager.pot
|
|
||||||
|
|
||||||
Loading…
Reference in new issue