Chris Frey wrote:
> For unix, if you're building from svn, you'll need to run all the autoconf
> tools. There is a 'bootstrap' script to make that easy. So far I haven't
> had any trouble with the autoconf side of things.
>
> To specify a different compiler, I use a command line like this (assuming
> I've built gcc-4.0.1 and installed it in /home/source5/rootdir-gcc401):
>
> ./configure --prefix=/usr/local \
> CC=/home/source5/rootdir-gcc401/bin/gcc \
> CPP=/home/source5/rootdir-gcc401/bin/cpp \
> CXX=/home/source5/rootdir-gcc401/bin/g++ \
> CXXCPP=/home/source5/rootdir-gcc401/bin/cpp
>
> I can use a compiler built in any old home directory using this. To run the
> results using a new compiler like gcc-4.0.1 when my system compiler is
> gcc-3.3.6, I have to do:
>
> export LD_LIBRARY_PATH=/home/source5/rootdir-gcc401/lib
After I downloaded mysqlpp using svn, what's the next step to do??
makemake.sh or configure?? I doesn't make alot of sence to me that it
has boostrap script or all autoconf tools - I don't really know that
therminology :) Most of the distributions have a readme that tells what
to do and almost always it's ./configure && make install clean
with mysqlpp I don't know where to start from. (makemake.sh fails,
there's no configure script etc.)
I use FreeBSD, it has a really nice ports collection, but it has older
version of mysql++ (1.7.x); with freebsd all I'd need to do to install
mysqlpp would be: cd /usr/ports/databases/mysql++; make install clean;
which downloades sources, configures and installs it (with all dependent
software using the right compiler). With freebsd there's no need to
specify extra LD_LIB_PATH etc, all is needed is to use g++34 instead of
g++ - it figures out where correct library is located by itself...
