Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QML and Qt Quick
  4. How can I debug the dread jom "error 2" problem?
Forum Updated to NodeBB v4.3 + New Features

How can I debug the dread jom "error 2" problem?

Scheduled Pinned Locked Moved QML and Qt Quick
3 Posts 2 Posters 1.3k 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.
  • C Offline
    C Offline
    cscooper
    wrote on last edited by
    #1

    I've been working on an application on Linux, and now need to get it to build on Windows using Visual Studio 2013. I can get it to mostly build on Visual Studio 2010 (though the compiler chokes because one of my libaries uses fenv.h) so I know the CMakeLists.txt is good (note it's a cmake project and not a pro project)

    When I switch to a Visual Studio 2013 kit, jom starts giving me the "error 2". I tried opening a command window and running the 'vcvarsall' batch file before running QtCreator from the command line (to ensure the proper environment is set up) and it didn't help.

    Does jom write any sort of log or error file, to give me some hint why it hates me so much?

    Thanks,
    Chris

    1 Reply Last reply
    0
    • dheerendraD Offline
      dheerendraD Offline
      dheerendra
      Qt Champions 2022
      wrote on last edited by
      #2

      error 2 ? This is clearly file not found issue. For which file it is giving this error ?

      Dheerendra
      @Community Service
      Certified Qt Specialist
      http://www.pthinks.com

      1 Reply Last reply
      0
      • C Offline
        C Offline
        cscooper
        wrote on last edited by
        #3

        I was able to track down the problem - jom had a dependency on a DLL (I think it was mspdb100.dll) which only existed in Visual Studio 2010, and so when I switched my path to point to Visual Studio 2013 it couldn't find the DLL. I don't think it's a good idea to have jom rely on external dependencies like this (or if it must, those DLLs should be part of the installation) ...

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved