>From what I was reading in the docs the ".dll" is added to the
"plugin" name when it trys to find the dll to load.
so for..
"Plugin
{
"file" "myplugin"
}
I will look to load myplugin.dll
On Thu, 9 Dec 2004 04:57:52 -0500 (EST), Neal Tibrewala wrote:
> I've compiled the serverplugin_empty file under linux (finally).
>
> I called the binary 'plugin_i486.so' and placed it into the bin/
> directory
> I created a file in cstrike/addons/plugin.vdf that contains:
>
> "Plugin"
> {
> "file" "plugin"
> }
>
> When I load the dedicated server all I get is a message:
>
> Unable to load plugin "plugin"
>
> Is there any way to find out why it's having trouble, or geta more
> useful
> error message (-debug doesn't help and it doesn't produce a
> debug.log
> file)? is it finding the binary? Is there a problem with how it
> was
> compiled? The resulting flattened link line is:
>
> g++ -o plugin_i486.so -shared -Wl,-Map,plugin_i486.so_map.txt -Wl
> plugin_convar.o plugin.o convar.o interface.o KeyValues.o
> utlbuffer.o
> memoverride.o /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/libstdc++.a
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/libgcc_eh.a
>
> Thanks.
>
> - Neal
>
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list
> archives, please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlcoders
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
