2004-10-20 10:17:51 -07:00
|
|
|
/**
|
|
|
|
|
@page Installation Installation
|
|
|
|
|
|
|
|
|
|
ENet should be trivially simple to integrate with most applications.
|
|
|
|
|
First, make sure you download the latest source distribution here @ref
|
|
|
|
|
SourceDistro.
|
|
|
|
|
|
|
|
|
|
@section Unix Unix-like Operating Systems
|
|
|
|
|
|
2007-10-09 16:22:45 -07:00
|
|
|
If you are using an ENet release, then you should simply be able to build it
|
|
|
|
|
by doing the following:
|
|
|
|
|
|
|
|
|
|
./configure && make && make install
|
|
|
|
|
|
|
|
|
|
If you obtained the package from CVS, you must have automake and autoconf
|
|
|
|
|
available to generate the build system first by doing the following command
|
|
|
|
|
before using the above mentioned build procedure:
|
|
|
|
|
|
|
|
|
|
aclocal && automake -a -c --foreign && autoconf
|
|
|
|
|
|
2004-10-20 10:17:51 -07:00
|
|
|
|
|
|
|
|
@subsection SolarisBSD Solaris and BSD
|
|
|
|
|
|
|
|
|
|
When building ENet under Solaris, you must specify the -lsocket and
|
|
|
|
|
-lnsl parameters to your compiler to ensure that the sockets library
|
|
|
|
|
is linked in.
|
|
|
|
|
|
|
|
|
|
@section Windows Microsoft Windows
|
|
|
|
|
|
2007-10-09 16:22:45 -07:00
|
|
|
There is an included MSVC 6 project (enet.dsp) which you may use to
|
|
|
|
|
build a suitable library file. Alternatively, you may simply drag all
|
|
|
|
|
the ENet source files into your main project.
|
2004-10-20 10:17:51 -07:00
|
|
|
|
|
|
|
|
You will have to link to the Winsock2 libraries, so make sure to add
|
|
|
|
|
ws2_32.lib to your library list (Project Settings | Link |
|
|
|
|
|
Object/library modules).
|
|
|
|
|
|
2007-10-09 16:22:45 -07:00
|
|
|
@subsection enet.dsp Building with the included enet.dsp
|
|
|
|
|
|
|
|
|
|
Load the included enet.dsp. MSVC may ask you to convert it if you
|
|
|
|
|
are on a newer version of MSVC - just allow the conversion and save
|
|
|
|
|
the resulting project as "enet" or similar. After you build this
|
|
|
|
|
project, it will output an "enet.lib" file to either the "Debug/"
|
|
|
|
|
or "Release/" directory, depending on which configuration you have
|
|
|
|
|
selected to build. By default, it should produce "Debug/enet.lib".
|
|
|
|
|
|
|
|
|
|
You may then copy the resulting "enet.lib" file and the header files
|
|
|
|
|
found in the "include/" directory to your other projects and add it to
|
|
|
|
|
their library lists. Make sure to also link against "ws2_32.lib" as
|
|
|
|
|
described above.
|
|
|
|
|
|
2004-10-20 10:17:51 -07:00
|
|
|
@subsection DLL DLL
|
|
|
|
|
|
|
|
|
|
If you wish to build ENet as a DLL you must first define ENET_DLL
|
|
|
|
|
within the project (Project Settings | C/C++ | Preprocessor |
|
|
|
|
|
Preprocessor definitions) or, more invasively, simply define ENET_DLL
|
|
|
|
|
at the top of enet.h.
|
|
|
|
|
|
|
|
|
|
*/
|
|
|
|
|
|
