README 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125
  1. Building via IDE Project Files
  2. ==============================
  3. This document describes how to compile, build and install curl and libcurl
  4. from sources using an IDE based development tool such as Visual Studio.
  5. Project files are currently available for Visual C++ v6.0 to v12.0. The
  6. following directory structure has been used to cater for this:
  7. somedirectory\
  8. |_curl
  9. |_projects
  10. |_<platform>
  11. |_<ide>
  12. |_lib
  13. |_src
  14. This structure allows for side-by-side compilation of curl on the same
  15. machine using different versions of a given compiler (for example VC8, VC9
  16. and VC10) and allows for your own application or product to be compiled
  17. against those variants of libcurl for example.
  18. Note: Typically this side-by-side compilation is generally only required
  19. when a library is being compiled against dynamic runtime libraries.
  20. Dependencies
  21. ============
  22. The projects files also support build configurations that require third
  23. party dependencies such as OpenSSL and SSH2. If you wish to support these,
  24. you will also need to download and compile those libraries as well.
  25. To support compilation of these libraries using different versions of
  26. compilers, the following directory structure has been used for both the
  27. output of curl and libcurl as well as these dependencies.
  28. somedirectory\
  29. |_curl
  30. | |_ build
  31. | |_<architecture>
  32. | |_<ide>
  33. | |_<configuration>
  34. | |_lib
  35. | |_src
  36. |
  37. |_openssl
  38. | |_ build
  39. | |_<architecture>
  40. | |_VC <version>
  41. | |_<configuration>
  42. |
  43. |_libssh2
  44. |_ build
  45. |_<architecture>
  46. |_VC <version>
  47. |_<configuration>
  48. As OpenSSL doesn't support side-by-side compilation when using different
  49. versions of Visual Studio a build helper batch file has been provided to
  50. assist with this. Please run "build-openssl -help" for usage details.
  51. Building with Visual C++
  52. ========================
  53. To build with VC++, you will of course have to first install VC++ which is
  54. part of Visual Studio.
  55. If you are building with VC6 then you will also need the February 2003
  56. Edition of the Windows Platform SDK which can be downloaded from:
  57. http://www.microsoft.com/en-us/download/details.aspx?id=12261
  58. If you require support for Internationalized Domain Names via Windows IDN
  59. then you will need either:
  60. * Microsoft Internationalized Domain Name (IDN) Mitigation APIs:
  61. http://www.microsoft.com/en-us/download/details.aspx?id=734
  62. * Microsoft Windows SDK Update for Windows Vista:
  63. http://www.microsoft.com/en-us/download/details.aspx?id=23719
  64. * Microsoft Visual Studio 2010 or above
  65. Once you have VC++ installed you should launch the application and open one
  66. of the solution or workspace files.
  67. Whilst files are provided for both libcurl and the curl command line tool as
  68. well as a configuration that includes both, it is recommend that you use the
  69. all-in-one configuration.
  70. Notes
  71. =====
  72. The following keywords have been used in the directory hierarchy:
  73. <platform> - The platform (For example: Windows)
  74. <ide> - The IDE (For example: VC6, VC10, BCC5)
  75. <architecture> - The platform architecture (For example: Win32, Win64)
  76. <configuration> - The target configuration (For example: DLL Debug,
  77. LIB Release - LIB OpenSSL)
  78. If you are using the source code from the git repository, rather than a
  79. release archive or nightly build, you will need to generate the project
  80. files. Please run "generate -help" for usage details.
  81. Should you wish to help out with some of the items on the TODO list, or
  82. find bugs in the project files that need correcting, and would like to
  83. submit updated files back then please note that, whilst the solution files
  84. can be edited directly, the templates for the project files (which are
  85. stored in the git repositoty) will need to be modified rather than the
  86. generated project files that Visual Studio uses.
  87. TODO
  88. ====
  89. These project files are a recent addition to the curl source code and as such
  90. are not 100% complete. This is a list of things that are still todo:
  91. * Support zlib
  92. * Use of static runtime libraries
  93. * Generate *.vcxproj.filters files for VC10, VC11 and VC12
  94. * Add the Test Suite components
  95. * Support for other development IDEs
  96. Any additional help would be appreciated ;-)