< Talk:Installing third party softwares in terminal/Build/KDE4 | WindowsRevision as of 10:08, 15 November 2007 by Skierpage (talk | contribs) (Oddness?)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) please add some more things in the article... Oddness? I added to the article. I don't understand the comment about "emerge is mostly usable together with the kdewin-installer". I've used the latter to install stuff to C:\KDE4, but I'm using emerge in C:\kderoot. It doesn't seem to have any dependencies on kdewin-installer, are you saying that it can reuse those packages or the same bin directory? If so presumably I need to make my emerge DOWNLOADDIR (default C:\distfiles) match my kdewin-installer "package download path" I noticed that kderoot\bin had libeay32.dll, libiconv2.dll, libintl3.dll, ssleay32.dll before the win32libs step, but that adds new versions of these to bin. I notice that kderoot\tmp had 561 MB of stuff in it, can this be removed? kdesettings.bat is not adding KDEROOT\bin and KDEROOT\lib to my PATH, it's some weirdness with the if test in the batch file. -- Skierpage 11:08, 15 November 2007 (CET) Retrieved from "https://techbase.kde.org/index.php?title=Talk:Installing_third_party_softwares_in_terminal/Build/KDE4/Windows/emerge&oldid=16296" Content is available under Creative Commons License SA 4.0 unless otherwise noted.