Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why is the binary package putting all the DLLs in the gnucash folder?

0
10 Posted

Why is the binary package putting all the DLLs in the gnucash folder?

0

This is caused by a fundamental technical fault of the MS Windows operating system. Gnucash depends on approx. 50 other DLLs. We don’t know whether any of those happen to exist already in your windows/system32 folder. If they did, the are probably vitally important for some other application on your computer and must not be replaced by the version that is required by and shipped with gnucash. If gnucash had overwritten an existing DLL in your windows folder, this would have killed that other application. This should better be avoided, and on MS Windows the only possible way to really avoid crashing your other existing application unfortunately requires shipping our own DLL into our own Program folder of gnucash. That’s the reason.

0

Gnucash depends on approximately 50 other DLLs. We don’t know whether any of those happen to exist already in your %windir%\system32 folder. To avoid interfering with programs depending on different versions of these DLLs, we write all the DLLs into our own folder.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.