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

Generate and build with Visual Studio 2019 GUI #133

Open
inkydragon opened this issue May 24, 2021 · 1 comment
Open

Generate and build with Visual Studio 2019 GUI #133

inkydragon opened this issue May 24, 2021 · 1 comment

Comments

@inkydragon
Copy link
Contributor

I mean that the VS 2019 project can be generated by meson --backend=vs2019, and then compiling and debugging using its GUI.

The output VS 2019 project files still have some bugs, here are some workarounds:

  1. Generate VS 2019 project: meson -Ddefault_library=static --force-fallback-for=zlib,harfbuzz,freetype2,fribidi,libpng -Dfreetype2:harfbuzz=disabled -Dharfbuzz:freetype=disabled -Dharfbuzz:cairo=disabled -Dharfbuzz:glib=disabled -Dharfbuzz:gobject=disabled --backend=vs2019 build-vs2019
  2. Replace some path: Replace "subprojects\ffmpeg => "..\..\subprojects\ffmpeg in all *.vcxproj files in the build directory (build-vs2019\).
    In my case: 136 times to replace in 6 files (build-vs2019-test\subprojects\ffmpeg\8fd69c1@@????@sta.vcxproj)
  3. Open Aegisub.sln and build

All those wrong paths in step 2 are using by CustomBuild, source files usually are *.asm.
Maybe is an upstream bug about custom build.

@CoffeeFlux
Copy link
Member

It's an issue in Meson itself, reported here: mesonbuild/meson#8020

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