| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
We still need to adapt the actual make rules and vars
so that an actual build might work.
|
| |
|
|
|
|
|
|
| |
We will keep only three Makefile.am:
* $(top_srcdir)
* manuals_and_examples/ (needs code to be generated first)
* systemtest/ (needs everything to be built)
|
| | |
|
| |
|
|
|
|
|
| |
Support (srcdir != builddir) VDIR builds.
This will also help a lot with preparing for a working
"make distcheck".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The CPPFLAGS, CFLAGS, CXXFLAGS, LDFLAGS vars should be
free for use by the person who does the build, so rasdaman
itself should put all its internally needed flags to
AM_CPPFLAGS, AM_CFLAGS, AM_CXXFLAGS, *_LIBS instead.
We do just that, and also put all the C preprocessor
defines in _CPPFLAGS so they are used for compiling
both C and C++ source files. This redistributes some
responsibilities from the _CFLAGS and _CXXFLAGS vars.
Also use _LDADD _LIBS where appropriate.
As a result, the user can now properly set CPPFLAGS,
CFLAGS, CXXFLAGS, LDFLAGS at configure or make time
and have these values used in the build.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Redefine $(pkgdatadir), $(pkgincludedir) and $(pkglibdir)
in order to make the subdir component configurable with the
RDM_SUBDIR variable.
Then install all libraries and include files to the package
specific subdirectories, as their names are far too generic
to allow general system wide installation, such as e.g.
"bool.h" or "libnetwork.a".
Move some very custom and non-general scripts (some with generic
names) to a new $(pkglibdir)/bin/ subdir.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
