From 9cce004234838754b8bd7776b4ed37686c9a17c2 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Wed, 16 Nov 2011 07:42:13 +0200 Subject: Add standard initial files --- .gitignore | 21 +++++++++++++++++ INSTALL | 1 + INSTALL-GIT | 78 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ LICENSE | 1 + NEWS | 1 + README | 20 ++++++++++++++++ version | 1 + 7 files changed, 123 insertions(+) create mode 100644 .gitignore create mode 100644 INSTALL create mode 100644 INSTALL-GIT create mode 100644 LICENSE create mode 100644 NEWS create mode 100644 README create mode 100644 version diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..3b9998d --- /dev/null +++ b/.gitignore @@ -0,0 +1,21 @@ +# Compiler/linker output. +# +*.o +*.o.d +*.so +*.a +*.l +*.l.cpp-options + +# Generated documentation. +# +*.pdf +*.ps + +# Generated build system files. +# +*-dynamic.make + +# Generated .gitignore files. +# +.gitignore diff --git a/INSTALL b/INSTALL new file mode 100644 index 0000000..d8fc40d --- /dev/null +++ b/INSTALL @@ -0,0 +1 @@ +@@ Complete INSTALL instructions \ No newline at end of file diff --git a/INSTALL-GIT b/INSTALL-GIT new file mode 100644 index 0000000..f917af5 --- /dev/null +++ b/INSTALL-GIT @@ -0,0 +1,78 @@ +The following instructions describe how to work with the source code that was +checked out from the git repository. + +The major difference between using a released source code package and source +code from the repository is that the former does not contain autotools-based +makefiles or Visual Studio project files. Instead, it contains templates for +these files as well as its own, custom build system. This build system is +used for development as well as to automatically generate the autotools and +Visual Studio files. + +This file describes how to use this build system to build the package as well +as to create a release-ready source distribution which contains the autotools +build system and Visual Studio project files. + + +Prerequisites +============= + +Besides the prerequisites listed in the INSTALL file, you will need the +following additional packages: + + - GNU bash >= 2.0.0 http://www.gnu.org/software/bash/ + - GNU make >= 3.81 http://www.gnu.org/software/make/ + - build >= latest http://www.codesynthesis.com/projects/build/ + +If you are planning to create the source code distributions, then you will +also need the following packages: + + - GNU m4 >= 1.4.0 http://www.gnu.org/software/m4/ + - GNU sed >= 4.0.0 http://www.gnu.org/software/sed/ + - tofrodos >= 1.7.0 http://www.thefreecountry.com/tofrodos/ + +As we as the GNU autotools: + + - GNU libtool >= 2.2.6b http://www.gnu.org/software/libtool/ + - GNU autoconf >= 2.67 http://www.gnu.org/software/autoconf/ + - GNU automake >= 1.11.1 http://www.gnu.org/software/automake/ + +Any reasonably up to date GNU/Linux installation would normally have all of +the above packages already present, except for build and maybe tofrodos. + + +Configuring and Building +======================== + +To build the source code simply run make in the root directory of the package. +The first time you run make, the build process will also configure the +package by asking you several questions. On the subsequent runs, make will +only rebuild what has changed. + +To run the automated test suite (if any), run 'make test'. To clean the object +files, executables, etc., run 'make clean'. To de-configure the package (that +is, to remove configuration files in addition to objects, executables, etc.), +run 'make disfigure'. + + +Creating Distribution +===================== + +To create the source code distribution, use the dist make target as well as +the dist_prefix variable to specify the directory where the distribution files +should be placed. For example: + +make dist dist_prefix=/tmp/package-1.1.0 + +Once the distribution files are ready, change to the distribution directory +and run the bootstrap script to bootstrap the autotools build system, for +example: + +cd /tmp/package-1.1.0 +./bootsrap + +To create the source code archives, use the autotools build system. First +configuring the package (see the INSTALL file for more information on this +step) and then use the dist target to make the archives, for example: + +./configure +make dist diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..444e226 --- /dev/null +++ b/LICENSE @@ -0,0 +1 @@ +Copyright (c) Code Synthesis Tools CC 2011. All rights reserved. diff --git a/NEWS b/NEWS new file mode 100644 index 0000000..72d0f8b --- /dev/null +++ b/NEWS @@ -0,0 +1 @@ +See the common NEWS file in the ODB compiler package. diff --git a/README b/README new file mode 100644 index 0000000..21671b7 --- /dev/null +++ b/README @@ -0,0 +1,20 @@ +ODB is an object-relational mapping (ORM) system for C++. It provides +tools, APIs, and library support that allow you to persist C++ objects +to a relational database (RDBMS) without having to deal with tables, +columns, or SQL and without manually writing any of the mapping code. +For more information see: + +http://www.codesynthesis.com/products/odb/ + +This package contains the Microsoft SQL Server ODB runtime library. +Every application that includes code generated for the SQL Server +database will need to link to this library. + +See the NEWS file for the user-visible changes from the previous release. + +See the LICENSE file for distribution conditions. + +See the INSTALL file for prerequisites and installation instructions. + +Send questions, bug reports, or any other feedback to the +odb-users@codesynthesis.com mailing list. diff --git a/version b/version new file mode 100644 index 0000000..38a3807 --- /dev/null +++ b/version @@ -0,0 +1 @@ +1.7.0.a1 -- cgit v1.1