Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. LNK2019 unresolved external symbol with Ultimate Toolbox COXTootlTipCtrl and ::MonitorFromRect

LNK2019 unresolved external symbol with Ultimate Toolbox COXTootlTipCtrl and ::MonitorFromRect

Scheduled Pinned Locked Moved C / C++ / MFC
helpc++mcpquestion
5 Posts 4 Posters 1 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    Gagnon Claude
    wrote on last edited by
    #1

    Hello, Recently, we move from VisualStudio 2010 to 2013. I use Ultimate Toolbox that I have compiled it with Visual C++ 2013 in a lib. It compiles and links without problem. When I link this lib with my program, I get a link error: LNK2019 unresolved external symbol. With Visual C++ 2010, the link process was correct. The symbol is the MonitorFromRect Windows function in COXToolTipCtrl:: CalculateInfoBoxRect(). We runs on Windows 7 Professionnal 64 bits. We compile on 32 bits Visual C++. Is there a way to bypass this problem? Thanks for any help. Claude

    L M 2 Replies Last reply
    0
    • G Gagnon Claude

      Hello, Recently, we move from VisualStudio 2010 to 2013. I use Ultimate Toolbox that I have compiled it with Visual C++ 2013 in a lib. It compiles and links without problem. When I link this lib with my program, I get a link error: LNK2019 unresolved external symbol. With Visual C++ 2010, the link process was correct. The symbol is the MonitorFromRect Windows function in COXToolTipCtrl:: CalculateInfoBoxRect(). We runs on Windows 7 Professionnal 64 bits. We compile on 32 bits Visual C++. Is there a way to bypass this problem? Thanks for any help. Claude

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      Gagnon Claude wrote:

      Is there a way to bypass this problem?

      Check your project settings to ensure the linker parameters are correct, and the library is included.

      S 1 Reply Last reply
      0
      • L Lost User

        Gagnon Claude wrote:

        Is there a way to bypass this problem?

        Check your project settings to ensure the linker parameters are correct, and the library is included.

        S Offline
        S Offline
        Stefan_Lang
        wrote on last edited by
        #3

        To elaborate on this suggestion, make sure that the linker uses the lib that you compiled with VS 2013, not the one that you compiled with VS 2010. The linker error may imply that it still sees the VS 2010 version. So, check the linker settings to see what search path it is using.

        GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)

        L 1 Reply Last reply
        0
        • S Stefan_Lang

          To elaborate on this suggestion, make sure that the linker uses the lib that you compiled with VS 2013, not the one that you compiled with VS 2010. The linker error may imply that it still sees the VS 2010 version. So, check the linker settings to see what search path it is using.

          GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #4

          I don't think you meant this message for me.

          1 Reply Last reply
          0
          • G Gagnon Claude

            Hello, Recently, we move from VisualStudio 2010 to 2013. I use Ultimate Toolbox that I have compiled it with Visual C++ 2013 in a lib. It compiles and links without problem. When I link this lib with my program, I get a link error: LNK2019 unresolved external symbol. With Visual C++ 2010, the link process was correct. The symbol is the MonitorFromRect Windows function in COXToolTipCtrl:: CalculateInfoBoxRect(). We runs on Windows 7 Professionnal 64 bits. We compile on 32 bits Visual C++. Is there a way to bypass this problem? Thanks for any help. Claude

            M Offline
            M Offline
            Member_14891958
            wrote on last edited by
            #5

            Hi Claude, The reason of the problem is that the code uses the definition of MultiMon.h for function MonitorFromRect instead of using the native definition of this function coming from WinUser.h. Solution : remove line "include MultiMon.h" from OXToolTipCtrl.cpp to force the usage of WinUser.h definition for this function. Florianne :)

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups