| 1 | /** |
|---|
| 2 | @page Installation Installation |
|---|
| 3 | |
|---|
| 4 | ENet should be trivially simple to integrate with most applications. |
|---|
| 5 | First, make sure you download the latest source distribution here @ref |
|---|
| 6 | SourceDistro. |
|---|
| 7 | |
|---|
| 8 | @section Unix Unix-like Operating Systems |
|---|
| 9 | |
|---|
| 10 | If you are using an ENet release, then you should simply be able to build it |
|---|
| 11 | by doing the following: |
|---|
| 12 | |
|---|
| 13 | ./configure && make && make install |
|---|
| 14 | |
|---|
| 15 | If you obtained the package from CVS, you must have automake and autoconf |
|---|
| 16 | available to generate the build system first by doing the following command |
|---|
| 17 | before using the above mentioned build procedure: |
|---|
| 18 | |
|---|
| 19 | autoreconf -vfi |
|---|
| 20 | |
|---|
| 21 | |
|---|
| 22 | @subsection SolarisBSD Solaris and BSD |
|---|
| 23 | |
|---|
| 24 | When building ENet under Solaris, you must specify the -lsocket and |
|---|
| 25 | -lnsl parameters to your compiler to ensure that the sockets library |
|---|
| 26 | is linked in. |
|---|
| 27 | |
|---|
| 28 | @section Windows Microsoft Windows |
|---|
| 29 | |
|---|
| 30 | There is an included MSVC 6 project (enet.dsp) which you may use to |
|---|
| 31 | build a suitable library file. Alternatively, you may simply drag all |
|---|
| 32 | the ENet source files into your main project. |
|---|
| 33 | |
|---|
| 34 | You will have to link to the Winsock2 libraries, so make sure to add |
|---|
| 35 | ws2_32.lib and winmm.lib to your library list (Project Settings | Link | |
|---|
| 36 | Object/library modules). |
|---|
| 37 | |
|---|
| 38 | @subsection enet.dsp Building with the included enet.dsp |
|---|
| 39 | |
|---|
| 40 | Load the included enet.dsp. MSVC may ask you to convert it if you |
|---|
| 41 | are on a newer version of MSVC - just allow the conversion and save |
|---|
| 42 | the resulting project as "enet" or similar. After you build this |
|---|
| 43 | project, it will output an "enet.lib" file to either the "Debug/" |
|---|
| 44 | or "Release/" directory, depending on which configuration you have |
|---|
| 45 | selected to build. By default, it should produce "Debug/enet.lib". |
|---|
| 46 | |
|---|
| 47 | You may then copy the resulting "enet.lib" file and the header files |
|---|
| 48 | found in the "include/" directory to your other projects and add it to |
|---|
| 49 | their library lists. Make sure to also link against "ws2_32.lib" and |
|---|
| 50 | "winmm.lib" as described above. |
|---|
| 51 | |
|---|
| 52 | @subsection DLL DLL |
|---|
| 53 | |
|---|
| 54 | If you wish to build ENet as a DLL you must first define ENET_DLL |
|---|
| 55 | within the project (Project Settings | C/C++ | Preprocessor | |
|---|
| 56 | Preprocessor definitions) or, more invasively, simply define ENET_DLL |
|---|
| 57 | at the top of enet.h. |
|---|
| 58 | |
|---|
| 59 | */ |
|---|
| 60 | |
|---|
