Compiling under Linux:zh-cn

From Valve Developer Community
Revision as of 01:46, 23 October 2005 by Softboysxp (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search



Slackware 10.0 ( ) is a good starting base to create your compiling environment.

Setting up the Makefile

As part of the compile process the Microsoft Visual C Project file used to compile your mod under Windows is converted into a snippet of a Makefile. This conversion process needs to be seeded with a few configuration parameters, all of which are contained in linux_sdk/Makefile. At a minimum you should configure these parameters (note, don't use "~" for your home directory since parts of the make process will not understand it):

  • MOD_PROJ, this is the filename of the Windows project file used to compile your mod.
  • MOD_CONFIG, the configuration set to use when compiling the Linux version of your mod. Typically this is the Release Win32 option. The easiest method to determine this parameter is to leave it at default, run the make process once and then look at the Makefile snippets that are produced and select the appropriate one.
  • GAME_DIR, the path to an installation of the game. The Makefile says "the directory the base binaries (, etc) are located" but actually it wants one level up from the directory with
  • CC, CPLUS, CLINK, CPP_LIB, these parameters should be pointed to your particular install of GCC 3.4.1.
  • XERCES_INC_DIR, XERCES_LIB_DIR, the installation directory of the Xerces library.

Once these configuration parameters are set compiling your mod should be a simple as running:


Several people have reported a bug that "export LD_LIBRARY_PATH=~/source/bin" was required before vcpm would run. Here's a patch to fix that bug. (If you haven't applied the SDK Known Issues List#First_big_pass_at_-Wall_and_consistent_code fixes, you will have to take out the -D changes below.)

--- Makefile.vcpm       Sat Oct  1 22:26:26 2005
+++ Makefile.vcpm.bak   Sat Oct  1 22:25:43 2005
@@ -14,12 +14,12 @@

 #we use custome CFLAGS because the base ones interfere with XERCES
-CFLAGS= -w -fpermissive -D_LINUX -DNDEBUG -D_alloca=alloca -D_snprintf=snprintf -D_vsnprintf=vsnprintf $(ARCH_CFLAGS)
 #DEBUG = -g -ggdb

-LDFLAGS_VC=-lm -ldl -L$(XERCES_LIB_DIR) -lxerces-c $(GAME_DIR)/bin/ $(GAME_DIR)/bin/
+LDFLAGS_VC=-lm -ldl -Wl,-rpath -Wl,$(GAME_DIR)/bin -L$(XERCES_LIB_DIR) -lxerces-c $(GAME_DIR)/bin/ $(GAME_DIR)/bin/

 DO_CC=$(CPLUS) $(INCLUDEDIRS) -w $(CFLAGS) -DARCH=$(ARCH) -o [email protected] -c $<

@@ -51,7 +51,7 @@

 $(TIER1_OBJ_DIR)/%.o: $(TIER1_SRC_DIR)/%.cpp
-       $(DO_CC) -Dstricmp=strcasecmp -Dstrcmpi=strcasecmp
+       $(DO_CC)

        -rm -rf $(VCPM_OBJ_DIR)

This will compile the vcpm program, run this against your VCProject file and then use the resulting Makefile snippet and the configuration parameters you set above to compile your mod.

Since you're using GCC, you may also want to look into SDK Known Issues List#Getting the SDK to work under -Wall -Werror.

Running your Mod

To run the mod copy the file produced by the make process to <mod dir>/bin/ and then run srcds_run with the appropriate -game parameter.