Skip to content

Commit

Permalink
Remove obsolete text from INSTALL-Windows.md4.
Browse files Browse the repository at this point in the history
  • Loading branch information
@jtv
jtv committed Jan 11, 2020
1 parent 727f550 commit e51d180
Showing 1 changed file with 20 additions and 331 deletions.
351 changes: 20 additions & 331 deletions INSTALL-Windows.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,17 +21,6 @@ libpqxx distribution.
We'll be using the command line throughout this document.


Build Environment
-----------------

If you use MSYS, you may need various additional tools (such as "mktemp")
installed. If you use Visual C++, make sure you have at least the 2015 version
or you'll run into serious compilation trouble.

You may have to make some adjustments to these instructions and scripts for the
build to succeeed. If you do, let us know so we can improve the procedure.


Obtaining libpq
---------------

Expand Down Expand Up @@ -106,47 +95,6 @@ extra "D" in their names.
below).


Preparing to Compile libpqxx
----------------------------

The rest of this text will assume that you have the libpq library in its binary
form(s), as well as its header files. Now, to work on building libpqxx!

You'll need to provide certain common settings:

i) Copy the file `win32/common-sample` to `win32/common`, and edit the latter
to reflect the paths to your PostgreSQL includes and library files:
- If you compiled PostgreSQL for yourself to obtain libpq, set PGSQLSRC in
win32/common to point to the "src" subdirectory in your PostgreSQL source
tree.
- If you installed libpq using the One Click Installer, verify that
PGSQLSRC points to your specific installation of PostgreSQL. Then follow
the instructions in `win32/common`.
- If you obtained libpq in any other way, you may be able to build libpqxx
by making the appropriate adjustments to the `common` file.

ii) Create the configuration headers: `include/pqxx/config-*-*.h`. The
easiest start for this is to copy from available samples. In
`config/sample-headers`, find the directories most closely matching your
compiler and libpq version, respectively. Take the `config-*-*.h` headers
from those directories and copy them into the `include/pqxx/` directory.
On a Unix-like system these headers would be generated automatically by the
configure script; in the Windows case they may need some editing. How these
files work is described in more detail below.

iii) If you are building libpqxx from a development source tree rather than from
a release distribution, you may not have the makefiles for your compiler.
These makefiles should be in the `win32` directory and have names ending in
".mak": "mingw.mak," "vc-libpqxx.mak," "vc-test.mak," and so on. If you
don't have these files but you do have a python interpreter, you can
generate them using the template2mak.py script in the tools directory:

tools/template2mak.py win32/mingw.mak.template win32/mingw.mak
tools/template2mak.py win32/vc-libpqxx.mak.template win32/vc-libpqxx.mak
tools/template2mak.py win32/vc-test.mak.template win32/vc-test.mak
tools/template2mak.py win32/vc-test-unit.mak.template win32/vc-test-unit.mak


Building libpqxx
----------------

Expand All @@ -155,41 +103,24 @@ The rest of the procedure depends on your compiler.

### Visual Studio

If you're using Visual C++:

1) Select Visual Studio Command Prompt from the Start menu ("Developer Command
Prompt" if building for x86 and "x64 Native Tools Command Prompt" if building
for x64). Alternatively, open a Command Prompt window and run

VCVARSALL.BAT amd64
If you're using Visual C++, use the CMake build. First, run the vcvars64
script:

to prepare the environment.
Then CD into the main directory of the libpqxx source tree. Among other
things it will contain the files "configure" and "Makefile.am," and
subdirectories "src," "include," "win32" etc.
call "<compiler>\2019\Community\VC\Auxiliary\Build\vcvars64.bat"

