You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after updating to v63.0 using Windows weasyprint.exe I get 4 error popups:
The procedure entry point g_bookmark_file_copy could not be located in the dynamic link library
C:\Users<..>\AppData\Local\Temp_MEI351522\libgobject-2.0-0.dll
click OK
The procedure entry point g_once_init_enter_pointer could not be located in the dynamic link library
C:\Users<..>\AppData\Local\Temp_MEI351522\libpango-1.0-0.dll
click OK
The procedure entry point DllMain could not be located in the dynamic link library
C:\Users<..>\AppData\Local\Temp_MEI351522\libharfbuzz-0.dll
1 more
Still the PDF is being generated.
I get this also for weasyprint.exe call w/o arguments.
Thanks,
Daniel
The text was updated successfully, but these errors were encountered:
Hi Guillaume, yes, I have GTK3 runtime installed that apparently has some pango dlls installed AND is part of my PATH environment variable. I did not add this manually. As far as I can tell this was installed and configured by either GIMP, Inkscape or Spyder (Python framework).
Ideally weasyprint would prioritize the dlls it is supposed to use. Do I understand correctly weasyprint.exe extracts the dll's to a temporary directory?
Hi all,
after updating to v63.0 using Windows weasyprint.exe I get 4 error popups:
The procedure entry point g_bookmark_file_copy could not be located in the dynamic link library
C:\Users<..>\AppData\Local\Temp_MEI351522\libgobject-2.0-0.dll
click OK
The procedure entry point g_once_init_enter_pointer could not be located in the dynamic link library
C:\Users<..>\AppData\Local\Temp_MEI351522\libpango-1.0-0.dll
click OK
The procedure entry point DllMain could not be located in the dynamic link library
C:\Users<..>\AppData\Local\Temp_MEI351522\libharfbuzz-0.dll
Still the PDF is being generated.
I get this also for weasyprint.exe call w/o arguments.
Thanks,
Daniel
The text was updated successfully, but these errors were encountered: