Compiling with Code::Blocks, part deux
-
- Elite
- Posts: 7243
- Joined: Mon Apr 18, 2005 2:40 pm
- Location: LS87, Buenos Aires, República Argentina
Re: Compiling with Code::Blocks, part deux
The only thing left to try is (VSSprite*)NULL.
But that's just dumb on MSVC's part.
But that's just dumb on MSVC's part.
-
- Confed Special Operative
- Posts: 381
- Joined: Thu Jan 31, 2008 3:25 am
- Location: hiding in a dark corner
Re: Compiling with Code::Blocks, part deux
That actually worked. Everything compiles without errors.klauss wrote:The only thing left to try is (VSSprite*)NULL.
But that's just dumb on MSVC's part.
But now of course I get several hundred unresolved externals because I didn't include any of the new audio stuff in the project yet.
make me a sandwich
make: *** No rule to make target 'me'. Stop.
make: *** No rule to make target 'me'. Stop.
-
- Confed Special Operative
- Posts: 381
- Joined: Thu Jan 31, 2008 3:25 am
- Location: hiding in a dark corner
Re: Compiling with Code::Blocks, part deux
Here's an updated patch. use instead of the previous one.
You do not have the required permissions to view the files attached to this post.
make me a sandwich
make: *** No rule to make target 'me'. Stop.
make: *** No rule to make target 'me'. Stop.
-
- Confed Special Operative
- Posts: 381
- Joined: Thu Jan 31, 2008 3:25 am
- Location: hiding in a dark corner
Re: Compiling with Code::Blocks, part deux
I'm trying to clean up the VS projects, and noticed that they contain the cmd/collide folder as well as cmd/collide2; but there is no cmd/collide in the source tree. OK to nuke that?
Also, cmd/iterator.h absent. Ok to nuke?
3rd; am I right toassume that the following files should not be included in the project directly?
gfx/bmp_to_png.cpp
gfx/raw_to_png.cpp
cmd/unit_jump.cpp
cmd/ai/pythonai.cpp
cmd/oldcollection.cpp
Finally, what am I missing? This is my current output (see attached lest it exceeds max message size)
Also, cmd/iterator.h absent. Ok to nuke?
3rd; am I right toassume that the following files should not be included in the project directly?
gfx/bmp_to_png.cpp
gfx/raw_to_png.cpp
cmd/unit_jump.cpp
cmd/ai/pythonai.cpp
cmd/oldcollection.cpp
Finally, what am I missing? This is my current output (see attached lest it exceeds max message size)
You do not have the required permissions to view the files attached to this post.
make me a sandwich
make: *** No rule to make target 'me'. Stop.
make: *** No rule to make target 'me'. Stop.
-
- Elite
- Posts: 7243
- Joined: Mon Apr 18, 2005 2:40 pm
- Location: LS87, Buenos Aires, República Argentina
Re: Compiling with Code::Blocks, part deux
If the source is missing, it's ok I would think.shenle wrote:I'm trying to clean up the VS projects, and noticed that they contain the cmd/collide folder as well as cmd/collide2; but there is no cmd/collide in the source tree. OK to nuke that?
Also, cmd/iterator.h absent. Ok to nuke?
You're correct, they're not in CMakeLists.txt, so linux isn't using them, I can't think of a reason for windows to want them either.shenle wrote: 3rd; am I right toassume that the following files should not be included in the project directly?
gfx/bmp_to_png.cpp
gfx/raw_to_png.cpp
cmd/unit_jump.cpp
cmd/ai/pythonai.cpp
cmd/oldcollection.cpp
-
- Elite
- Posts: 7243
- Joined: Mon Apr 18, 2005 2:40 pm
- Location: LS87, Buenos Aires, República Argentina
Re: Compiling with Code::Blocks, part deux
You need to include unit.cpp, which is no longer included in unit.h.shenle wrote:Finally, what am I missing? This is my current output (see attached lest it exceeds max message size)
-
- Confed Special Operative
- Posts: 381
- Joined: Thu Jan 31, 2008 3:25 am
- Location: hiding in a dark corner
Re: Compiling with Code::Blocks, part deux
unit.cpp is already included, as well as unit.h.klauss wrote:You need to include unit.cpp, which is no longer included in unit.h.shenle wrote:Finally, what am I missing? This is my current output (see attached lest it exceeds max message size)
make me a sandwich
make: *** No rule to make target 'me'. Stop.
make: *** No rule to make target 'me'. Stop.
-
- Elite
- Posts: 7243
- Joined: Mon Apr 18, 2005 2:40 pm
- Location: LS87, Buenos Aires, República Argentina
Re: Compiling with Code::Blocks, part deux
Are you sure?
Take a good look. I remember it was marked as "do not build this file" (or something like that).
Take a good look. I remember it was marked as "do not build this file" (or something like that).
-
- Confed Special Operative
- Posts: 381
- Joined: Thu Jan 31, 2008 3:25 am
- Location: hiding in a dark corner
Re: Compiling with Code::Blocks, part deux
You're right. I'm not all that familiar with VS10, having used mostly C::B and VS7 in the past so I missed that.
Building now.
Building now.
make me a sandwich
make: *** No rule to make target 'me'. Stop.
make: *** No rule to make target 'me'. Stop.
-
- Confed Special Operative
- Posts: 381
- Joined: Thu Jan 31, 2008 3:25 am
- Location: hiding in a dark corner
Re: Compiling with Code::Blocks, part deux
Code: Select all
1>OpenALRenderer.obj : error LNK2019: unresolved external symbol __imp__alSpeedOfSound referenced in function "protected: void __thiscall Audio::OpenALRenderer::setupDopplerEffect(void)" (?setupDopplerEffect@OpenALRenderer@Audio@@IAEXXZ)
1>unit_generic.obj : error LNK2019: unresolved external symbol "public: virtual __thiscall UnitImages<void>::~UnitImages<void>(void)" (??1?$UnitImages@X@@UAE@XZ) referenced in function "public: virtual void * __thiscall UnitImages<void>::`scalar deleting destructor'(unsigned int)" (??_G?$UnitImages@X@@UAEPAXI@Z)
make me a sandwich
make: *** No rule to make target 'me'. Stop.
make: *** No rule to make target 'me'. Stop.
-
- Elite
- Posts: 7243
- Joined: Mon Apr 18, 2005 2:40 pm
- Location: LS87, Buenos Aires, República Argentina
Re: Compiling with Code::Blocks, part deux
That means you're using a new al.h but an old al.lib/dll
-
- Confed Special Operative
- Posts: 381
- Joined: Thu Jan 31, 2008 3:25 am
- Location: hiding in a dark corner
Re: Compiling with Code::Blocks, part deux
I'm using both from vega-vc7, supposedly they're the same version.klauss wrote:That means you're using a new al.h but an old al.lib/dll
make me a sandwich
make: *** No rule to make target 'me'. Stop.
make: *** No rule to make target 'me'. Stop.
-
- Confed Special Operative
- Posts: 381
- Joined: Thu Jan 31, 2008 3:25 am
- Location: hiding in a dark corner
Re: Compiling with Code::Blocks, part deux
I have downloaded and compiled OpenAL from svn, and replaced all the headers and libs with the new versions. I still get
Code: Select all
1>OpenALRenderer.obj : error LNK2019: unresolved external symbol __imp__alSpeedOfSound referenced in function "protected: void __thiscall Audio::OpenALRenderer::setupDopplerEffect(void)" (?setupDopplerEffect@OpenALRenderer@Audio@@IAEXXZ)
1>unit_generic.obj : error LNK2019: unresolved external symbol "public: virtual __thiscall UnitImages<void>::~UnitImages<void>(void)" (??1?$UnitImages@X@@UAE@XZ) referenced in function "public: virtual void * __thiscall UnitImages<void>::`scalar deleting destructor'(unsigned int)" (??_G?$UnitImages@X@@UAEPAXI@Z)
make me a sandwich
make: *** No rule to make target 'me'. Stop.
make: *** No rule to make target 'me'. Stop.
-
- Elite
- Posts: 7243
- Joined: Mon Apr 18, 2005 2:40 pm
- Location: LS87, Buenos Aires, República Argentina
Re: Compiling with Code::Blocks, part deux
It's just common sense: if the call was wrong (which it isn't), the compiler would complain, not the linker.
The fact that it's the linker complaining hints that the .h has the function's declaration, but the .lib doesn't have the function itself.
So... I'll urge you to keep digging
The fact that it's the linker complaining hints that the .h has the function's declaration, but the .lib doesn't have the function itself.
So... I'll urge you to keep digging
-
- Confed Special Operative
- Posts: 381
- Joined: Thu Jan 31, 2008 3:25 am
- Location: hiding in a dark corner
Re: Compiling with Code::Blocks, part deux
I would dig, but don't know where anymore. I'm not a programmer (duh!)
make me a sandwich
make: *** No rule to make target 'me'. Stop.
make: *** No rule to make target 'me'. Stop.