From 8fc1fc844a9695fb0d1d5d3c13393d4709ce7592 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Fri, 18 Feb 2011 15:58:27 +0200
Subject: Add binary package resources

---
 binary/mingw/README          | 52 ++++++++++++++++++++++++++++++++++++++++++++
 binary/mingw/default.options |  8 +++++++
 binary/mingw/manifest.txt    | 14 ++++++++++++
 3 files changed, 74 insertions(+)
 create mode 100644 binary/mingw/README
 create mode 100644 binary/mingw/default.options
 create mode 100644 binary/mingw/manifest.txt

(limited to 'binary/mingw')

diff --git a/binary/mingw/README b/binary/mingw/README
new file mode 100644
index 0000000..390f3b3
--- /dev/null
+++ b/binary/mingw/README
@@ -0,0 +1,52 @@
+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 pre-compiled binary distribution of the ODB
+compiler for Windows. The top-level directory structure of this package
+is as follows:
+
+bin\          ODB compiler binary
+etc\          ODB compiler configuration
+doc\          ODB system documentation
+man\          man pages for the ODB compiler
+mingw\        GCC compiler, MinGW, and MSYS binaries, see manifest
+              inside for details
+
+To install this package simply unpack it into a directory of your choice,
+for example C:\tools. The ODB compiler binary will be in the bin\
+directory inside the package directory, for example
+C:\tools\odb-x.y.z-i686-windows\bin\. You can run the ODB compiler by
+either using the absolute path, for example:
+
+C:\tools\odb-x.y.z-i686-windows\bin\odb --version
+
+Or you can add the bin\ directory to the Path environment variable. To
+accomplish this, open Control Panel, then System, select the Advanced tab
+and click on the Environment Variables button. If you have administrator
+privileges, select the Path variable from the System variables list.
+Otherwise, select (or create) the Path variable from the User variables
+list. Click the Edit button and add the bin\ directory to the list. Click
+Ok, then log off and log on again for the changes to take effect. Once this
+is done, you should be able to run the ODB compiler by using just its name,
+for example:
+
+odb --version
+
+If you would like to add commonly-used libraries, such as Boost or Qt,
+to the ODB compiler header search list, you can add them to the
+etc\odb\default.options file (this file serves a similar purpose in ODB
+as the VC++ Directories dialog in VC++). For more information, refer to
+the instructions at the beginning of this file.
+
+Note also that while you can move the ODB compiler directory around, you
+cannot move the individual sub-directories or files inside it. For example,
+copying the ODB compiler executable to
+C:\Windows will not work.
+
+Send questions, bug reports, or any other feedback to the
+odb-users@codesynthesis.com mailing list.
diff --git a/binary/mingw/default.options b/binary/mingw/default.options
new file mode 100644
index 0000000..89c4f30
--- /dev/null
+++ b/binary/mingw/default.options
@@ -0,0 +1,8 @@
+# Default ODB options file. This file is automatically loaded by the ODB
+# compiler and can be used for installation-wide customizations, such as
+# adding an include search path for a commonly used library. In this
+# regard, the default options file in ODB serves a role similar to the
+# VC++ Directories dialog in VC++. For example:
+#
+# -I C:\boost_1_45_0
+#
diff --git a/binary/mingw/manifest.txt b/binary/mingw/manifest.txt
new file mode 100644
index 0000000..fe8d583
--- /dev/null
+++ b/binary/mingw/manifest.txt
@@ -0,0 +1,14 @@
+This directory contains components from the MinGW and MSYS systems as
+well as the GCC compiler.
+
+The MinGW and GCC distributions are comprised of several different
+packages. Each of the various packages is governed by its own
+individual copyright and licensing terms. Some of those packages are
+licensed by the GNU Public License (GPL) or the GNU Lesser General
+Public License(LGPL), some are licensed in the Public Domain and some
+have their own open-source licenses.
+
+For full source code and licensing details see:
+
+MinGW and MSYS:   http://www.mingw.org 
+GCC:              http://gcc.gnu.org
-- 
cgit v1.1