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

Be less strict about FixFwData name and location #410

Merged
merged 2 commits into from
Oct 22, 2024

Conversation

rmunn
Copy link
Contributor

@rmunn rmunn commented Oct 22, 2024

Fix #409.

On Linux, dotnet compiles binaries to filenames without .exe in them, so we should handle that scenario gracefully. Also, it's common to be running from a different directory than the one where FixFwData.exe is found (e.g., dotnet run in the project that calls LfMergeBridge), so we should also check the location of LfMergeBridge.dll since FixFwData will usually be installed alongside LfMergeBridge.dll.


This change is Reviewable

On Linux, dotnet compiles binaries to filenames without .exe in them, so
we should handle that scenario gracefully. Also, it's common to be
running from a different directory than the one where FixFwData.exe is
found (e.g., `dotnet run` in the project that calls LfMergeBridge), so
we should also check the location of LfMergeBridge.dll since FixFwData
will usually be installed alongside LfMergeBridge.dll.
@rmunn rmunn requested a review from hahn-kev October 22, 2024 06:19
@rmunn rmunn self-assigned this Oct 22, 2024
@rmunn rmunn merged commit 6f825b2 into develop Oct 22, 2024
8 of 9 checks passed
@rmunn rmunn deleted the bug/less-strict-fixfwdata-location branch October 22, 2024 07:18
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.

LfMergeBridge is too picky about location and filename of FixFwData.exe
2 participants