Author: wyoung
Date: Thu Jan 24 01:45:02 2008
New Revision: 2126
URL: http://svn.gna.org/viewcvs/mysqlpp?rev=2126&view=rev
Log:
Added OS X README
Added:
trunk/README-Mac-OS-X.txt
Modified:
trunk/README.txt
Added: trunk/README-Mac-OS-X.txt
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/README-Mac-OS-X.txt?rev=2126&view=auto
==============================================================================
--- trunk/README-Mac-OS-X.txt (added)
+++ trunk/README-Mac-OS-X.txt Thu Jan 24 01:45:02 2008
@@ -1,0 +1,76 @@
+OS X is Unix under the hood, so README-Unix.txt covers the generic
+bits. I'll just cover a few of the issues specific to OS X here.
+
+
+Prerequisite: Install the MySQL Development Files
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ MySQL++ is built on top of the MySQL C API library, so for MySQL++
+ to build, it needs at least that library and its header files
+ installed. You don't need the server itself installed on your
+ development machine, though it's often helpful anyway, for testing.
+ You can get MySQL in at least three different ways for OS X:
+
+ - From Fink: http://finkproject.org/ I mention this first
+ because it's the method I use to test MySQL++ in development.
+ If you ask about OS X on the mailing list, you'll get the most
+ help if you're also using the Fink version of MySQL. Once you
+ have Fink installed, install the MySQL C API development
+ files with:
+
+ $ fink install mysql15-dev
+
+ Then, in configuring MySQL++, give the --with-mysql=/sw flag
+ to the configure script.
+
+ - From MySQL.com. I've not tried the official binaries,
+ but they're known to work with MySQL++. As I understand it,
+ they install from a typical Mac GUI installer. I don't know
+ if it lets you install the development files separately from
+ the server itself, so be sure to check. The official Windows
+ installers, for instance, have in the past installed the server
+ by default but not the development files.
+
+ Once it's installed, the configure script shipped with MySQL++
+ v3.0 and up should find the library without any help.
+
+ - From MacPorts, http://macports.org. I have zero information on
+ this other than that it's theoretically possible for it to work.
+ If you figure out how to make it work, please post the method
+ to the mailing list so I can update this document.
+
+
+Making Universal Binaries
+~~~~~~~~~~~~~~~~~~~~~~~~~
+ The command line build system will generate libraries that
+ only work with the platform you build MySQL++ on. If you need
+ to generate a libmysqlpp that works on both Intel and PowerPC
+ machines, something like this may work:
+
+ $ ./configure CXXFLAGS='-arch ppc -arch i386' --disable-dependency-tracking
+
+ This is untested with MySQL++ in particular, but it's said to work
+ with other projects.
+
+ Note that with Tiger -- and to a greater extent, Leopard --
+ there are really *four* architectures, not two: you have 32-bit
+ and 64-bit versions of both PowerPC and Intel. I'm not sure
+ exactly how you'd modify the command above to make a library that
+ supports all four, but I'll take a wild guess and say you'll need
+ four -arch flags. Or, you can just avoid the command line build
+ system, and do it in...
+
+Xcode
+~~~~~
+ Until very recently, there's been no official support in MySQL++
+ for building on OS X using Xcode. People have gotten it to work
+ before on their own, but it's not something we felt we could
+ support directly.
+
+ As of MySQL++ v3.0, we're including Xcode project files. So far,
+ they're completely untested, but being part of the official
+ tarball, it obligates us to at least try to support them. :)
+ If they don't work, see HACKERS.txt for more info on fixing
+ the source files that generate these project files. We're not
+ terribly interested in receiving updated project files. They can
+ be useful for comparison, but ultimately what we care about is
+ being able to generate them correctly.
Modified: trunk/README.txt
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/README.txt?rev=2126&r1=2125&r2=2126&view=diff
==============================================================================
--- trunk/README.txt (original)
+++ trunk/README.txt Thu Jan 24 01:45:02 2008
@@ -60,24 +60,30 @@
Building the Library
~~~~~~~~~~~~~~~~~~~~
- MySQL++ uses Bakefile to generate platform-specific project files
- and makefiles from a single set of input files. We currently
- support these platforms:
+ MySQL++ uses Bakefile (http://bakefile.org/) to generate
+ platform-specific project files and makefiles from a single set
+ of input files. We currently support these platforms:
autoconf:
For Unixy platforms, including Linux, Mac OS X, and Cygwin. See
- README-Unix.txt for details. Supplementary details for Cygwin
- are in README-Cygwin.txt.
+ README-Unix.txt for details. Supplementary details for Cygwin
+ are in README-Cygwin.txt, and for OS X in README-Mac-OS-X.txt.
+
+ MinGW:
+ We ship Makefile.mingw for MinGW. It currently only builds the
+ static version of the library for technical reasons. This has
+ licensing ramifications. See README-MinGW.txt for details.
Visual C++:
We ship Visual C++ 2003 project files. This is the oldest
version MySQL++ will run on, due to compiler limitations.
See README-Visual-C++.txt for more details.
- MinGW:
- We ship Makefiles made for MinGW. These currently only work for
- building static versions of the library, which has licensing
- ramifications. See README-MinGW.txt for details.
+ Xcode:
+ We ship an Xcode v2 project file. It hasn't been tested
+ much yet, since the autoconf method works just fine on OS X.
+ As a result, we need both success and failure reports on the
+ mailing list. See README-Mac-OS-X.txt for more information.
Example Programs
_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits
