CMake project minor issue

Sysprogs forums Forums VisualGDB CMake project minor issue

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #33525
    GeneM
    Participant

    We converted a small prototype project to a CMake project.  It looks like if I make a mistake related to CMake that causes the project not to build, the VS Build drop down changes from its normal list of build tasks to the “Build Dropdown after CMake Mistake” in the attached image.  If I close VS and restart it after the mistake, I get the normal Build drop down  “Normal Build Dropdown”, also in the attached image.

    This isn’t a big deal, just a minor annoyance but if there’s a way around it I’d love to hear about it.

    Thanks

    Attachments:
    You must be logged in to view attached files.
    #33533
    support
    Keymaster

    Unfortunately, it is hard to suggest anything specific based on the description you provided.
    In order for us to provide any help with this, we need to be able to reproduce the problem on our side.
    Please provide complete and detailed steps to reproduce the issue as described below:

    1. The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
    2. Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch.
    3. The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.

    You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.

    You can also try checking various diagnostic output from various parts of VisualGDB as described on this page. Although we won’t be able to review it for a specific project unless the we can reproduce the problem from scratch, checking it might provide some clues on what is causing the unexpected behavior.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.