[comment] * these descriptions are intended for developers only... [compile] * copy cds(or all contents of harddisk MS sent) to harddisk(c:/mech/... or somewhere) -> I'll assume this(=c:/mech/) directory from below... -> & I didn't test with other directory... * unzip this package & overwrite original(above) directories... c:/mech/coretech/... c:/mech/ctcls c:/mech/launcher c:/mech/mw4/... * make directory "c:/mech/dbg.bin/" * move c:/mech/mw4/content to c:/mech/dbg.bin/content -> "mw4.exe -build ..." can be executed via Profile version only in original version -> but we changed this command can be excuted via Debug version too... -> actually in Profile version you should move c:/mech/dbg.bin/content to c:/mech/pro.bin/content before building resource -> copy c:/mech/dbg.bin/resource to c:/mech/rel.bin/resource after building resource via debug version * launch "Microsoft Developer Studio" * setup "include & lib" directories from "{MS Developer Studio=Micro Visual C++ 6.0}/Tools{=Menu}->Options{=MenuItem}->Directory{=Tab}" -> first: Platform SDK(or DirectX SDK) & 2nd: Developer Studio * copy {Developer Studio Directory}/vc98/include/*.* to c:/stlnative -> see c:/Mech/MW4/Libraries/stlport/stl_inc_find.hpp -> this(=c:/stlnative) directory must not be included in devstudio/Tools->Options->Directory * load c:/mech/mw4/code/MechWarrior4.dsw -> we never touched project workspaces(*.dsw) except this file... -> we never use any other .dsw file to build mw4.exe & autoconfig.exe * Select MW4Application project -> execute "Build{=Menu}->Build mw4.exe{=Menuitem}" * Select "Launcher" project -> execute "Build{=Menu}->Build launcher.exe{=Menuitem}" * now mw4.exe & launcher.exe is located in c:/mech/dbg.bin -> for release version : c:/mech/rel.bin -> for profile version : c:/mech/pro.bin -> ... * we didn't include source-directories that are not touched in this package -> so OVERWRITING is required... [Changed & moved projects] * we moved ".../Content/ShellScripts/ScriptStrings" to ".../mw4/code/ScriptStrings" -> for sourcesafe & other problem... * we renamed ".../mw4/Libraries/comline" to ".../mw4/Libraries/server" -> for sourcesafe problem... * we remove all the "post-build step" -> except MissionLang/MW4/ScriptStrings projects -> instead of "post-build step" we use sharing feature of sourcesafe... * coretech/Libraries/GamePlatform is duplicated as coretech/Libraries/GamePlatformNoMain -> for compiling coretech/Code/* -> & WinMain(...) is uncommented in coretech/Libraries/GamePlatform -> so coretech/Libraries/GamePlatformNoMain is used for mw4.exe [touched sources : security] * We fixed server keys(for packet encryption) as 1000 -> see : c:/mech/mw4/libraries/adept/network.cpp -> Network::Network() -> for console problem... -> actually in tesla system client & server do not communicate directly for game-lobby -> instead of direct communication between server & client(s) they are fully dependent to console(mw4.exe -ctcltype 1...) -> this may not be needed these days but we have no choice in early time of development... * we use "#define USE_HACK_CRC 1" in c:/Mech/MW4/Code/MW4/NetGenericMessages.cpp -> for testing(mainly for debug version) -> we work as a team & our developement-environment are not same -> so disk image of mw4.exe is not same & it will happen "resource doesn't match" message when join a game -> even if same disk image of mw4.exe is built this message will pop when we setup breakpoint in security zones -> "#define USE_HACK_CRC 1" can be commented in final release... -> but we didn't test... [other changes in source files] * we touched sources as minimum as possible for checking sources we've touched... -> we didn't use same comment style & even use korean language for commenting... -> so use wincmd.exe to check sources touched...(wincmd.exe/Commands{=menu}->Synchronize dirs...{=Menuitem}) -> use "by content" options -> windiff is not proper for these purpose(comparing multiple files) * some .cpp files are not compiled directly but included in some other .cpp files -> for header file setup... [project settings] * we added LAB_ONLY to debug settings for resource-building in debug version -> to check bad resources * we did not use "post-build step" for coping output files -> we changed output directory & link->output-files directly in project settings * we added NO_MR & NO_LOG to mw4 & mw4application projects -> because we're working on Mission Review now... [misc changes] * we us* we use "-nocd" options by default * we use AssetsDirectory1/2 where mw4.exe is exist... * see sources for other changes using wincmd.exe ^^ [sourcesafe] * we use sourcesafe & "shareing feature" -> so same file may exist in 2 or more directories... -> but in this package we remove sourcesafe reference from *.dsp/*.dsw for your convennince [tools] * we didn't include tools directories in this package -> & original sources may not be compiled correctly...