kurt

Forum Replies Created

Viewing 3 posts - 16 through 18 (of 18 total)
  • Author
    Posts
  • in reply to: How to use Clang Static Analysis #13405
    kurt
    Participant

    Ah, I’ve learned something new.

    (1) In the “IntelliSense Directories” tab, I cannot just add a top-level directory and expect the system to traverse recursively … I will need to add each folder explicitly.  For

    example:

    <toolchain_root_folder>/usr/src/kernel/include
    <toolchain_root_folder>/usr/src/kernel/include/linux

    By manually adding these folders one-by-one, I am able to make the system find things like size_t, time_t, etc.

    (2) The order in which I place these folders do matter.  For example, toolchain folders should be on top, while project folders should be below.

    —————————–

    Question:  Is there an easier way where I can just put define <toolchain_root_folder> and let change search recursively?

    in reply to: How to use Clang Static Analysis #13404
    kurt
    Participant

    Thanks for the screenshot and letting me know it’s automated behavior.  It is working now.

    While a bit off topic, I still have issues setting up Clang IntelliSense:

    (1) From the posts in the forum, I understood that we have to put in the correct flags (-D<xxx>) for the parsing to work.  I might have to read up on Clang since I am using GCC… it’s a vague question, but any examples or tutorials for non-Clang users to reap the benefits for Clang IntelliSense will be appreciated.

    (2) I am getting simple IntelliSense errors like “vector is not part of the std namespace”.  Ok, I understand that the library files are in the VM and not in Visual Studio/PC, so I need to let VisualGDB know about the paths.  So, under the “IntelliSense Directories” tab in the Settings, I clicked “Add Remote” and added all the paths in the remote VM, which includes my project’s source headers, the compiler headers (/usr/include/, /usr/lib/gcc), and the paths to my ARM toolchain.  I can see that IntelliSense errors related to missing functions from my project is now resolved, but I still face issues with the standard libraries (such as the vector example) and things like “unable to find size_t”.  What else do I need to do?

     

    in reply to: Moving a VisualGDB license to another computer/VM #13383
    kurt
    Participant

    Hi,

    Is this answer still valid now in 2017?  In the “About” dialog, I see that there is a “Revert to trial button”.  I wonder if that can be used to switch between 2 machines like Photoshop?

    Thanks.

    • This reply was modified 6 years, 11 months ago by kurt. Reason: typo
Viewing 3 posts - 16 through 18 (of 18 total)