🔒 Locked

Evil Linker

Started by OrigamiMan64 Apr 18, 2004 at 6:09 PM 9 replies 550+ views

Original Post

Apr 18, 2004 at 6:09 PM

I am working in .NET 2003. My solution consists of 4 Win32 static library projects and one Win32 executable. When I build one of the libraries, there are no errors. However, when I build my main executable, I get a linker error that a function referanced by that library has not been defined. How is this possible? The full project can be referanced at www.ezequal.com/OrigamiMan64/DOS3D.zip if it helps.

zealouselixir

157

zealouselixir

Apr 18, 2004 at 6:19 PM

Seems that if I insert the library files into the executable project within the IDE, most of the unresolved externals resolve themselves. That may indicate that you aren''t properly linking the libraries you''re creating to the executable project.

Later,
ZE.

//email me.//zealouselixir software.//msdn.//n00biez.//
m i s c e l l a n e o u s l i n k s

OrigamiMan64

Author

OrigamiMan64

Apr 18, 2004 at 6:26 PM

yah, I noticed without the referances in the DOS3D project, there were a lot more linker errors. However, I added referances to all 4 other projects, and I still get 2 linker errors.

zealouselixir

157

zealouselixir

Apr 18, 2004 at 6:37 PM

Yeah, I got those two as well. But it seems as if they might be legitimate; I couldn''t find a definition for LoadBitmap(char const *, Color). The other one seems to have been caused by a macro replacement of "DrawTextA" for "DrawText" (caused by WinGDI, I suspect). Consider renaming the DrawText function.

Later,
ZE.

OrigamiMan64

Author

OrigamiMan64

Apr 18, 2004 at 6:41 PM

LoadBitmap is defined in Bitmap.cpp, in project Draw

OrigamiMan64

Author

OrigamiMan64

Apr 18, 2004 at 6:44 PM

haha, they were both window''s fault! I #undef''d their function names in my implementation files, and now everything links fine :D Thanks a bunch.

mfawcett

Apr 18, 2004 at 9:05 PM

That's not Windows' fault, that's yours for not using a namespace, AND for using commonly known API function names as your own.

[edited by - mfawcett on April 18, 2004 10:06:12 PM]

OrigamiMan64

Author

OrigamiMan64

Apr 20, 2004 at 11:06 PM

no, the problem was really that windows used the preprocessor to define their functions, and even if I did use a namespace the stupid text replace would have nullified it. I have as much right to those function names as windows does :-P

psamty10

Apr 20, 2004 at 11:11 PM

Interestingly, some of my students ran into the exact same problem in class today... goddamn #defines

It absolutely is not your fault, but its a common mistake....

And yeah, even if you did use a namespace youd still be screwed.... the legacy of #defines destroying perfectly good code continues

[edited by - psamty10 on April 20, 2004 12:12:56 AM]

Code_Dark

103

Code_Dark

Apr 21, 2004 at 12:16 AM

Arrgh, Dev-C++ is horrible for DirectX and OpenGL because of it''s hellish linking problems. It''s horrible!

- CD

// Brought to you by Code_Dark | [( Politics Forum Beta-Test )]

NLDEV

Apr 21, 2004 at 12:22 AM

quote:
Original post by Code_Dark
Arrgh, Dev-C++ is horrible for DirectX and OpenGL because of it's hellish linking problems. It's horrible!

- CD

// Brought to you by Code_Dark | [( Politics Forum Beta-Test )]

That's odd. I have no problem using OpenGL with GCC. What kind of errors do you get?

[edited by - MikeMJH on April 21, 2004 1:24:01 AM]

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.