Please help me test the source code
-
The file is M0tah make of FLHOOK source code, I want to change it to my language, because I am a C++ noob, so every time when I try to recompile the source code, I always get error and can’t finish.
May anyone can help me that, you don’t need to modify anything, just compile the source code, and see will there be errors, if not, please tell my what kind of VC are you use, and help me inform how to set the compiler environment as well as the compilation step.
Grateful for your help.
-
Just saw your catchup PM. I don’t know how to compile Adoxa’s plugin.
But in this very topic…
The FLHook version you using is very old so as the C++ it uses.
When I try to compile it with VS2008 it gives me a plenty of C2679 errors, even more C4267, C4996 and ‘deprecated’ warings.
I used to work on this version of FLHook, You need get yourself a Visual C++ 2003 to compile it.
When you got it, open the ‘FLHook.vcproj’ in the project-vc7, then, it should build without error.
However, you better switch to lastest FLHook, which everybody working based on it.
-
Never mind about the “how to compile Adoxa’s plugin”, because I use the command line order:
nmake /nologoto recompile Adoxa’s plugin, and will successful compile without error.
But I’m not sure all of the Adoxa’s plugin can use above order to compile or not.
Another question is why my recompile of dll big then Adoxa’s?
I use the Microsoft Visual C++ 6.0 to do that, may anyone can teach me why?
-
I use VC6 (with SP6 and the apparently no longer available dinkumware fixes, along with the 2003 R2 SDK) for all my plugins. It may be the lack of the fixes that’s causing the increase in size.
It may be possible to build this FLHook with VC6, but you’re probably better off with either a newer Hook or a newer compiler (2003 would be ideal if you could get it, but I was able to compile it with 2008 SP1 Express - didn’t test it, though).
-
I think so - 2003 seems to be what that version of FLHook was compiled with (VC6 requires modification, as [c]_wtof[/c] is not even present; later compilers have lots of security warnings, which can be removed by a couple of defines). If you’re really wanting to compile this version, then obtaining 2003 would probably be the best way to do so. However, if you already have a later compiler, it would probably be better to make it work with that.
My plugins should work fine with your existing VC6; not sure if they’ll work with later compilers (I think most will, but a couple rely on VC6 internals, Console especially).
-
Yes, Adoxa, now I use the VS2003 to compile the 1.6.7 of FLHook, and it work fine without any compile warning.
About your tools, I use the command line compile tool to compile it, because I don’t know how to setup the VS2003 of environment variable to compile, so I download the VC++ command line compile tools to compile it, and use the```
nmake /nologoThanks for your hardwork to share those amazing tools for us, hope I can learn the VC++ form the FLHook code, and try to make some function for the game.
