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

Loader shared lib: back to default cmake prefix #606

Merged
merged 1 commit into from
Jun 24, 2021

Conversation

xantares
Copy link
Contributor

@xantares xantares commented Jun 17, 2021

#595 restores the default lib prefix for mingw (libvulkan-1.dll instead of vulkan-1.dl) and basically reverts #523
but it changes the import lib name (libvulkan.dll.a instead of libvulkan-1.dll.a) and breaks cmake detection in FindVulkan
(find_library looks for libvulkan-1.dll.a under mingw)
now we go back to using the default cmake prefix which is equivalent to the #595 prefix prior to #523
without the broken import lib name

cc @Biswa96

@ci-tester-lunarg
Copy link

Author xantares not on autobuild list. Waiting for curator authorization before starting CI build.

@Biswa96
Copy link
Contributor

Biswa96 commented Jun 17, 2021

Oh! I didn't know that. Apology for that 🙇

@lenny-lunarg
Copy link
Contributor

So the way this has been going back and forth makes we think we need to figure out something a little better. Our policy has been that we don't officially support MinGW, but we'll take PRs if people want to make them. As a result, I've mostly just been making sure the changes don't break MSVC/gcc/clang and agreeing to them otherwise. But since this has been going back and forth, it makes we think this approach might not be the best.

I could ping the two of you when we have something mingw-related, but that does somewhat obligate the two of you to reply. Alternatively, we could add add a job to our github actions CI to see if things are likely to break. If we did that I'd probably want to mark is as a job that's allowed to fail and we just ping you guys if we know we're going to break things.

Does anything like that sound reasonably? I just don't like this back and forth that's been going on.

@Biswa96
Copy link
Contributor

Biswa96 commented Jun 17, 2021

IMO, adding a little comment in that cmake file would help in future. BTW, as it turns out file naming is important here, it may be possible to check the file names after build and install in CI. I am not familiar with CI, just little thought.

@lenny-lunarg
Copy link
Contributor

IMO, adding a little comment in that cmake file would help in future.

@lenny-lunarg
Copy link
Contributor

IMO, adding a little comment in that cmake file would help in future.

That's good point. Maybe we just need to properly document why it ended up this way and what to watch out for.

@ci-tester-lunarg
Copy link

CI Vulkan-Loader build queued with queue ID 4068.

@ci-tester-lunarg
Copy link

CI Vulkan-Loader build # 468 running.

@ci-tester-lunarg
Copy link

CI Vulkan-Loader build # 468 passed.

@ci-tester-lunarg
Copy link

Author xantares not on autobuild list. Waiting for curator authorization before starting CI build.

@xantares
Copy link
Contributor Author

ok I added some comments, feel free to ping me for mingw stuff

but it changed the import lib name (libvulkan.dll.a instead of libvulkan-1.dll.a) which in turns breaks cmake detection in FindVulkan
now we go back to using the default cmake prefix which is equivalent to what KhronosGroup#595 wants, (prior to KhronosGroup#523), but without the broken behavior

cc @Biswa96
@ci-tester-lunarg
Copy link

Author xantares not on autobuild list. Waiting for curator authorization before starting CI build.

@xantares
Copy link
Contributor Author

everything should be ready @lenny-lunarg

Copy link
Collaborator

@charles-lunarg charles-lunarg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comment definitely helps clarify what should be the output of the build script.
While it'd be nice to have builds of this setup, I think simply deferring expertise and taking PR's that fix whatever issues that arise are an adequate solution.

else()

# when adding the suffix the import and runtime library names must be consistent
# mingw: libvulkan-1.dll.a / libvulkan-1.dll
Copy link

@SpaceIm SpaceIm Sep 2, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't it defeat the purpose of #523?

which was:

# mingw: libvulkan-1.dll.a / vulkan-1.dll

Why?

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.

None yet

6 participants