|
34 | 34 | <productname>Windows</productname>.
|
35 | 35 | </para>
|
36 | 36 |
|
37 |
| - <para> |
38 |
| - Finally, the client access library |
39 |
| - (<application>libpq</application>) can be built using |
40 |
| - <productname>Visual C++ 7.1</productname> or |
41 |
| - <productname>Borland C++</productname> for compatibility with statically |
42 |
| - linked applications built using these tools. |
43 |
| - </para> |
44 |
| - |
45 | 37 | <para>
|
46 | 38 | Building using <productname>MinGW</productname> or
|
47 | 39 | <productname>Cygwin</productname> uses the normal build system, see
|
@@ -539,113 +531,4 @@ $ENV{DOCROOT}='c:\docbook';
|
539 | 531 | </sect2>
|
540 | 532 |
|
541 | 533 | </sect1>
|
542 |
| - |
543 |
| - <sect1 id="install-windows-libpq"> |
544 |
| - <title>Building <application>libpq</application> with |
545 |
| - <productname>Visual C++</productname> or |
546 |
| - <productname>Borland C++</productname></title> |
547 |
| - |
548 |
| - <para> |
549 |
| - Using <productname>Visual C++ 7.1-9.0</productname> or |
550 |
| - <productname>Borland C++</productname> to build libpq is only recommended |
551 |
| - if you need a version with different debug/release flags, or if you need a |
552 |
| - static library to link into an application. For normal use the |
553 |
| - <productname>MinGW</productname> or |
554 |
| - <productname>Visual Studio</productname> or |
555 |
| - <productname>Windows SDK</productname> method is recommended. |
556 |
| - </para> |
557 |
| - |
558 |
| - <para> |
559 |
| - To build the <application>libpq</application> client library using |
560 |
| - <productname>Visual Studio 7.1 or later</productname>, change into the |
561 |
| - <filename>src</filename> directory and type the command: |
562 |
| -<screen> |
563 |
| -<userinput>nmake /f win32.mak</userinput> |
564 |
| -</screen> |
565 |
| - </para> |
566 |
| - <para> |
567 |
| - To build a 64-bit version of the <application>libpq</application> |
568 |
| - client library using <productname>Visual Studio 8.0 or |
569 |
| - later</productname>, change into the <filename>src</filename> |
570 |
| - directory and type in the command: |
571 |
| -<screen> |
572 |
| -<userinput>nmake /f win32.mak CPU=AMD64</userinput> |
573 |
| -</screen> |
574 |
| - See the <filename>win32.mak</filename> file for further details |
575 |
| - about supported variables. |
576 |
| - </para> |
577 |
| - |
578 |
| - <para> |
579 |
| - To build the <application>libpq</application> client library using |
580 |
| - <productname>Borland C++</productname>, change into the |
581 |
| - <filename>src</filename> directory and type the command: |
582 |
| -<screen> |
583 |
| -<userinput>make -N -DCFG=Release /f bcc32.mak</userinput> |
584 |
| -</screen> |
585 |
| - </para> |
586 |
| - |
587 |
| - <sect2> |
588 |
| - <title>Generated Files</title> |
589 |
| - <para> |
590 |
| - The following files will be built: |
591 |
| - |
592 |
| - <variablelist> |
593 |
| - <varlistentry> |
594 |
| - <term><filename>interfaces\libpq\Release\libpq.dll</filename></term> |
595 |
| - <listitem> |
596 |
| - <para> |
597 |
| - The dynamically linkable frontend library |
598 |
| - </para> |
599 |
| - </listitem> |
600 |
| - </varlistentry> |
601 |
| - |
602 |
| - <varlistentry> |
603 |
| - <term><filename>interfaces\libpq\Release\libpqdll.lib</filename></term> |
604 |
| - <listitem> |
605 |
| - <para> |
606 |
| - Import library to link your programs to <filename>libpq.dll</filename> |
607 |
| - </para> |
608 |
| - </listitem> |
609 |
| - </varlistentry> |
610 |
| - |
611 |
| - <varlistentry> |
612 |
| - <term><filename>interfaces\libpq\Release\libpq.lib</filename></term> |
613 |
| - <listitem> |
614 |
| - <para> |
615 |
| - Static version of the frontend library |
616 |
| - </para> |
617 |
| - </listitem> |
618 |
| - </varlistentry> |
619 |
| - |
620 |
| - </variablelist> |
621 |
| - </para> |
622 |
| - |
623 |
| - <para> |
624 |
| - Normally you do not need to install any of the client files. You should |
625 |
| - place the <filename>libpq.dll</filename> file in the same directory |
626 |
| - as your applications executable file. Do not install |
627 |
| - <filename>libpq.dll</filename> into your <filename>Windows</>, |
628 |
| - <filename>System</> or <filename>System32</> directory unless |
629 |
| - absolutely necessary. |
630 |
| - If this file is installed using a setup program, then it should |
631 |
| - be installed with version checking using the |
632 |
| - <symbol>VERSIONINFO</symbol> resource included in the file, to |
633 |
| - ensure that a newer version of the library is not overwritten. |
634 |
| - </para> |
635 |
| - |
636 |
| - <para> |
637 |
| - If you are planning to do development using <application>libpq</application> |
638 |
| - on this machine, you will have to add the |
639 |
| - <filename>src\include</filename> and |
640 |
| - <filename>src\interfaces\libpq</filename> subdirectories of the source |
641 |
| - tree to the include path in your compiler's settings. |
642 |
| - </para> |
643 |
| - |
644 |
| - <para> |
645 |
| - To use the library, you must add the |
646 |
| - <filename>libpqdll.lib</filename> file to your project. (In Visual |
647 |
| - C++, just right-click on the project and choose to add it.) |
648 |
| - </para> |
649 |
| - </sect2> |
650 |
| - </sect1> |
651 | 534 | </chapter>
|
0 commit comments