|
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.
more
|
|
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.
more
|
Why is the binary package putting all the DLLs in the gnucash folder?
Related Questions
- Further information of the question: I invest in a security which issues ReturnOfCapital, which in Canada ...
- Yes, you can install the newer windows binary (say, 2.2.1) directly on top of the older one (say, 2.2.0). You ...
- Yes. Many of the developers hang out on icq in the #gnucash discussion on irc.gnome.org. Also, there is a ...
- The core functionality of GnuCash is written in C, but do not forget that much of this can be accessed ...
- Ask nicely. :-) You can file an enhancement request at Bugzilla. Please bear in mind to describe your ...