Linker can not find static library in same directory?

Apparently the directory containing the project files is not included in the linker search path, and needed to be defined explicitly by adding ". \" to the list of directories containg library files for the projects.

Up vote 0 down vote favorite share g+ share fb share tw.

I'm porting some Visual Studio 2008/VC9 stuff to Code::Blocks/MinGW and for some reason the linker cannot find a static library from another project in the workspace. In Visual Studio 2008 I could just set the static lib project as a dependency, and it would build in the right order (i.e. Static lib needs to be built before linking the other project), and link the correct library for the configuration.

I couldn't find such an option in Code::Blocks, so I made sure to explicitly build the static lib first (libcommon. A) then under "build options" for the other project add "libcommon. A" in the "linker settings".

The . A file is located in the same directory as the project files, however I still get an error from the linker of the other projects saying they cant find it... ld. Exe cannot find -lcommon What am I doing so it cant find the library, even though its right next to the projects file?

Also is there a better way to simulate the Visual Studio dependencies within a single solution/workspace? C++ linker mingw static-libraries codeblocks link|improve this question edited Dec 12 '09 at 20:47 asked Dec 10 '09 at 12:29Fire Lancer5,13843073 68% accept rate.

Your error message mentions "-lcommon", but you say your library is named "libcommon. A". I am not familiar with Code::Blocks; does "-lcommon" translate to "libcommon.

A"? You could always run File Monitor and see what file (and in which directory) the linker is looking for. – Luke Dec 12 '09 at 18:54 Well I specifically told code blocks to link "libcommon.

A" and it gave the linker "lcommon", so I'm going to go with the compiler doesn't expect the proceeding "lib" and the ". A" extension. Other libraries work fine and have the same difference between the filename and what the linker gets.

– Fire Lancer Dec 12 '09 at 19:10.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.