Review Request 117011: Use bin/../share on Windows as a workaround
Aleix Pol Gonzalez
aleixpol at kde.org
Mon Mar 24 00:16:38 UTC 2014
> On March 23, 2014, 11:51 p.m., Aleix Pol Gonzalez wrote:
> > So what should happen so that we didn't need the workaround?
>
> Alexander Richardson wrote:
> QStandardPaths would have to look in %KDEROOT%\share and not just C:\ProgramData.
So why aren't we adding this in Qt? Or even, why are we installing documentation in share/ if it doesn't make sense on Windows?
- Aleix
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117011/#review53878
-----------------------------------------------------------
On March 23, 2014, 11:28 p.m., Andrius da Costa Ribas wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/117011/
> -----------------------------------------------------------
>
> (Updated March 23, 2014, 11:28 p.m.)
>
>
> Review request for KDE Frameworks and kdewin.
>
>
> Repository: kdoctools
>
>
> Description
> -------
>
> This is a workaround for kdoctools for the same problem discussed in review #115210. In particular, emerge installs docbook-dtd data under %KDEROOT%\share.
>
>
> Diffs
> -----
>
> src/xslt.cpp db67599
>
> Diff: https://git.reviewboard.kde.org/r/117011/diff/
>
>
> Testing
> -------
>
> Tested using MSVC 2013. KJsEmbed, which depends on this, builds after this patch (KJsEmbed still has an unrelated problem on install step).
>
>
> Thanks,
>
> Andrius da Costa Ribas
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140324/38c3f31c/attachment-0001.html>
More information about the Kde-frameworks-devel
mailing list