-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Python script for generating Natvis file and update file for 3.11.2 #3697
Merged
nlohmann
merged 3 commits into
nlohmann:develop
from
falbrechtskirchinger:inline-ns-natvis
Aug 12, 2022
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
generate_natvis.py | ||
================== | ||
|
||
Generate the Natvis debugger visualization file for all supported namespace combinations. | ||
|
||
## Usage | ||
|
||
``` | ||
./generate_natvis.py --version X.Y.Z output_directory/ | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
#!/usr/bin/env python3 | ||
|
||
import argparse | ||
import itertools | ||
import jinja2 | ||
import os | ||
import sys | ||
|
||
if __name__ == '__main__': | ||
parser = argparse.ArgumentParser() | ||
parser.add_argument('--version', required=True, help='Library version number') | ||
parser.add_argument('output', help='Output directory for nlohmann_json.natvis') | ||
args = parser.parse_args() | ||
|
||
namespaces = ['nlohmann'] | ||
abi_prefix = 'json_abi' | ||
abi_tags = ['_diag', '_ldvcmp'] | ||
version = '_v' + args.version.replace('.', '_') | ||
inline_namespaces = [] | ||
|
||
for n in range(0, len(abi_tags) + 1): | ||
for tags in itertools.combinations(abi_tags, n): | ||
ns = abi_prefix + ''.join(tags) | ||
inline_namespaces += [ns] | ||
inline_namespaces += [ns + version] | ||
|
||
namespaces += [f'{namespaces[0]}::{ns}' for ns in inline_namespaces] | ||
|
||
env = jinja2.Environment(loader=jinja2.FileSystemLoader(searchpath=sys.path[0]), autoescape=True, trim_blocks=True, | ||
lstrip_blocks=True, keep_trailing_newline=True) | ||
template = env.get_template('nlohmann_json.natvis.j2') | ||
natvis = template.render(namespaces=namespaces) | ||
|
||
with open(os.path.join(args.output, 'nlohmann_json.natvis'), 'w') as f: | ||
f.write(natvis) |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to use wildcards for the namespace?
nlohmann::*::basic_json...
? If so, could we also hardcode the values fornlohmann::*::detail::value_t::*
? This would allow a single natvis file that would work for any version?Otherwise, would it make sense to include the version number in the filename so that users could have multiple version files installed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wildcards are only supported for template parameters according to the documentation.
Users will have to comment on whether versioning the Natvis file would be helpful. (ping @jheydebrand)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I saw documentation that said that they worked for templates, but it didn't specifically say that it was only used there, so I wasn't sure if it was limited to templates or just poorly documented.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and
The very specific wording suggests to me it only works for templates. 🤷♂️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed that it only works for templates. :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the swift responses.
Versioning the natvis file would not provide any benefit for me.
When consuming the library via its CMake integration the correct / matching natvis file will be included anyway and I have no desire to copy the file to some system-wide directory (which is supported by Visual Studio and might have been the use-case for versioned natvis files you were thinking about?).