Join GitHub today
[xbmc][fix] Fix on demand dll loading to point to the correct files #10155
@Paxxi don't know if caused by this one, but when debugging on Windows when building to a custom path, cpluff.dll is tried to be loaded at the wrong place.
Loading all the rest works and load dlls from the main kodi directory but cpluff.dll seems to be loaded from portable_directory/..
@Paxxi ok no in fact it's the xbmcbin globally that point to KODI_HOME even when forcing a working folder.
Migrating KODI_HOME to the working dir solve that issue but seems to cause a lot of others :(
Issue is a mix between portable mode / working directory in debug settings and KODI_HOME.
Maybe this have changed on another PR and there's just need to have some updates of Wiki to reflect how to handle that ?
There's been a lot of volatility in this area the last week as one major change led to many things being overlooked and issues popping up all over the place.
Wiki is not updated as no changes are meant to be required by someone opening up the solution and trying to debug.
To get this working with the dlls in the system folder we play some tricks and add system to the path for dll resolution during debugging. This fails for some files currently it seems and I'll get it sorted sometime this week.
As a workaround just copy cpluff.dll into the root folder and it should work.
Ok thanks, that's what I ended up doing. (All the ones from DllPaths_win32.h as curl is also needed and in my case nfs too).
Just for information since maybe I do things wrong and -p is not the solution, but how are we supposed to manage multiple debugging Kodi profiles for different Kodi versions ? (Like when working on different branches to update previous PR / backport)
Edit : To avoid spam : Ok thanks, so will continue -p as this is what I master for the 12 other production Kodi to test the client side ;)