Code::Blocks Forums

User forums => Using Code::Blocks => Topic started by: Czuber on January 29, 2009, 03:58:17 am

Title: Cross Compiling ld problem
Post by: Czuber on January 29, 2009, 03:58:17 am
Hi Guys,

Sorry because probably there is a question like mine but I can't find it.
I'm on Debian Linux trying to build my open source game for windows. So I created a WinRelease tab with Mingw32 compiler and I did the wiki tutorial...

My Release and Debug goes fine, but when I try to build the WInRelease I got:

/usr/lib/gcc/i586-mingw32msvc/4.2.1-sjlj/../../../../i586-mingw32msvc/bin/ld: cannot find -lOgreMain

I'm using some libs kind OpenAL, OIS, Ogre, ODE, Enet...
Do I have to put the dll files to link it? How it works?

Thanks!
Title: Re: Cross Compiling ld problem
Post by: Jenna on January 29, 2009, 06:42:53 am
You will need a development version for windows on your linux-machine.
It must be quiet the same as on a windows machine.

You need the windows specific headers (if any) and the dll's and maybe the .a-files to link against.

The linux libs will not work for th WinRelease-target, of course.
Title: Re: Cross Compiling ld problem
Post by: Czuber on January 29, 2009, 02:49:50 pm
In theory the sources are the same  :shock:
I did a symbolic link in ./i586-mingw32msvc/..../include to /usr/lib/AL , OIS...

About dll libs...
I didn't find any .dll on ../i586-mingw32msvc/lib :|
Where do I could put them?

Thanks by the answer!
[]s
Title: Re: Cross Compiling ld problem
Post by: Jenna on January 29, 2009, 03:08:14 pm
In theory the sources are the same  :shock:
I did a symbolic link in ./i586-mingw32msvc/..../include to /usr/lib/AL , OIS...

About dll libs...
I didn't find any .dll on ../i586-mingw32msvc/lib :|
Where do I could put them?

Thanks by the answer!
[]s


That means you try to use linux-libs for a windows program.

You will need a development version for windows on your linux-machine.
It must be quiet the same as on a windows machine.

You need the windows specific headers (if any) and the dll's and maybe the .a-files to link against.

The linux libs will not work for th WinRelease-target, of course.

That should be enough hints.

Topic locked, because not related to C::B.

Sorry.