Re: [CMake] [vtk-developers] python, postgreSQL, VTK build

2008-08-30 Thread Darren Weber
With some manual tweaks, I got the following cmake variable settings: POSTGRES_INCLUDE_DIRECTORIES /Library/PostgreSQL/8.3/include POSTGRES_LIBRARIES /Library/PostgreSQL/8.3/lib/libpq.dylib PQXX_HEADER_PATH /usr/local/include PQXX_INCLUDE_DIRECTORIES /usr/local/include;/Library/PostgreSQL/8.

Re: [CMake] [vtk-developers] python, postgreSQL, VTK build

2008-08-29 Thread Darren Weber
I downloaded libpqxx-2.6.9.tar.gz and build in /usr/src/libpqxx-2.6.9 Before doing anything, we have /usr/src/pqxx-2.6.9/include/pqxx/config.h.inwith: /* Define if the compiler supports the standard "long double" type */ #undef PQXX_HAVE_LONG_DOUBLE /* Define if the compiler supports "long long"

Re: [CMake] [vtk-developers] python, postgreSQL, VTK build

2008-08-29 Thread David C Thompson
> My prior build for libpqxx was: > > ./configure --enable-shared > make > sudo make install > > So now I have pqxx 2.6.9, but how do I enable the LONG_LONG support? Just make sure that the configure script reported "checking for long long: yes" instead of "checking for long long: no". If your

Re: [CMake] [vtk-developers] python, postgreSQL, VTK build

2008-08-29 Thread David Thompson
> For my install of PGSQL, I had to build pqxx from source and I have > the following libraries: Doh! I thought the change from libpq+libpqxx to just libpq made it into VTK 5.2. I guess not. Anyway, you will need libpqxx version 2.6.9 with the ALLOW_LONG_LONG option turned because VTK requires 64-

Re: [CMake] [vtk-developers] python, postgreSQL, VTK build

2008-08-29 Thread David Cole
Including the "libpq.dylib" at the end. It's a full path to a file. On Fri, Aug 29, 2008 at 4:45 PM, David Cole <[EMAIL PROTECTED]> wrote: > Set POSTGRES_LIBRARIES to the full path to the pq dylib... > > > On Fri, Aug 29, 2008 at 4:39 PM, Darren Weber < > [EMAIL PROTECTED]> wrote: > >> >> For my

Re: [CMake] [vtk-developers] python, postgreSQL, VTK build

2008-08-29 Thread David Cole
Set POSTGRES_LIBRARIES to the full path to the pq dylib... On Fri, Aug 29, 2008 at 4:39 PM, Darren Weber <[EMAIL PROTECTED]>wrote: > > For my install of PGSQL, I had to build pqxx from source and I have the > following libraries: > > [ [EMAIL PROTECTED] ~/src/kitware/VTK_build ]$ ls > /Library/Po

Re: [CMake] [vtk-developers] python, postgreSQL, VTK build

2008-08-29 Thread Darren Weber
For my install of PGSQL, I had to build pqxx from source and I have the following libraries: [ [EMAIL PROTECTED] ~/src/kitware/VTK_build ]$ ls /Library/PostgreSQL/8.3/lib/ libecpg.6.0.dylib* libecpg.dylib@ libecpg_compat.a libpgtypes.3.0.dylib* libpgtypes.dylib@ libpq.a libecpg.6.dy

Re: [CMake] [vtk-developers] python, postgreSQL, VTK build

2008-08-29 Thread David Cole
As David Thompson rightfully pointed out, we should not be using LINK_LIBRARIES in VTK's CMakeLists.txt files. Change the LINK_LIBRARIES statement in VTK/IO/CMakeLists.txt to: SET(KIT_LIBS ${KIT_LIBS} ${POSTGRES_LIBRARIES}) and make sure that POSTGRES_LIBRARIES has the full path to pq in it, a

Re: [CMake] [vtk-developers] python, postgreSQL, VTK build

2008-08-29 Thread Darren Weber
I had some choices on how to install MySQL and PostgreSQL on OS X (Leopard Server, in my case). There is a "default" install of MySQL for Leopard server, but it had no development libraries that I could find. There was no default install of PostgreSQL. I first tried macports, but I found some pr