2) Run:
(Replace `<compiler>` with the path to your compiler's installation location.)

"nmake /f win32/vc-libpqxx.mak ALL"
Then, in the directory where you want to do the build, configure for building:

to compile all dynamic, static, debug and release libraries. Once
completed, you will find them in these libraries in the lib directory. The
build script also copies the libpq dlls and stub libraries to the lib
directory. You will have to link with these files when building
applications that use libpqxx clases and methods.
cmake <source-directory> -DBUILD_SHARED_LIBS=1

3) Your version of the libpq DLL may require other DLLs in order to execute.
If you installed libpq with the one click installer, these DLLs can be found
in the same folder as libpq itself. The exact set of DLLs varies depending
on the version of PostgreSQL that you installed. For the 9.1 version
of the One Click Installer, they were: `libeay32.dll`, `libiconv-2.dll`,
`libintl-8.dll`, and `ssleay32.dll`.
Replace `<source-directory>` with the path to where your libpqxx source tree
is. The `-DBUILD_SHARED_LIBS=1` is only needed if you're building a shared
library.

4) Once you have identified any additional DLLs, you should copy them to
another location (perhaps the libpqxx lib folder).
Finally, compile:

5) At this point, you will no longer need to keep the postgres sources or
binaries on your computer to build applications with libpqxx.
msbuild libpqxx.sln


### MinGW
Expand All @@ -205,263 +136,21 @@ Running the test suite
----------------------

After building libpqxx, it is recommended that you compile and run the
self-test programs included in the package. Unix, Cygwin, or MSYS users simply
type "make check" to build and run the entire regression test. For Visual C++
users, the following steps should accomplish the same:

1) To build all of the self-test configurations, run:
nmake /f win32\vc-test.mak ALL
nmake /f win32\vc-test.mak ALL DEBUG=1
nmake /f win32\vc-test.mak ALL DLL=1
nmake /f win32\vc-test.mak ALL DLL=1 DEBUG=1
This will create four new directories: TestStaticDebug, TestStaticRelease,
TestDllDebug, and TestDllRelease. Each of these folders will contain the
program "runner.exe," as well as any required DLLs.

2) Make sure a PostgreSQL database is running and accessible, and set up the
self-test programs included in the package.

Unix, Cygwin, or MSYS users simply type "make check" to build and run the
entire regression test. For Visual C++ users, the following steps should
accomplish the same:

1) Make sure a PostgreSQL database is running and accessible, and set up the
environment variables PGDATABASE, PGHOST, PGPORT, PGUSER and PGPASSWORD as
described in the libpqxx README.md file so the test program can connect
without needing to pass a connection string.

3) Run runner.exe from any of the test directories. When runner.exe runs,
2) Run `runner.exe` from any of the test directories. When runner.exe runs,
it executes each of the test programs in order. Some of the tests will
produce lots of output, some won't produce any. Error messages that are
expected in the course of a normal test run are prefixed with "(Expected)"
to show that they are not harmful. All tests should complete successfully.


Running the unit tests
----------------------

You may also want to compile and run the unit test programs included in the
package. The procedure for doing so for Visual Studio users is nearly
identical to the procedure for running the main test suite, except for the name
of the .mak file, which is `win32\vc-unit.mak`. The output build directories
are UnitStaticDebug, UnitStaticRelease, UnitDllDebug, and UnitDllRelease. The
test application name is again runner.exe. All of these tests should complete
successfully as well.


Setting Up a Visual Studio Project
----------------------------------

Here's how to set up a Visual C++ project file for your own program using
libpqxx (based on description by Alexandre Hanft, 2006-03-06):

1) Create a new project in the Visual C++ development environment.
2) Add your first C++ file and provide some initial code, e.g. by copying the
example from the libpqxx home page.
3) Edit Project Properties, C++: Additional Include Directories. Add the
location of the "include" directory found in your libpqxx source tree, e.g.
`C:\src\libpqxx\include` if you keep libpqxx in `C:\src\libpqxx`.
4) Edit Project Properties, Linker: Additional Library Directories. Add the
directory where your libpq and libpqxx libraries are, for example:
`C:\src\libpqxx\lib`
5) Edit Project Properties, Linker, Input: Additional Dependencies. Add:
libpqxx.lib.
That is for your Release build. Do the same for your Debug build, but
replace that "libpqxx.lib" in there with "libpqxxD.lib".
6) Your program should build successfully now. It may not be ready to run yet,
because some dynamically loaded libraries are needed when starting your
program. Copy the necessary libpq and libpqxx DLLs from the lib directory
in your libpqxx tree, directly into your project's build directory so the
system can find them when your development environment launches your
program.
7) Your program should now be able to run. However, you may need to tell it
how to connect to a database. If you set the environment variables
PGDATABASE, PGHOST, PGPORT, PGUSER and PGPASSWORD as described in the
libpqxx README.md file, your program should be able to connect without
passing further parameters.
8) Once your program gets to the point where users should be able to configure
it properly, change it to pass a connection string or URL where it connects
to a database, and include your user's configuration settings. A typical
connection string setting all parameters named above might look like:
"postgresql://[email protected]:5432/my_database"
9) For any other problems, please check the project homepage as listed in the
main libpqxx README.md file.


