[LumiStance]

Any recommendation for the VM?
Does the Debian version matter if you don't distribute plugins?
I was attempting on a server with squeeze/sid.

How dependent is win32 on visual studio (may not be an option in the future)?
Is Code Blocks or a non IDE possible?

[Zephyrus]

Originally Posted by LumiStance Any recommendation for the VM? Does the Debian version matter if you don't distribute plugins? I was attempting on a server with squeeze/sid. How dependent is win32 on visual studio (may not be an option in the future)? Is Code Blocks or a non IDE possible?

if you plan to use the latest debian then its okay to use debian 6 for compile too, but you cant use a binary compiled on debian 6 on debian 5 unless you made some ELF changes to the binary, which wouldnt speed up development on linux at all, but im also not sure about the GCC version if its backward-compatible with the debian 5 one

not sure, maybe if you make your own project file for those then it would work, tbh i havent tried but if you dont plan to distribute why dont you just use visual studio express? its free for non-commercial use

[asherkin]

Originally Posted by LumiStance How dependent is win32 on visual studio (may not be an option in the future)? Is Code Blocks or a non IDE possible?

You have to use a compiler that is ABI-compatible with MSVC, which is only MSVC.

[psychonic]

Code::Blocks can use the msvc compiler on Windows.

[Old and Slow]

Originally Posted by LumiStance What is your procedure for recreating your build environment on a clean install of your OS? And when is the last time you actually used that procedure? When is the last time anyone verified that stub_mm and sample_mm still compile?

I did all that this afternoon - new SDKs, new server, compiled the MM:S plugins.
See the attached text file - it's just for Linux at the moment, may look at Windoze next.

[API]

Originally Posted by Old and Slow I did all that this afternoon - new SDKs, new server, compiled the MM:S plugins. See the attached text file - it's just for Linux at the moment, may look at Windoze next.

Dude, you rock! We should pin this / put it in a Wiki somewhere.

[Powerlord]

Originally Posted by pimpinjuice Dude, you rock! We should pin this / put it in a Wiki somewhere.

I'll be honest, these directions (except for the VDF files) are almost identical to how you compile SourceMod extensions... right down to the ENGINE= and DEBUG= arguments in the make line.

[LumiStance]

Thanks for the info everybody. The online documentation is not exactly thorough on the requirements.

Originally Posted by Old and Slow I did all that this afternoon - new SDKs, new server, compiled the MM:S plugins. See the attached text file - it's just for Linux at the moment, may look at Windoze next.

You are awesome! Thanks.

When I get a change to walk through this, I'll make any needed changes to the wiki.

[LumiStance]

Originally Posted by Old and Slow Also in the Makefile, the following to minimize the compile messages: line 142, add the @ at the front of each line: @$(CPP) $(INCLUDE) $(CFLAGS) -o $@ -c $< also lines 145-147: @mkdir -p $(BIN_DIR) @ln -sf $(HL2LIB)/$(LIB_PREFIX)vstdlib$(LIB_SUFFIX) @ln -sf $(HL2LIB)/$(LIB_PREFIX)tier0$(LIB_SUFFIX) and line 151: @if [ "$(ENGSET)" = "false" ]; then \ and line 158: @$(CPP) $(INCLUDE) -m32 $(OBJ_BIN) $(LINK) -ldl -lm -o $(BIN_DIR)/$(BINARY)

I think these changes need to be made to the mmsource sourcecode package.
I know I did some unneeded google searches
https://bugs.alliedmods.net/show_bug.cgi?id=5377


I did succeed in loading all the plugins, including stubplugin_mm. As I already had a working srcds server (and tried the wiki steps before), it went rather quick.

[Old and Slow]

Originally Posted by Powerlord I'll be honest, these directions (except for the VDF files) are almost identical to how you compile SourceMod extensions... right down to the ENGINE= and DEBUG= arguments in the make line.

That's straight from the Metamod examples. I haven't ever done anything with Sourcemod.

I have some additional changes to the Makefile that give the debug SO a different name to it can co-exist with the Release version, and also put it in the proper spot in a local addons directory. I also have a streamlined Makefile that just does CSS and doesn't require any arguments, it just builds both versions at the same time. Metamod is setup to support multiple versions, of course.