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
I installed the lib gtkmm and run asample program from the manual (base.cc). A run-time error occurred because the dll pangomm called the function wrap_register from glibmm which has a static variable wrap_func_table but because pangomm has its own copy not initialized a run-time error occurs when this variable is referenced in wrap_register.
How can I solve this problem ? I hoped vcpkg would solve these kind of linking issues automatically.
The text was updated successfully, but these errors were encountered:
Ok, thanks. I expect the same problem not only for pangomm.dll but also for the atkmm.dll.
Were these dll statically compiled with glibmm, so that the functions were included in the dlls ?
Sent from Mail for Windows 10
From: Norbert Nemec
Sent: Saturday, 25 May 2019 18:40
To: microsoft/vcpkg
Cc: JacqKrol; Author
Subject: Re: [microsoft/vcpkg] Problem with shared static variable between dll(#6550)
I think I have a fix already - going to prepare a PR
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
The problem was that since #5937 glibmm could only be built as static library but atkmm, pangomm and gtkmm each can only be linked as dynamic libary, leading to up to three copies of the glibmm static data in one executable. My fix reverts that change so that glibmm is also built as dynamic libary.
I installed the lib gtkmm and run asample program from the manual (base.cc). A run-time error occurred because the dll pangomm called the function wrap_register from glibmm which has a static variable wrap_func_table but because pangomm has its own copy not initialized a run-time error occurs when this variable is referenced in wrap_register.
How can I solve this problem ? I hoped vcpkg would solve these kind of linking issues automatically.
The text was updated successfully, but these errors were encountered: