Building on Windows, linker error

Building on Windows, linker error

Postby StefanP.MUC » 18 Mar 2011, 11:58

I finally are near to get the build done one WIndows (using Code::Blocks, Eclipse gave me way to much errors and crashes). Then I can speed up my work on the code because I don't need to cross-check everything between Windows and my Linux VM.

But I get an error from the linker:
{l Code}: {l Select All Code}
ld.exe, cannot find -lpthreadGC2


I can't find what's wrong there. The correct path is set to this (I even tried setting a global envrionment variable directly to this). Where's the correct place to look what's causing this error?
StefanP.MUC
 

Re: Building on Windows, linker error

Postby oln » 18 Mar 2011, 12:24

I'll have a look at it, may have broken some things after reorganising the script.
User avatar
oln
 
Posts: 1020
Joined: 26 Oct 2010, 22:16
Location: Norway

Re: Building on Windows, linker error

Postby oln » 18 Mar 2011, 12:51

Found the issue, managed to write include_directories instead of link_directories.
Fixing it now.
User avatar
oln
 
Posts: 1020
Joined: 26 Oct 2010, 22:16
Location: Norway

Re: Building on Windows, linker error

Postby oln » 18 Mar 2011, 13:08

Should be fixed now.
Also fixed the findcegui so that it finds cegui if the env var CEGUIDIR is specified, and fixed so that it finds the openal bundled with sfml if sfml is found.
User avatar
oln
 
Posts: 1020
Joined: 26 Oct 2010, 22:16
Location: Norway

Re: Building on Windows, linker error

Postby StefanP.MUC » 18 Mar 2011, 13:17

Nice, thanks. It works now perfectly. Just compiled the first time on Windows. :D
StefanP.MUC
 

Re: Building on Windows, linker error

Postby StefanP.MUC » 18 Mar 2011, 13:46

By the way, is this correct that cmake generates Code::Blocks project files holding the absolute path to the source files? I store the OpenDungeons project in a subfolder of "My Documents" and Codeblocks displays the very long absolute path to the source file instead of the expected short relative path (this is how Codeblocks would do it if you create a project from within CB).
This looks a bit messy...

Example:
current: "C:/Users/Stefan/Documents/Programs/opendungeons/src/MapEditor.cpp" (cmake version of CB Project)
expected: "src/MapEditor.cpp" (CB version of CB project)
StefanP.MUC
 

Re: Building on Windows, linker error

Postby oln » 18 Mar 2011, 14:02

I think that is the "correct" behaviour yes.
I think I read somewhere why it's done like this, but I can't remember where.
User avatar
oln
 
Posts: 1020
Joined: 26 Oct 2010, 22:16
Location: Norway

Who is online

Users browsing this forum: No registered users and 1 guest