Skip to content
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

[BUG] Windows Headers for nvCOMP 4.0.0 and 4.0.1 #109

Open
Nicolas-Iskos opened this issue Sep 5, 2024 · 2 comments
Open

[BUG] Windows Headers for nvCOMP 4.0.0 and 4.0.1 #109

Nicolas-Iskos opened this issue Sep 5, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@Nicolas-Iskos
Copy link

Describe the bug

  1. Public nvCOMP 4.0.0 doesn't seem to include header files (no "include" directory).
  2. Public nvCOMP 4.0.1 has headers but linker issues arise when using static compilation in debug mode. A runtime crash occurs when using the static library in release mode. See included attachments for error messages.

+@VasuAgrawal to add more detail if necessary.

@Nicolas-Iskos Nicolas-Iskos added ? - Needs Triage bug Something isn't working labels Sep 5, 2024
@naveenaero naveenaero self-assigned this Sep 11, 2024
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@naveenaero
Copy link
Collaborator

naveenaero commented Oct 25, 2024

Regarding (1), I checked and nvCOMP v4.0.0 packages for windows do have "include" directories.
Regarding (2), we are actively looking at fixing this. The debug + static linking issue is acknowledged and is being looked at. @VasuAgrawal can you please provide more information regarding the crash when using it in static + release mode?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants