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

Building on Windows 10 x64 with Visual Studio 2019 #11

Closed
jonnor opened this issue Aug 27, 2020 · 3 comments
Closed

Building on Windows 10 x64 with Visual Studio 2019 #11

jonnor opened this issue Aug 27, 2020 · 3 comments

Comments

@jonnor
Copy link

jonnor commented Aug 27, 2020

Hi,
thank a lot for this open implementation of PEAQ! It built, installed and ran without issues on my Arch Linux system.

However on Windows 10 with Visual Studio 2019 I had a couple of minor issues. I installed Gstreamer 1.x for x64 per the instructions. Then when using the provided Visual Studio files from git (develop branch), I got the following issues.

  • Had to use Retarget Solution to updated to a C runtime that was installed with VS code. v142 in my case
  • Compile errors due to gstreamer/glib header files not found. Turns out default build config is win32, and will then only look for 32bit gstreamer headers. Changing Target Platform in Visual Studio to x64 made things compile.
  • Linker errors in msvcrt. To fix this I added ucrt.lib and vcruntime.lib to the linker config. Some random forum post says this is expected VS versions post 2015. This made the .dll and .exe link correctly.
  • Now got issue that the peaq Gstreamer element was not found, despite using --gst-plugin-load. To fix, renamed gstpeaq-1.0 to gstpeaq.dll - as per A confusing execute error  #7 (comment)

I have made the Visual Studio changes in this branch: https://github.com/jonnor/gstpeaq/tree/fix-build-vs2019
Not sure it is pull request quality, but hopefully it can be useful for others along with the hints in this post.

@martinholters
Copy link
Member

I've left a comment over there re. the 64bit thing.

I think it would be best to just remove the GStremer-0.10 stuff and then drop the -1.0 suffix everywhere, making the renaming unnecessary. But even without that, if you go over INSTALL.Windows to update the required versions (and fix what you spot otherwise) and double-check the 32bit/64bit thing, I'd be happy to receive a PR.

@martinholters
Copy link
Member

I believe this is fixed by #16 and moreover, as the Windows build is now tested as part of CI, it hopefully shouldn't regress.
Please comment if any issues remain.

@jonnor
Copy link
Author

jonnor commented Mar 11, 2021 via email

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

No branches or pull requests

2 participants