Compiler Tag files vs. Language Tag files

[smitchell]

This is probably a "newbie" type question but I haven't been able to find an answer.

My projects are predominantly C/C++ and use variants of the Microsoft Visual 'C/C++' compiler.
I can identify probably four different build environments for my projects:
- Visual Studio 2008 with standard headers for C/C++
- Visual Studio 2008 with standard headers for C/C++ plus MFC
- Visual Studio 2008 with standard headers for C/C++ plus wxWidgets
- Windows DDK which uses a different MS Visual 'C/C++' compiler and separate header files

Currently, I use a single compiler tag file for Visual Studio 2008 and then supplement it with "language specific" tag files for WINDDK and wxWidgets. This arrangement makes symbols visible but there are duplicates that cause navigation to frequently prompt me to select one of several alternates.

How can I configure my tag files to eliminate the symbol pollution between these different build environments?

Stan Mitchell
SlickEdit Version 14.0.0.7

[hs2]

I've added new compiler tag file(s) e.g. for my WDK projects. Since these tag files are associated with projects this should be fine also for your use cases.
HS2

[smitchell]

Thanks for the guidance. I went back to the manual to read up on creating custom projects. Then I remembered why I had abandoned that approach (I think ~2007). All of my projects are created in Visual Studio. So I am dependent on using a Visual Studio project type (the .sln and .vcproj files are created outside of SlickEdit). That choice forced me to use the Language specific tag files for the different build environments. Looks like that's the best I can do.

Stan Mitchell
SlickEdit Version 14.0.2.2

[pvonkaenel]

I had a similar tagfile issue, but another user pointed out a very clever and useful solution:

http://community.slickedit.com/index.php?topic=4759.0

Hope that helps,
Peter

[smitchell]

Thank you Peter (and dunkers) that's exactly what I was looking for!

Stan Mitchell
SlickEdit Version 14.0.2.2