[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: Krita 2.4 - Windows: how to report bugs?
From:       Boudewijn Rempt <boud () valdyas ! org>
Date:       2011-12-23 8:13:17
Message-ID: 201112230913.17098.boud () valdyas ! org
[Download RAW message or body]

On Friday 23 December 2011 Dec, Dotan Cohen wrote:
> On Thu, Dec 22, 2011 at 21:12, Boudewijn Rempt <boud@valdyas.org> wrote:
> > On windows, you need to have a full debug-build stack -- i.e., you cannot mix a \
> > release-build of libc with a debug-build of krita. The app simply wouldn't start. \
> > And Microsoft in their license agreement for msvc explicitly forbids the \
> > redistribution of debug builds of their libc and libc++ equivalents. 
> > It's a huge pain, and the reason for mozilla's breakpad thing, in fact.
> > 
> 
> That is ridiculous. What are they trying to protect?

The user, apparently... That's the reason they give.

> 
> If I have msvc then I could build a debug Krita, no?

Right.

> I understand that
> building Krita is a pain, but it might be worthwhile if a Windows dev
> were to write a script for building Krita with a local msvc for those
> who would like to test debug builds.
> 
> I know nothing about Windows, but I'll give it a try if whoever
> compiled the current Krita / Caligraphy build would share their
> resources with me.


These are the notes Stuart created while building the packages:


http://community.kde.org/Calligra/Building_Calligra_on_Windows

Note that for a debug build, you have to set that correctly in the emerge settings. \
This is useful background information: \
http://techbase.kde.org/Projects/KDE_on_Windows.


-- 
Boudewijn Rempt
http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl
_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop


[prev in list] [next in list] [prev in thread] [next in thread]