.....................................465 16.1. Building with Visual C++ or the Microsoft Windows SDK........................................465 16.1.1. Requirements ................................. of the configure script varying depending on which 459 Chapter 15. Installation from Source Code SDK version was used during configure. That shouldn’t pose any problem in simple scenarios, but if you PG_SYSROOT=/desired/path all To find out the appropriate path on your machine, run xcodebuild -version -sdk macosx Path Note that building an extension using a different sysroot version than was used to build

.....................................438 16.1. Building with Visual C++ or the Microsoft Windows SDK.................................438 16.1.1. Requirements ........................................ system header files. This results in the outputs of the configure script varying depending on which SDK version was used during configure. That shouldn’t pose any problem in simple scenarios, but if you PG_SYSROOT=/desired/path all To find out the appropriate path on your machine, run xcodebuild -version -sdk macosx Path Note that building an extension using a different sysroot version than was used to build

.....................................460 16.1. Building with Visual C++ or the Microsoft Windows SDK.................................460 16.1.1. Requirements ........................................ system header files. This results in the outputs of the configure script varying depending on which SDK version was used during configure. That shouldn’t pose any problem in simple scenarios, but if you PG_SYSROOT=/desired/path all To find out the appropriate path on your machine, run xcrun --show-sdk-path Note that building an extension using a different sysroot version than was used to build the

.....................................487 16.1. Building with Visual C++ or the Microsoft Windows SDK........................................487 16.1.1. Requirements ................................. system header files. This results in the outputs of the configure script varying depending on which SDK version was used during configure. That shouldn’t pose any problem in simple scenarios, but if you PG_SYSROOT=/desired/path all To find out the appropriate path on your machine, run xcrun --show-sdk-path Note that building an extension using a different sysroot version than was used to build the

..................................... 505 17.1. Building with Visual C++ or the Microsoft Windows SDK .............................. 505 18. Server Setup and Operation ................................ ..................................... 505 17.1. Building with Visual C++ or the Microsoft Windows SDK ..................................... 505 17.1.1. Requirements ................................... system header files. This results in the outputs of the configure script varying depending on which SDK version was used during configure. That shouldn't pose any problem in simple scenarios, but if you

..................................... 480 17.1. Building with Visual C++ or the Microsoft Windows SDK ........................ 480 18. Server Setup and Operation ...................................... ..................................... 480 17.1. Building with Visual C++ or the Microsoft Windows SDK ................................ 480 17.1.1. Requirements ........................................ system header files. This results in the outputs of the configure script varying depending on which SDK version was used during configure. That shouldn't pose any problem in simple scenarios, but if you

.....................................512 17.1. Building with Visual C++ or the Microsoft Windows SDK........................................512 17.1.1. Requirements ................................. system header files. This results in the outputs of the configure script varying depending on which SDK version was used during configure. That shouldn’t pose any problem in simple scenarios, but if you PG_SYSROOT=/desired/path all To find out the appropriate path on your machine, run xcrun --show-sdk-path Note that building an extension using a different sysroot version than was used to build the

.....................................484 17.1. Building with Visual C++ or the Microsoft Windows SDK.................................484 17.1.1. Requirements ........................................ system header files. This results in the outputs of the configure script varying depending on which SDK version was used during configure. That shouldn’t pose any problem in simple scenarios, but if you PG_SYSROOT=/desired/path all To find out the appropriate path on your machine, run xcrun --show-sdk-path Note that building an extension using a different sysroot version than was used to build the

..............................................395 16.1. Building with Visual C++ or the Platform SDK .........................................................395 16.1.1. Requirements ............... Microsoft Platform SDK and use the included compiler. It is also possible to build with the full Microsoft Visual C++ 2005 or 2008. In some cases that requires the installation of the Platform SDK in addition Platform SDK PostgreSQL can be built using the Visual C++ compiler suite from Microsoft. These compilers can be either from Visual Studio, Visual Studio Express or some versions of the Platform SDK. If you

..............................................369 16.1. Building with Visual C++ or the Platform SDK ..................................................369 16.1.1. Requirements ...................... Microsoft Platform SDK and use the included compiler. It is also possible to build with the full Microsoft Visual C++ 2005 or 2008. In some cases that requires the installation of the Platform SDK in addition Platform SDK PostgreSQL can be built using the Visual C++ compiler suite from Microsoft. These compilers can be either from Visual Studio, Visual Studio Express or some versions of the Platform SDK. If you