[rkward-devel] Windows packaging

[Prasenjit Kapat]

Hi,

Sorry for the delay, I am not getting much time these days...

On Tue, Oct 26, 2010 at 2:48 AM, Thomas Friedrichsmeier
<thomas.friedrichsmeier at ruhr-uni-bochum.de> wrote:
>>> yes and no. libstdc++ is certainly needed (by all KDE apps), but it should
>>> already be included in the Qt / and or KDE libraries. Either this is not the
>>> case on your system,

libstdc++ is NOT included in either of the two KDE installations on my
machine! Yet, kwrite.exe / konqueror.exe starts up fine (dolphin.exe
does start but gives some error of not being able to launch
klauncher).

On my system libstdc++ is only present in C:\MinGW\bin. Where is it on
your system?

(For compiling, my kde is in D:\KDE4 and for RKWard packaging, kde is
in D:\RKWard_packaging\RKWard\KDE .)

>>> or MinGW somehow thought it was a good idea to link
>>> against libstdc++ dynamically, in addition to that.

I guess this is the case.

>>> Which version of GCC is this? I used 4.4.0.
>> Mine's 4.5.0 (as seen from g++.exe --version). Should a different
>> version matter? After all the compilation was done with this MinGW as
>> well. Note: C:\MinGW\bin is not in my %PATH%, I only add it in the
>> make_release.bat file.
>
> I would be surprised, if it matters, but I'm trying to spot differences. So
> here's one that we could revisit, later.

Yes, something that I'll have to comeback to and try.

> Not having C:\MinGW\bin in the %PATH% should not be the problem, or at least,
> if it was, the installer as compiled on my computer would not work on yours,
> either.

If I add the following to rkward.bat

SET OLD_PATH=%PATH%
SET PATH=C:\MinGW\bin;%PATH%

[.. actual part of rkward.bat ..]

SET PATH=%OLD_PATH%

Then, rkward does start.

>> The directory is fine as well - rkward.bin.exe is in
>> D:\RKWard_package\RKWard\KDE\bin which is where all the libkde* exist.
>
> Just for testing: Does it work, if you install to the KDE-installation you
> used for building, instead? If it does, then we'll know we should look out for
> problems with the KDE installation rather than the build.

No, the error is same, it is still looking for libstdc++

>> Here, I've a question. For packaging, I installed the "end user" (not
>> the "package manager") version of KDE (mingw flavor). I only checked
>> kdebase-apps (Bin) and let it install the dependencies. Is that OK?
>
> Yes, that should do the trick. To make sure you really got the correct flavor,
> take a look at the "manifest"-directory in there. This should contain kdelibs-
> mingw4-4.4.x-bin.mft, among many others. Looking in mine, I see that I have
> kdewin-mingw4-4.3.2-bin.mft, however that got there. I guess you will have
> kdewin-mingw4-0.5.2-bin.mft, instead? Might be something to look at, too, but
> I don't think it's the cause of the problem.

Yes, I do have, kdewin-mingw4-0.5.2-bin.mft

-- 
Prasenjit