Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Build Target Conflicts #34

Closed
SkyeHoefling opened this issue Sep 15, 2021 · 0 comments · Fixed by #33
Closed

Build Target Conflicts #34

SkyeHoefling opened this issue Sep 15, 2021 · 0 comments · Fixed by #33

Comments

@SkyeHoefling
Copy link
Contributor

SkyeHoefling commented Sep 15, 2021

Description

When using multiple FileOnQ imaging libraries in the same downstream project there are naming conflicts with build targets for net48. This is because both FileOnQ.Imaging.Heif and FileOnQ.Imaging.Raw use the same build <Target> name of CopyNativeDlls.

The conflict prevents native assemblies from being copied to the bin directory correctly. This will create a silent error as the build will not fail and the application will have a runtime error.

Proposed Solution

Make the build target names unique

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant