| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
These prevented Automake from creating the correct build rules.
|
| |
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Clean up the building of the doxygen docs for VPATH
builds and "make distcheck". This shifts the doxygen
run from "make install" time to "make all" time.
Fix a number of permissions in the docs we "cp -R" to
install them, and create the target dir before copying
manual files.
Have doxygen ignore subdirs like .git.
|
|
|
|
|
|
| |
Do not generate java/Makefile and petascope/Makefile.
Those appear to be unused and thus not shipped in the dist tarball.
|
|
|
|
|
|
| |
This requires newer automake versions, and xz being
installed. However, with those HUGE dist tarballs of
5+MB gzipped, this makes a lot of sense.
|
|
|
|
|
|
|
| |
Support (srcdir != builddir) VDIR builds.
This will also help a lot with preparing for a working
"make distcheck".
|
|
|
|
|
| |
Move automake option "--foreign" from Makefile.am to
configure.ac.
|
|
|
|
|
|
|
|
|
| |
automake 1.10 was released around the time autoconf 2.61
(which we already require) was released in late 2006, so
that should not present a real obstacle to people.
However, it at least avoids compatibility issues with even
more ancient versions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
Place $(logdir) in $(localstatedir)/log/$(PACKAGE) by default.
$(prefix)/log is not used by anybody, and special-casing a prefix of
"/usr/local" for a logdir of "/var/log" without "local" makes no sense.
|
|
|
|
|
| |
Fix typo for test port definition: The defined variable
is called RASMGR_PORT, not RASMGRPORT.
|
|
|
|
| |
"dnl" is the safer bet for comments in configure.ac.
|
|
|
|
| |
Properly quote m4 args, and avoid confusing it with bison.
|
|
|
|
| |
Use proper quoting for shell variables with spaces in their values.
|
| |
|
|
|
|
| |
documentation for more information.
|
| |
|
|
|
|
| |
architecture with branchs of mandatory test, fixed test, and open test. The rasql query tests are in mandatory test folder. The PG memleak test is in fixed test folder. User can add extra test by following a similar structure.
|
| |
|
|
|
|
| |
b523d72a5b65b362e499daf12f045ed9ba12ef28
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removed the rnprotocol Makefile and adjusted compilation structure.
Originally both rnprotocol, servercomm and clientcomm directories
were pushing files into libservercomm.a and libclientcomm.a.
Because the libraries stay in the directories where they were created
the libs were never merged.
While this was okay for the server it is impossible to deploy both
libraries that contain all the required object files.
Now the servercomm and cliencomm are responsible for compiling the
files in rnprotocol and joining them into the respective libraries.
|
|
|