HOW TO BUILD ============ Requirements: ------------- Visual C++ compiler 2010 (VC 10.0) or up - Included in visual c++ express 2010 or windows sdk 7.0 Note: If you're having trouble installing the windows sdk, you may be affected by this bug: http://support.microsoft.com/kb/2717426 QtSDK 4.8.x (http://qt-project.org/downloads) - Qt5 is not yet supported but WIP - Install according to instruction boost libraries (http://www.boost.org/) - Compile according to their instructions (using vc++): http://www.boost.org/doc/libs/1_54_0/more/getting_started/windows.html - A few of the boost libraries need to be built (the rest is header-only). The only compiled lib MO needs (at the time of writing) is boost_thread. You can disable the others to safe yourself compile time (even on a modern system compiling boost can easily take an hour) zlib (http://www.zlib.net/) - Compile static library according to their instructions - Depending on the version of zlib and how you built you should have a file called zlibstatic.lib or zlibstat.lib in "build" or "x86\ZLibStatRelease". - Please copy that lib file to "build\zlibstatic.lib" (if it doesn't exist) so MO finds it. 7z.dll (http://www.7-zip.org/download.html) - Part of the 7-zip program - Has to be the 32-bit dll! (approx. 893kb) - If you don't want to install 7-zip (32-bit) you can open the 7z installer (i.e. 7z920.exe) in an archiving tool and unpack only the 7z.dll Recommended: ------------ Qt Creator Set up (using Qt Creator): -------------------------- 1. Using Qt Creator open source/ModOrganizer.pro from your working copy 2. Open the "Projects" tab, open the "Details" for "Build Environment" 3. Click "Add" to add a variable called "BOOSTPATH" with the path of your boost installation as the value (i.e. C:\code\boost_1_52_0) 4. Click "Add" to add a variable called "ZLIBPATH" with the path of your zlib installation as the value (i.e. C:\code\zlib-1.2.7) 5. Switch the build configuration at the very top of the same page from "debug" to "release" (or vice versa) and repeat steps 3 and 4 6. Compile the configuration(s) you want to use (debug and/or release) (Build All). This should compile correctly. 7. return to the "projects" tab and switch to "Run Settings" 8. Determine the folder of the qt binaries in the package you downloaded. This could be "QtSDK\Desktop\Qt\4.8.5\msvc2010\bin" or "Qt4.8.5\bin" For Release build: 9r. Add a "Run configuration" that points to \output\ModOrganizer.exe 10r. Copy "7z.dll" to \output\dlls 11r. From the qt binaries directory, copy the following files to \output\dlls: QtCore4.dll, QtDeclarative4.dll, QtGui4.dll, QtNetwork4.dll, QtScript4.dll, QtSql4.dll, QtWebkit4.dll, QtXml4.dll, QtXmlPatterns4.dll For Debug build: 9d. Add a "Run configuration" that points to \outputd\ModOrganizer.exe 10d. Copy "7z.dll" to \outputd\dlls 11d. From the qt binaries copy the following files to \outputd\dlls: QtCored4.dll, QtDeclaratived4.dll, QtGuid4.dll, QtNetworkd4.dll, QtScriptd4.dll, QtSqld4.dll, QtWebkitd4.dll, QtXmld4.dll, QtXmlPatternsd4.dll Now you should be able to compile and run Mod Organizer. Please note that when you change anything apart from the "organizer" subproject, qt creator may not pick up on the changes and not recompile the modified subproject. the "organizer" project on the other hand is always re-linked. If anyone knowledgeable enough with qmake can fix that that would be awesome. Set up (without Qt Creator): ---------------------------- 1. open a command line shell and navigate to \source 2. run "qmake -tp vc" to create a visual c++ solution 3. Open that solution 4. - 98. A miracle happens 99. You can now compile MO using VC I'm not using this workflow so I can't give more detailed instructions. Please note that the primary project format of MO remains qmake, if you work with visual studio and make changes to the project (like adding source files) you have to manually transfer those changes to the .pro file.