Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Generated SWIG types with long filenames make the repository unusable as submodule (USDK-137)
See original GitHub issueThe repo directly contains generated SWIG code in src/USD.NET/generated/SWIG.
These are filenames there:
src/USD.NET/generated/SWIG/SWIGTYPE_p_std__pairT_VtDictionary__IteratorT_std__mapT_std__string_VtValue_std__lessT_std__string_t_t_p_std__mapT_std__string_VtValue_std__lessT_std__string_t_t__iterator_t_bool_t.cs
src/USD.NET/generated/SWIG/SWIGTYPE_p_VtDictionary__IteratorT_std__mapT_std__string_VtValue_std__lessT_std__string_t_t_p_std__mapT_std__string_VtValue_std__lessT_std__string_t_t__iterator_t.cs
The others in the directory are way more sane:
These long filenames prevent using usd-unity-sdk as submodule as it exceeds maximum allowed path length. Is it really necessary that these are named as they currently are?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yep, good point 😄 I mentally bucketed it with ‘Improve SWIG generated bindings’, but I will keep this open as a bug
Hey, this is not a feature request but a bug!