Member Avatar for Elixir42

Hi Answerers,

Background:
I just figured out how to solve my unresolved external symbols by just dragging the project files from explorer (contained in exe's directory) and plonking them in the dll project, under thier own filter!

Original Situation:
I was getting 'unresolved external symbols' errors because I was #include-ing files that my dll needed that resided in the exe's project folder. Guessing I would figure that the .obj files would get built and the .dll would not know where they were to link to them.

My Question:
* Will this cause any problems in the future? - having two different .obj files. One for the .dll and one for the .exe?
* Is there a better way of doing this. - I tried adding the directory of the .exe's .obj files to the .dll's linker settings but it didn't work.

Thanks for your thoughts.

  • 2 Contributors
  • 2 Replies
  • 249 Views
  • 3 Hours Discussion Span
  • Latest Post Latest Post by Elixir42
Member Avatar for rubberman

Your biggest problem in the future will be using Visual Studio. In any case, this was NOT a C++ problem. It was a Windows Visual Studio problem.

Member Avatar for Elixir42

Many thanks 'rubberman' for your swift reply. Apologies if I posted this in the wrong place.

Your biggest problem in the future will be using Visual Studio

May I ask you to elaborate on what problems I would get?

Edited by Elixir42 because: formatting
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.