[BAILOPAN]

Oh, metamod.org doesn't have the changes

Don't use metamodx source from the CVS because I added volalite things to it.

Just wait for the next metamod update. You shouldn't need to compile metamod.

[Girthesniper]

How do you know they haven't secretley quit on MetaMod.org?

This sucks i was compiling meta like 3 weeks ago with your help now i cant figure it out again. Anyway you can help a geek out? I tried the X2 code and VS doesnt like the project files at all. My whole world just died right when I thoug I was getting the hang of things.

I compiled AMXX just fine. I get it I think you have a jacked debug meta on CSV not ready for the moron to come try to compile. I compile all dll for my self so its optimized for my machine. When will meta be ready for standard compiling X4?

[BAILOPAN]

The reason you are getting those errors is because the engine interface does not match.

Change all instances of the long datatype to "int". Then change EngineFPrintf from FILE *fp to void *fp

Sorry to drag this.... but, when you update your source and the engine interfaces properly will you release all source so we can compile amxx, meta and other modules like the old days? Is the engine dif due to amxx 0.2 dev work?

[QwertyAccess]

why bother asking of course hes going to release it

I guess I meant will the source be released for MetamodX that will compile properly. I am a bit of a nub when it comes to this so read my shit slow and careful then it may make sense

[devicenull]

So, exactly what other directories do I need included?
I have
hlsdk\SourceCode\common
hlsdk\SourceCode\dlls
hlsdk\SourceCode\engine
hlsdk\SourceCode\game_shared
hlsdk\SourceCode\pm_shared
amxmodx\amxmodx
amxmodx\engine
amxmodx\sc
amxmodx\amxmodx\sdk
"C:\Program Files\Microsoft SDK\include" //This is where the Windown SDK is
metamodx\metamodx
"C:\Program Files\Microsoft Visual C++ Toolkit 2003\include" //standard includes for the compiler

Which of those do I need, do I need any others?

I then use
cl /EHsc /LD /I%INCLUDE% amxmodx.cpp
Compiler flags: Use NT based stuff, compile to a dll, and include everything above
to compile.. compiling finishes fine, linking fails
This is using the compiler/linker from VS without VS..
the entire batch file to compile is

@echo off

Set PATH=C:\Program Files\Microsoft Visual C++ Toolkit 2003\bin;%PATH%
Set INCLUDE=%INCLUDE%;C:\source\metamodx\hlsdk\SourceCode\common;C:\source\metamodx\hlsdk\SourceCode\dlls
Set INCLUDE=%INCLUDE%;C:\source\metamodx\hlsdk\SourceCode\engine;C:\source\metamodx\hlsdk\SourceCode\game_shared;C:\source\metamodx\hlsdk\SourceCode\pm_shared
Set INCLUDE=%INCLUDE%;C:\Source\amxmodx\amxmodx;C:\amxmodx\amxmodx\engine;C:\Source\amxmodx\amxmodx\sdk
Set INCLUDE=%INCLUDE%;"C:\Program Files\Microsoft SDK\include"
Set INCLUDE=%INCLUDE%;C:\Source\metamodx\metamodx;C:\Source\amxmodx\sc;"C:\Program Files\Microsoft Visual C++ Toolkit 2003\include"
Set LIB=C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib;%LIB%

cd amxmodx
cl /EHsc /LD /I%INCLUDE% amxmodx.cpp
Pause

Anything I should try?
I get errors like this

amxmodx.obj : error LNK2019: unresolved external symbol _amx_Release referenced in function "long __cdecl callfunc_end(struct tagAMX *,long *)" (?callfunc_end@@YAJPAUtagAMX@@PAJ@Z)

Would post this elsewhere.. but noone in the other forums have a clue as to using anything other then small

[BAILOPAN]

Use the flags we use in the vcproj file