Author Topic: Tag Compiler Libraries disable doesnt work  (Read 951 times)

acmemike

  • Community Member
  • Posts: 32
  • Hero Points: 1
Tag Compiler Libraries disable doesnt work
« on: October 24, 2016, 03:30:44 pm »
I am trying to not have compiler tag files for my project.  In the Context Tagging dialog I choose 'Auto Tag...'.  In the Tag Compiler Libraries dialog I de-select the three compilers that are selected. I click OK.  I click 'Auto Tag...' again and the three compilers are re-selected. Why didnt my config changes persist?   Thanks.

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2617
  • Hero Points: 400
Re: Tag Compiler Libraries disable doesnt work
« Reply #1 on: October 24, 2016, 03:43:27 pm »
The Auto-tag GUI is just a utility to help you build the compiler tag files up-front.

To choose what compiler tag file to use for your project, go to Project > Project Properties... > Compile/Link.  I would recommend making a custom compiler configuration named "Empty" if you really do not want to have a compiler tag file.

The purpose of the compiler tag file is so that you have code completion for system libraries like the STL and Posix function calls.

JimmieC

  • Senior Community Member
  • Posts: 423
  • Hero Points: 15
Re: Tag Compiler Libraries disable doesnt work
« Reply #2 on: October 26, 2016, 08:12:46 pm »
This is similar to my post:
      "How to restrict tag file search to specific tag files?"
       https://community.slickedit.com/index.php/topic,11569.msg49098.html#msg49098

I work with embedded code (TI DSP\BIOS, NXP MQX, or bare-metal) so seeing tags for VS, C#, or whatever is just noise and not useful to me. I would like to see SE eventually support the option to choose which tag files to use on a per-project basis.

Jim

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2617
  • Hero Points: 400
Re: Tag Compiler Libraries disable doesnt work
« Reply #3 on: October 26, 2016, 11:15:08 pm »
I am going to add an option to the Project Properties dialog so that you can select "None" for the Compiler Configuration.  This way, you will not get a compiler tag file.  This will be an improvement over creating an empty one yourself.

As for being able to choose which tag files to use on a per-project basis, well, there are so many ways to go about this already, I think this is just a matter of people understanding better how to use the project system. You can add Auto-updated tag files to your workspace, which are only active when your workspace is active.  You can also add sub-projects to your workspace (and even specify that they be tagged separately).

With respect to tagging, the Compiler Tag file is the only thing that is Project/Configuration specific.  Your workspace is the world you are working in right now, a project is just a part of that, so the tagging system needs to be able to see outside of your project within the current workspace.  It would make the whole system intensely tedious if you had to switch projects to find a symbol outside of the current project.  If you want a more restricted world view, you should be using a more restricted workspace.

Language specific tag files are really intended to be global tag files that you expect to use always with that Language.  There is an outstanding feature request to add check-boxes to this dialog per-tag file so that you can easily disable a tag file -- I also plan on implementing that in a future release.