There was a lot of trouble yesterday. I made a mistake and therefore the apps were crashing on startup because of missing msvc debug runtime libs. I've now added a new package 'msvc8-runtime-msvc' to address this issue.
And I've also uploaded a new version of the installer (0.8.0-2) to hopefully fix crashes on startup. There's also a version which is not packed with upx - maybe upx is the problem here...
I've also added some new questions to my last blog entry. If you still have problems, plz ask at #kde-windows or our mailing list. I'm now doing some geocaching so I can fix the installer dep problem this evening :)
Samstag, 20. Oktober 2007
Freitag, 19. Oktober 2007
kde4 / win32 beta3 binary packages available
They're finally released :)
I uploaded them this morning, but then I realized that the installer does not show them... so we had to fix the installer. Ralf then found another quick fix for the problem on the server side (our parser had problems with spaces in the path) and simply renamed the path.
Ralf did not told it to me and therefore the packages were released and I did not knew about :-D
Nevertheless I also fixed the installer and uploaded a new version (0.8.0-2) which you can grab here.
Here are some questions you might have when you're trying to install the packages:
Q: Why does the packager also downloads a lot of packages I did not select?
A: In contrast to linux there're no 'system' libs like libpng, libjpeg, ... available for windows. But they're needed by kde4 and therefore we packaged them too.
Q: Why does the kdewin-installer installs the 'Microsoft Visual Redistributable Package' every time?
A: Our installer is not complete yet and lacks support for 3rd-party binary installers. Therefore it can't know if this package is already installed or not
Q: I can't start an application because of missing dll's / crashes on startup
A: The problem is that some dll's are in kde\lib instead kde\bin. We already moved a lot to bin but get not ready for beta3. For now simply add kde\lib to your PATH environment variable
Q: Why does pop up a command line window named 'dbus-daemon' every time I start a kde app?
A: DBus is one of our bleeding edges and we had no time to make this app run as a service.
Q: An application is crashing - what should I do?
A: There are a lot of bugs in kdelibs4/win32 which can lead to a crash. Try to reproduce the crash on linux. If it's crashing there too, report the bug to bugs.kde.org. If you can't test on linux, also report to bugs.kde.org :)
Q: Hey your crap is constantly crashing - and this is named 'beta3'???
A: Although it's beta3, the platform specific source for windows is in early alpha stage. We currently plan a release for windows which can be called beta in the timeframe of kde 4.1. This is mostly due to lack of time from our site (we're all not paid for this work and do this in our free time)
Q: I get 'The program can not initialized correctly ...'
A: M$ is stupid. They do not ship the debug runtime with their vcredist package and therefore you can't start an application (you need to have VS 2005 SP1 installed). We're working on a solution.
Q: Why are there no packages for mingw?
A: I did not see a reason for this in this early phase of kde4/win32. The end user doesn't care and a developer should compile kde for themself. If you've problems compiling kde4 on windows, join #kde-windows and ask for help. There're outdated mingw binaries available for download. I don't suggest using them.
Q: My applications are crashing on startup!
A: I only tested the apps on my development system. Therefore some libs were available which you normally does not find on an end-user system. We've uploaded a new package named 'msvc8-runtime-msvc' in kdesupport section. After installing this package, all apps should start. If not let us know (#kde-windows or kde-windows@lists.kde.org)
Q: There are still missing libraries!
A: Our dependency system is not bug-free yet. Therefore sometimes the packager does not select all needed packages. You need at least all packages in win32libs and all packages in kdesupport.
And now start downloading and enjoy! :)
I uploaded them this morning, but then I realized that the installer does not show them... so we had to fix the installer. Ralf then found another quick fix for the problem on the server side (our parser had problems with spaces in the path) and simply renamed the path.
Ralf did not told it to me and therefore the packages were released and I did not knew about :-D
Nevertheless I also fixed the installer and uploaded a new version (0.8.0-2) which you can grab here.
Here are some questions you might have when you're trying to install the packages:
Q: Why does the packager also downloads a lot of packages I did not select?
A: In contrast to linux there're no 'system' libs like libpng, libjpeg, ... available for windows. But they're needed by kde4 and therefore we packaged them too.
Q: Why does the kdewin-installer installs the 'Microsoft Visual Redistributable Package' every time?
A: Our installer is not complete yet and lacks support for 3rd-party binary installers. Therefore it can't know if this package is already installed or not
Q: I can't start an application because of missing dll's / crashes on startup
A: The problem is that some dll's are in kde\lib instead kde\bin. We already moved a lot to bin but get not ready for beta3. For now simply add kde\lib to your PATH environment variable
Q: Why does pop up a command line window named 'dbus-daemon' every time I start a kde app?
A: DBus is one of our bleeding edges and we had no time to make this app run as a service.
Q: An application is crashing - what should I do?
A: There are a lot of bugs in kdelibs4/win32 which can lead to a crash. Try to reproduce the crash on linux. If it's crashing there too, report the bug to bugs.kde.org. If you can't test on linux, also report to bugs.kde.org :)
Q: Hey your crap is constantly crashing - and this is named 'beta3'???
A: Although it's beta3, the platform specific source for windows is in early alpha stage. We currently plan a release for windows which can be called beta in the timeframe of kde 4.1. This is mostly due to lack of time from our site (we're all not paid for this work and do this in our free time)
Q: I get 'The program can not initialized correctly ...'
A: M$ is stupid. They do not ship the debug runtime with their vcredist package and therefore you can't start an application (you need to have VS 2005 SP1 installed). We're working on a solution.
Q: Why are there no packages for mingw?
A: I did not see a reason for this in this early phase of kde4/win32. The end user doesn't care and a developer should compile kde for themself. If you've problems compiling kde4 on windows, join #kde-windows and ask for help. There're outdated mingw binaries available for download. I don't suggest using them.
Q: My applications are crashing on startup!
A: I only tested the apps on my development system. Therefore some libs were available which you normally does not find on an end-user system. We've uploaded a new package named 'msvc8-runtime-msvc' in kdesupport section. After installing this package, all apps should start. If not let us know (#kde-windows or kde-windows@lists.kde.org)
Q: There are still missing libraries!
A: Our dependency system is not bug-free yet. Therefore sometimes the packager does not select all needed packages. You need at least all packages in win32libs and all packages in kdesupport.
And now start downloading and enjoy! :)
Donnerstag, 18. Oktober 2007
Small delay for kde4/beta3 packages for windows
Yesterday evening I found a bug in kstars which cause a crash on startup. Because I want to have a working kstars application in kdeedu package, I decided to do some investigation on this problem. After some debugging I could fine the problem and added a workaround (although a separated thread would be better there, I'll see if I find some time for this). Later this evening I had not time the rebuild the beta3 package for kdeedu 'cause I wanted to cheer my girlfriend on her table tennis match. Sadly it did not help much... :( We arrived back home one o'clock this morning and I initiated the packaging process hoping all compiles fine.
This morning I learned that I should never hope that something runs smoothly until it really worked - somehow the emerge script fetched an old header... this means that I've to restart with kdeedu this evening and after uploading all the stuff I'll let you know how to get the packages (and what to do to get it running)
This morning I learned that I should never hope that something runs smoothly until it really worked - somehow the emerge script fetched an old header... this means that I've to restart with kdeedu this evening and after uploading all the stuff I'll let you know how to get the packages (and what to do to get it running)
Dienstag, 2. Oktober 2007
Still not released a snapshot of kde4/win32
I'm sorry but I still had no time to release a snapshot of kde4/win32.
There were two big problem I hit before I could even think of trying to compile kdelibs with our emerge-scripts.
The first one was Qt - looks like nobody ever did a 'make install' with Qt on windows. After five mails to qt-bugs I ended up with four public
four public task-tracker entries with no priorty... :(
At least qt now install all things correct with my local patches.
The second one was CLucene. As this dependency is now mandatory for strigi and soprano, I had to find out a way to compile it on win32. Thx to cmake a (more or less) small cmake script helped here. Now it compiled fine with msvc and this normally implies that it's no problem to get it compiling with mingw too. This was a big misapprehension (and a good example how not to write platform independend code). clucene-config.h is needed for mingw...
After adding ~60 configure-checks and a lot of iterations trying to compile strigi/soprano it finally worked.
This means that I can now start compiling kdelibs on windows but I wonder if I should wait for beta3.
There were two big problem I hit before I could even think of trying to compile kdelibs with our emerge-scripts.
The first one was Qt - looks like nobody ever did a 'make install' with Qt on windows. After five mails to qt-bugs I ended up with four public
four public task-tracker entries with no priorty... :(
At least qt now install all things correct with my local patches.
The second one was CLucene. As this dependency is now mandatory for strigi and soprano, I had to find out a way to compile it on win32. Thx to cmake a (more or less) small cmake script helped here. Now it compiled fine with msvc and this normally implies that it's no problem to get it compiling with mingw too. This was a big misapprehension (and a good example how not to write platform independend code). clucene-config.h is needed for mingw...
After adding ~60 configure-checks and a lot of iterations trying to compile strigi/soprano it finally worked.
This means that I can now start compiling kdelibs on windows but I wonder if I should wait for beta3.
Abonnieren
Posts (Atom)