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

Fix extract_all_objects for custom targets with VS backend #8211

Conversation

vvainola
Copy link
Contributor

@vvainola vvainola commented Jan 16, 2021

  • Changed the object names built from generated sources on VS backend
    to match filenames used in ninja backend

fixes #8020

@vvainola vvainola requested a review from jpakkane as a code owner January 16, 2021 13:30
@vvainola vvainola force-pushed the fix_extract_objects_for_VS_backend branch from 36baeda to 6bb946a Compare January 16, 2021 14:40
- Changed the object names built from generated sources on VS backend
to match filenames used in ninja backend
@vvainola vvainola force-pushed the fix_extract_objects_for_VS_backend branch from 6bb946a to bc6f05e Compare January 16, 2021 14:44
@vvainola
Copy link
Contributor Author

vvainola commented Jan 16, 2021

How to fix the unity builds?

@CoffeeFlux
Copy link
Contributor

Would love to see this land - any chance of re-running the lanes so I can see the failure?

@jpakkane
Copy link
Member

There does not seem to be a button for that so it would need a rebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

extract_all_objects() with custom target results in invalid paths for subproject with Visual Studio backend
3 participants