Getting Started with MinGW and MSYS
-----------------------------------

(Based on contribution by Michael J. Pedersen, 2004-08-17)

MSYS is a Unix-like environment for Windows. Once you have this installed,
building libpqxx should be a lot more like it is under Unix except that the
locations of libraries and such aren't sufficiently standardized.

Packages to download if you don't have them already:
1) MinGW (http://www.mingw.org/).
2) MSYS (http://www.mingw.org/).
3) w32api (http://www.mingw.org/).
4) PostgreSQL (http://www.postgresql.org/).
5) zlib (http://www.zlib.org/).

It is generally recommended to get the latest versions of these packages.

Compiling and installing PostgreSQL before you get to libpqxx:
1) Install MinGW (install to `c:\mingw`)
2) Install MSYS -- but not into the MinGW directory tree!
3) Run MSYS (Start -> Programs -> MinGW -> MSYS -> msys)
4) Extract, compile, and install zlib
# From the main source directory of zlib:
./configure --prefix=c:/mingw/local && make && make install
5) Extract, compile, and install postgres
# From the main source directory of PostgreSQL:
./configure --prefix=c:/mingw/local --with-includes=c:/mingw/local/include --with-libs=c:/mingw/local/lib
make && make install
6) Extract, compile, and install libpqxx
export lDFLAGS=-lws2_32
./configure --prefix=c:/mingw/local --enable-static
make && make install

If you don't have and don't want to install MSYS, you won't be able to perform
the "./configure" step. You can build libpqxx without it, but it takes a bit
more work and doesn't build the self-test. Use the special makefile MinGW.mak
in the win32 directory instead of the regular Makefile, and follow the
procedure described below to use the prefabricated configuration headers
enclosed in the source archive.


Building libpqxx without MSYS
-----------------------------

# (First set up configuration headers, see below)
export LDFLAGS=-lws2_32
make -f win32/MinGW.mak
# (Also install library, headers, and pkg-config on your system)

Having installed libpqxx, when compiling your own programs, use the following
steps (examples only here):

g++ -c -o myfile.o myfile.cpp `pkg-config libpqxx --cflags`
g++ -o myexec myfile.o `pkg-config libpqxx --libs` -lws2_32

Note that the linker step (g++ -o myexec) will give a spurious warning
about not knowing how to use the -R flag, but the executable will still
be generated, and work just fine.

The last argument to that linker step MUST be `-lws2_32`. Without it, the link
will provide errors about undefined references to select(). If it's not the
last argument, you will get the same results. Make sure it's there, and make
sure it's last. Trust me, you'll be happier.


Setting up the configuration headers
------------------------------------

Several headers, normally generated by the configure script, define certain
aspects of your compilation environment so that the library can work around
compiler shortcomings, functions missing in older libpq versions, etc. (Samples
for various compiler and libpq versions can be found in the subdirectory
config/sample-headers, so if you find you need to provide these headers
yourself, look there first.)

Each of the aspects mentioned below is represented by a configuration item -- a
preprocessor macro that is either #define'd to some value or not defined at
all. Most of the items are of a Boolean nature, i.e. some feature or
workaround is enabled if the corresponding macro is defined, or disabled if the
macro is left undefined. Note that defining these macros to anything at all,
even 0, means that the corresponding option is _enabled_.

At the time of writing, there are 2 of these configuration headers that you
need to concern yourself about, both of which should be created in the
include/pqxx subdirectory:

config-internal-compiler.h
config-public-compiler.h


The names contain two variables:

1. Internal or public. Configuration items that affect the compilation of
your client program are located in the config-public-*.h files (currently only
one file); ones that affect only the compilation of the library itself are kept
in the config-internal-*.h ones and are not included at all when compiling
client programs. Public configuration items are prefixed with PQXX_ to avoid
clashes with macros defined by other code.

2. Autotools-related, compiler-related, or libpq-related. The autotools items
are of no real interest, and the libpq section is currently empty, but the
compiler one is different. The compiler-related items describe features and
shortcomings of the compiler environment, such as the availability of
particular headers or definitions, or the ability to compile C++ language
constructs that aren't always available. The libpq items (none at the time of
writing) describe what features are available in the version of libpq you're
compiling against.

A complete list of configuration items and their categorizations can be found in
the configitems file. The normal configure script reads the list of items from
include/pqxx/config.h.in and writes them to include/pqxx/config.h, then splits
them up into the five smaller files as directed by the configitems database.

Again, sample versions of these headers for various environments can be found
in the config/sample-headers/ directory. Try copying the ones that most
resemble your own environment into include/pqxx/ and, if you have any problems
compiling with those, editing them by hand to enable or disable features that
appear to be giving you trouble.


Shared and Static Libraries, or .DLL vs. .LIB
---------------------------------------------

There are two ways to build the libpqxx library: as a shared library (known
in the Unix world as a Shared Object or "so," but in the Windows world as a
Dynamically Loaded Library or DLL) or as a static library (whose name would
end in ".a" on Unix systems but in ".LIB" on Windows systems). Linking your
own applications to these types of libraries is quite similar, except with a
DLL the system will also have to be able to find the library when your program
is loaded--not just when you are compiling it.

Unlike the situation in the Unix world, however, your choice on this point must
be known as you compile your application code. With libpqxx you do this by
defining the preprocessor macro PQXX_SHARED when compiling your code for use
with a libpqxx DLL. Leave this definition out if you intend to link to the
static version of the library.

(Internally, when compiling libpqxx, this variable will also be set according to
which kind of library is being built. It has a slightly different meaning in
that case, but this should really only matter to you if you are helping debug
the library)

Similarly, you may choose to link to either the static or the shared version of
libpq. The default is to use the dynamic library, which makes more sense there
because libpq's API and ABI are much simpler and more stable. To build a
libpqxx for use with a static libpq, however, define the preprocessor symbol
PQXX_PQ_STATIC both when compiling libpqxx and while building your own
application.


Troubleshooting: config headers
-------------------------------

The biggest typical problem for Windows/VC++ users is the need to edit the
configuration headers manually, resulting usually in compile errors, e.g. for
missing header files. Thus, if you get a compile error, the first places to
look are the config-*-*.h and config-*-*.h files in include/pqxx.

If you have to edit your configuration headers, please send us your results on
Github, so that headers corresponding to your environment can be included in
later libpqxx releases.

CAUTION: DO NOT try to unset yes/no configuration items by defining their macros
to zero. A value of zero counts as "yes." If a macro is defined at all, that
means "yes" (or "true," or "enabled" etc.) regardless of what actual value you
set. To disable an item, make sure it is not defined at all.


Troubleshooting: linking
------------------------

When you link your application to libpqxx on Windows, you may also need to link
to ws2_32.lib. On Visual C++, add these in the compiler user interface under:

Project Properties::Linker::Input::Additional Dependencies

We recommend that you specify libpqxx_static.lib and ws2_32.lib there, in that
order.

In MinGW, the problem may be that your MinGW environment does not inherit your
Windows `PATH` like it used to, and so `ws2_32.lib` is not in your path. Fix
it by updating your `PATH`, or tell MinGW to start off by copying the Windows
path, by setting `MSYS2_PATH_TYPE=inherit`.
3) Similarly, run `unit_runner.exe`.

0 comments on commit e51d180

Please sign in to comment.