To utilize GNS, you must perform two tasks:
To build the client library from within MSVC6, go to File => Open Workspace, change your filter to "Projects (.dsp)" and open gns.dsp from the GNS folder.
The project is configured to build gnsD.dll and gnsD.lib in debug mode, and gns.lib and gns.dll in release mode. Just go to Build => Batch Build... and then click on Build.
This will create the GNS library files in your Debug and Release folders.
To build the client library from within .NET 2003, go to File => Open Solution, and open gns.sln from the GNS folder.
The project is configured to build gnsD.dll and gnsD.lib in debug mode, and gns.lib and gns.dll in release mode. Just go to Build => Batch Build... and then click on Select All then Build.
This will create the GNS library files in your Debug and Release folders.
There is currently no makefile for creating the gns library itself. The only makefile included in gns-0.2.tar.gz is that to create the GNS server. In order to at least decompress the source package onto your system, type the following in the directory where you downloaded your GNS distribution:
% tar xvfz gns-0.1.tar.gz
This will create a new subdirectory, and decompress the package contents into it.
From there, you may either create a library, or, include the source files listed in section one into an existing project.
The GNS library comes with a makefile (gns.mak) that you can use to create a project or an environment to compile in.
To build the server from within MSVC6, go to File => Open Workspace, change your filter to "Projects (.dsp)" and open gnsServe.dsp from the gnsServe subdirectory of the GNS folder.
The project is configured to build gnsServe.exe in debug mode and release mode. Just go to Build => Batch Build... and then click on Build.
This will create the GNS server in your Debug and Release folders.
To build the the GNS server from within .NET 2003, go to File => Open Solution, and open gnsServe.sln from the gnsServe subdirectory of the GNS folder.
The project is configured to build gnsServe.exe in debug mode and release mode. Just go to Build => Batch Build... and then click on Select All then Build.
This will create the GNS server in your Debug and Release folders.
In order to compile and install the GNS server on your system, type the following in the directory where you downloaded your GNS distribution:
% tar xvfz gns-0.1.tar.gz
This will create a new subdirectory, and decompress the package contents into it. Change your working directory to the base directory of the GNS distribution and build a GNS server by entering the following commands:
% cd gns-0.2
% ./configure
% make
% make install
Since GNS uses autoconf, you should have not trouble compiling it.
The GNS server comes with a makefile (gnsServe.mak) that you can use to create a project or an environment to compile in.
Once the GNS library and GNS server are build, you are ready to build a test client.
To build the server from within MSVC6, go to File => Open Workspace, change your filter to "Projects (.dsp)" and open gnsTest.dsp from the gnsServe subdirectory of the GNS folder.
The project is configured to build gnsServe.exe in debug mode and release mode. Just go to Build => Batch Build... and then click on Build.
This will create the GNS test program in your Debug and Release folders.
To build the the GNS server from within .NET 2003, go to File => Open Solution, and open gnsTest.sln from the gnsTest subdirectory of the GNS folder.
The project is configured to build gnsTest.exe in debug mode and release mode. Just go to Build => Batch Build... and then click on Select All then Build.
This will create the GNS test program in your Debug and Release folders.
The GNS test program comes with a makefile (gnsTest.mak) that you can use to create a project or an environment to compile in a Microsoft Windows environment only.
From MSVC6, go to Tools => Options. Change the settings dropdown at the top to All Configurations. Then, click on the C++ tab, and set the category to Preprocessor. This will bring up the Additional Include Directories field. Add the full path to the GNS include folder in that field.
Then, click on the Link tab at the top of the options window, and change the category to Input. This will bring up the Additional Library Path field. Add the full path to the GNS library folder in that field.
Next, change your settings dropdown to Win32 Debug. While still in the Input category, make sure gnsD.lib is in the Object / Library Modules field.
Next, change your settings dropdown to Win32 Release. While still in the Input category, make sure gns.lib is in the Object / Library Modules field.
Finally, click OK. Now your project is configured to build with the GNS library.
From .NET, go to Project => Properties.
Change your Configuration dropdown to All Configurations. Then expand the C/C++ tree and click on General. In the Additional Include Directories field, make sure you have the full path to the Include folder in your GNS folder.
Next, expand the Linker tree and click on General. In the Additional Library Directories field, make sure you have the full path to the Lib folder in your GNS folder.
Next, change your Configuration dropdown to Win32 Debug. While still in the Linker tree, click on Input. Make sure gnsD.lib is there.
Finally, change your Configuration dropdown to Win32 Release. While still in the Linker tree, make sure gns.lib is under the Input section.
Finally, click OK. Now your project is configured to build with the GNS library.
Once you have built the GNS server, all that's left to do before running it is to make sure that the file gns.conf is in the working directory that your debugger points to. If you are not using a debugger, just copy gnsServe.exe and gns.conf into the same directory, and run gnsServe.exe.
gns.conf is the configuration file that the GNS server reads from on startup. An example configuration file is included with the GNS package which you may use for testing. Information on configuring the file may be found in section three.
When you start the server, a console window will appear, which looks like
This means the server is up and running on your computer. If you do not see this text, it may be because the server was not able to open gns.conf.
The GNS package includes a test application called gnsTest. Once your server is running, you may run gnsTest.exe to test the capabilities of your server.
When the light on the corner is red, that means you are disconnected from your server. When the light is green, it means you are connected. The light will be red most of the time in some tabs, but be peristently green in other tabs where you have a dedicated connection to the server, such as a chat room.
There is a sample plug-in available in the plug-ins section of the GNS website at http://www.gamieon.com/gns called gnsMySQL. Instructions on building and implementing plug-ins may be found in that package, which is available on the website. Once a plug-in is built, it must be put in the working directory where the server is running from, and the following command must be in gns.conf in order for the server to load the plug-in:
loadplugin my_plugin_name plugin_filename
Please refer to Section 3.2.9 for details on the syntax of loading plug-ins from the GNS server.
Should you run into any problems, please report them to support@gamieon.com