| unresolved external during link [message #1737103]
||Tue, 05 July 2016 17:03
| Alex Birman
Registered: March 2014
I've encountered a weird problem and I'll be glad if you could help me.
During a link of an executable project I get and unresolved external error.
The structure of my application is as the following:
Main_exe - executable project.
Using_lib_proj - using the unresolved function unres_foo() from unresolved.cpp
Used_lib_proj - project that contains the unresolved.cpp file.
Side_lib_proj - I'll tell about it later on.
Using_lib_proj references the Used_lib_proj.
Main_exe references all the libs. Also, in its properties, Linker section, I've added all the other libs, both in -l and -L options.
Despite the above, unres_foo() is unresolved during link.
The weird thing is, that when I open the definition of unres_foo() with F3 where it's used in Using_lib_proj, an empty file unresolved.cpp is opened, but it's path is Side_lib_proj path/Used_lib_proj/unresolved.cpp!
Side_lib_proj and Used_lib_proj are parallel folders, one aside another. There's no such a path Side_lib_proj path/Used_lib_proj/
soooo... why does it happen? Where can I search for a mistake in definitions?
Powered by FUDForum
. Page generated in 0.01157 seconds