Project property page not showing c++ and linker properties

Sysprogs forums Forums VisualGDB Project property page not showing c++ and linker properties

This topic contains 5 replies, has 2 voices, and was last updated by  support 2 weeks, 3 days ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #33141

    paulh001
    Participant

    I have created a new cmake project with VisualGDB wizard and want to config compiler and linker settings, but in the project property page there a now compiler and linker options visible. I remember this always has worked in the past. Also msbuild new project do not work correct. However old project created in the past still have the properties.

     

    Microsoft Visual Studio Community 2022
    Version 17.3.3
    VisualStudio.17.Release/17.3.3+32825.248
    Microsoft .NET Framework
    Version 4.8.04161

    Installed Version: Community

    Visual C++ 2022 00482-90000-00000-AA026
    Microsoft Visual C++ 2022

    Arduino IDE for Visual Studio by Visual Micro 22.0
    Visual Micro is an Arduino Compatible IDE for Visual Studio 2022. For more information and forum please visit http://www.visualmicro.com.

    ASP.NET and Web Tools 17.3.376.3011
    ASP.NET and Web Tools

    Azure App Service Tools v3.0.0 17.3.376.3011
    Azure App Service Tools v3.0.0

    C# Tools 4.3.0-3.22423.10+b35bb0baca1071d50cc4f8cf5a1a89e7cc112461
    C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

    Cookiecutter 17.0.22179.3
    Provides tools for finding, instantiating and customizing templates in cookiecutter format.

    Linux Core Dump Debugging 1.0.9.32708
    Enables debugging of Linux core dumps.

    Microsoft JVM Debugger 1.0
    Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

    NuGet Package Manager 6.3.0
    NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/

    Python – Profiling support 17.0.22179.3
    Profiling support for Python projects.

    Python with Pylance 17.0.22179.3
    Provides IntelliSense, projects, templates, debugging, interactive windows, and other support for Python developers.

    Test Adapter for Boost.Test 1.0
    Enables Visual Studio’s testing tools with unit tests written for Boost.Test. The use terms and Third Party Notices are available in the extension installation directory.

    Test Adapter for Google Test 1.0
    Enables Visual Studio’s testing tools with unit tests written for Google Test. The use terms and Third Party Notices are available in the extension installation directory.

    TypeScript Tools 17.0.10701.2001
    TypeScript Tools for Microsoft Visual Studio

    Visual Basic Tools 4.3.0-3.22423.10+b35bb0baca1071d50cc4f8cf5a1a89e7cc112461
    Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

    Visual C++ for Linux Development 1.0.9.32708
    Visual C++ for Linux Development

    Visual Studio IntelliCode 2.2
    AI-assisted development for Visual Studio.

    VisualGDB 5.6
    Allows developing and debugging Embedded, Linux, Android and other GCC/GDB-based applications with Visual Studio.

    #33142

    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.

    Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.

    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.

    #33152

    paulh001
    Participant

    Hello,

    The steps I took were.

    1. Start Visual studio
    2. select new project
    3. select template linux visualgdb
    4. Select CMake / Ninja
    5. after project is created try to open project properties (Menu project -> properties)
    6. Dialog box appears but without any properties for compiler and linker

    See attachment

     

     

    • This reply was modified 2 weeks, 3 days ago by  paulh001.
    Attachments:
    You must be logged in to view attached files.
    #33153

    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.

    Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.

    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.

    • This reply was modified 2 weeks, 3 days ago by  support.
    #33157

    paulh001
    Participant

    So, you cannot set compiler and linker settings like you can with MSBUILD.

    That would be a disappointment.

    Attachments:
    You must be logged in to view attached files.
    #33159

    support
    Keymaster

    You can if you follow the steps outlined in the documentation and tutorials. If you are doing something different from the steps suggested in the documentation, you will inevitably get different results.

    We have asked you to provide the steps to reproduce the issue beginning from VS launch, accompanied by the uncropped screenshots, so that we could point out what you are doing incorrectly. Instead, you have provided ambiguous steps and attached 3 instances of the same cropped screenshot that does not show sufficient context.

    We will not be able to help you based on the information you provided and have to close the issue. If you require further help, please do read and follow our problem reporting guidelines. We will not be able to provide any further replies unless you provide the information we requested.

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.