Talk:BuildTheCode

From Sirikata Wiki
Jump to: navigation, search

Windows dependencies.

The requirement of Cygwin for the windows compile is not necessary.

If you have cygwin, you will still need to install a SVN client. Then, checkout:

and name that directory "dependencies".

If using a command-line SVN client, run "svn co http://sirikata.googlecode.com/.../win32vc9 dependencies"

Then, go into the dependencies folder and unzip all the packages directly into the dependencies directory ("Extract here"). The extracted directories should have generic names like "installed-curl".

PatrickHorn 05:43, 24 February 2009 (UTC)

DLL Path under windows

[First of all, if you get a message saying anything like 0xc0150002, "failed to initialize properly", "the runtime asked to terminate", or about "reinstalling the application", first check that if you use Visual Studio 2005, you have Service Pack 1 installed. Also, you may need to install the "Visual C++ Redistributable Package".]

Currently, we dynamically link to Boost and cURL. In order to have windows find these DLLs, you have a couple of options. Choose the one that feels the most natural to you.


Add the following two folders into your PATH environment variable:

  • C:\sirikata\dependencies\boost_1_35_0\lib
  • C:\sirikata\dependencies\installed-curl
  • (Any other folder with DLLs is not currently required, but will be needed soon)

To set the PATH environment variable:

  • right click on My Computer, select Properties, click on the Advanced tab, and click on Environment Variables....
  • Then, you can choose if you want to set the Current User or the Local Machine environment variables, and click on the PATH variable, and click Edit....
  • Set the cursor at the end of the text field, and add a ";", followed by the boost path, then another ";" and the curl path, etc.

Move the DLLs into the same directory as the executable

Another option is to simply move the DLLs (not the LIB files) out of the dependencies\boost_1_35_0 folder and into the build\cmake\Debug folder.

Move the DLLs into a common folder (or system directory)

A hybrid of the above two, is to move all of the DLLs into a common folder, maybe called "dlls". Then edit environment variables as described above, and add just the "dlls" folder to the PATH.

Any comments about this process? Should we provide a simple batch file to copy all the DLLs into a single folder? PatrickHorn 05:43, 24 February 2009 (UTC)