14.12.2014, 10:42
1) There's a small tutorial/guide here:
https://github.com/Zeex/sampgdk/wiki...GDK-with-CMake
which is also linked from this thread (large bold link at the top):
https://sampforum.blast.hk/showthread.php?tid=421090
Scripting discussion is probably not a very good place for this sort of questions, you'd have more attention in the official topic.
2) For a while there had been problems with running multiple sampgdk-based plugins simultaneously if one of them was statically linked with sampgdk (particularly with callbacks), but the shared version of the library worked fine so it was preferred.
Now there's not much diference between the two except maybe slightly lower memory usage and easier updates. If you use the shared library/DLL then an update to a newer version of sampgdk is simple - just replace the library and you're done (and new versions are backwards compatible), whereas with the static library or amalgamation all plugins have to be recompiled.
https://github.com/Zeex/sampgdk/wiki...GDK-with-CMake
which is also linked from this thread (large bold link at the top):
https://sampforum.blast.hk/showthread.php?tid=421090
Scripting discussion is probably not a very good place for this sort of questions, you'd have more attention in the official topic.
2) For a while there had been problems with running multiple sampgdk-based plugins simultaneously if one of them was statically linked with sampgdk (particularly with callbacks), but the shared version of the library worked fine so it was preferred.
Now there's not much diference between the two except maybe slightly lower memory usage and easier updates. If you use the shared library/DLL then an update to a newer version of sampgdk is simple - just replace the library and you're done (and new versions are backwards compatible), whereas with the static library or amalgamation all plugins have to be recompiled.