PageRenderTime 58ms CodeModel.GetById 25ms RepoModel.GetById 0ms app.codeStats 0ms

/docs/gem.pg-0.13.1/files/README-Windows_rdoc.html

https://github.com/toy/rb
HTML | 139 lines | 114 code | 25 blank | 0 comment | 0 complexity | a7e4c27460942757de8fbedc7eabd357 MD5 | raw file
    

  1. <?xml version="1.0" encoding="utf-8"?>
    2. 

  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    3. 

  3.     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    4. 

  4. <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
    5. 

  5. <head>
    6. 

  6.     <title>README-Windows.rdoc</title>
    7. 

  7.     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    8. 

  8.     <link rel="stylesheet" href="../css/reset.css" type="text/css" media="screen" />
    9. 

  9.     <link rel="stylesheet" href="../css/main.css" type="text/css" media="screen" />
    10. 

  10.     <script src="../js/jquery-1.3.2.min.js" type="text/javascript" charset="utf-8"></script>
    11. 

  11.     <script src="../js/jquery-effect.js" type="text/javascript" charset="utf-8"></script>
    12. 

  12.     <script src="../js/main.js" type="text/javascript" charset="utf-8"></script>
    13. 

  13. </head>
    14. 

  14. 

  15. <body>     
    16. 

  16.     <div class="banner">
    17. 

  17.         <h1>
    18. 

  18.             README-Windows.rdoc
    19. 

  19.         </h1>
    20. 

  20.         <ul class="files">
    21. 

  21.             <li>README-Windows.rdoc</li>
    22. 

  22.             <li>Last modified: Mon Feb 13 07:34:43 +0100 2012</li>
    23. 

  23.         </ul>
    24. 

  24.     </div>
    25. 

  25. 

  26.     <div id="bodyContent">
    27. 

  27.         <div id="content">
    28. 

  28.     
    29. 

  29.     <div class="description">
    30. 

  30.         <h1>Compiling &#8216;pg&#8217; on MS Windows</h1>
    31. 

  31. <p>
    32. 

  32. In order to build this extension on MS Windows you will need a couple
    33. 

  33. things.
    34. 

  34. </p>
    35. 

  35. <p>
    36. 

  36. First, a compiler. For the one click installer this means you should either
    37. 

  37. use VC++ 6.0 or the compiler that comes with cygwin or mingw if
    38. 

  38. you&#8217;re building on that platform.
    39. 

  39. </p>
    40. 

  40. <p>
    41. 

  41. If you&#8217;ve built Ruby yourself, you should use the same compiler to
    42. 

  42. build this library that you used to build Ruby.
    43. 

  43. </p>
    44. 

  44. <p>
    45. 

  45. Second, PostgreSQL. Be sure you installed it with the development header
    46. 

  46. files if you installed it using the standard PostgreSQL installer for
    47. 

  47. Windows. If you didn&#8217;t, you can run the installer again, select
    48. 

  48. &#8220;modify&#8221;, and then select the &#8216;development headers&#8217;
    49. 

  49. option to install them.
    50. 

  50. </p>
    51. 

  51. <p>
    52. 

  52. I recommend making sure that &#8216;pg_config.exe&#8217; is in your PATH.
    53. 

  53. The PostgreSQL installer for Windows does not necessarily update your PATH
    54. 

  54. when it installs itself, so you may need to do this manually. This
    55. 

  55. isn&#8217;t strictly necessary, however.
    56. 

  56. </p>
    57. 

  57. <p>
    58. 

  58. In order to build ruby-pg, just run &#8216;rake&#8217;. If the
    59. 

  59. pg_config.exe executable is not in your PATH, you&#8217;ll need to
    60. 

  60. explicitly point ruby-pg to where your PostgreSQL headers and libraries are
    61. 

  61. with something like this:
    62. 

  62. </p>
    63. 

  63. <pre>
    64. 

  64.         rake --with-pg-dir=c:/progra~1/postgr~1/8.3
    65. 

  65. </pre>
    66. 

  66. <p>
    67. 

  67. Adjust your path accordingly. BE SURE TO USE THE SHORT PATH NAMES! If you
    68. 

  68. try to use a path with spaces in it, the nmake.exe program will choke.
    69. 

  69. </p>
    70. 

  70. <h2>Cross compiling for mswin32</h2>
    71. 

  71. <p>
    72. 

  72. Using rake-compiler a cross compiled pg gem can be build on a Linux or
    73. 

  73. MacOS X host for the win32 platform. The generated gem is statically linked
    74. 

  74. against libpq and libssl. OpenSSL and PostgreSQL are downloaded and
    75. 

  75. compiled from the sources. There are no runtime dependencies to any but the
    76. 

  76. standard Windows DLLs.
    77. 

  77. </p>
    78. 

  78. <p>
    79. 

  79. Install mingw32 using the instructions in rake-compiler&#8217;s README. For
    80. 

  80. Debian/Ubuntu it is <tt>apt-get install gcc-mingw32</tt> . Use ruby-1.8.7
    81. 

  81. for the following commands.
    82. 

  82. </p>
    83. 

  83. <p>
    84. 

  84. Download and cross compile ruby 1.8 and 1.9 for win32 with:
    85. 

  85. </p>
    86. 

  86. <pre>
    87. 

  87.         rake-compiler cross-ruby VERSION=1.8.7-p352
    88. 

  88.         rake-compiler cross-ruby VERSION=1.9.2-p290
    89. 

  89. </pre>
    90. 

  90. <p>
    91. 

  91. Download and cross compile pg for win32:
    92. 

  92. </p>
    93. 

  93. <pre>
    94. 

  94.         rake cross native gem
    95. 

  95. </pre>
    96. 

  96. <p>
    97. 

  97. or with custom versions:
    98. 

  98. </p>
    99. 

  99. <pre>
    100. 

  100.         rake cross native gem RUBY_CC_VERSION=1.8.7:1.9.2 \
    101. 

  101.             OPENSSL_VERSION=1.0.0e POSTGRESQL_VERSION=9.1.1
    102. 

  102. </pre>
    103. 

  103. <p>
    104. 

  104. If everything works, there should be pg-VERSION-x86-mingw32.gem in the pkg
    105. 

  105. directory.
    106. 

  106. </p>
    107. 

  107. <h2>Reporting Problems</h2>
    108. 

  108. <p>
    109. 

  109. If you have any problems you can submit them via [the project&#8217;s
    110. 

  110. issue-tracker][bitbucket]. And submit questions, problems, or solutions, so
    111. 

  111. that it can be improved.
    112. 

  112. </p>
    113. 

  113. 

  114.     </div>
    115. 

  115.     
    116. 

  116. 

  117.     
    118. 

  118. 

  119.     
    120. 

  120.     
    121. 

  121. 

  122.     
    123. 

  123.     
    124. 

  124. 

  125.     
    126. 

  126. 

  127.     
    128. 

  128. 

  129.     
    130. 

  130. 

  131.     
    132. 

  132. 

  133.     
    134. 

  134. 

  135.     
    136. 

  136. </div>
    137. 

  137.     </div>
    138. 

  138.   </body>
    139. 

  139. </html>
    140.