Am 29.08.2017 um 14:16 schrieb Harald Sitter:
> On Thu, Aug 24, 2017 at 3:20 PM, Ralf Habacker
> wrote:
>> 10. The conclusion of 9. is that it might also be a solution on windows
>> to patch only all generated files after 3. and before 4.
> Hm, I may be missing a piece of the puzzle in my mind, b
Am 29.08.2017 um 15:03 schrieb Harald Sitter:
> On Sun, Aug 27, 2017 at 8:37 PM, Luigi Toscano
> wrote:
>> Even without the if branch it would be still complicated.
> Ah! I think I get the complexity now. At build time we need to run our
> tools already and so the dtd/xsl need to be able to resol
On Sun, Aug 27, 2017 at 8:37 PM, Luigi Toscano wrote:
> Even without the if branch it would be still complicated.
Ah! I think I get the complexity now. At build time we need to run our
tools already and so the dtd/xsl need to be able to resolve the paths,
hence the initial configure_file with abs
On Thu, Aug 24, 2017 at 3:20 PM, Ralf Habacker wrote:
> 10. The conclusion of 9. is that it might also be a solution on windows
> to patch only all generated files after 3. and before 4.
Hm, I may be missing a piece of the puzzle in my mind, but it appears
to me this should be working with the cm
Harald Sitter wrote:
> On Tue, Aug 22, 2017 at 10:18 PM, Luigi Toscano
> wrote:
>> Harald Sitter wrote:
>>> The reason this puzzles me is that the relocatable code for Windows
>>> would work just fine for Linux and OSX, from what I can tell there is
>>> no real downside to it besides the addition
Am 23.08.2017 um 14:15 schrieb Harald Sitter:
> On Tue, Aug 22, 2017 at 10:47 PM, Ralf Habacker
> wrote:
>> Hi,
>>
>> I'm using the following patch to cross build kdoctools for windows
>>
>> https://build.opensuse.org/package/view_file/home:rhabacker:branches:windows:mingw:win32:KF536/mingw32-kdoc
On Tue, Aug 22, 2017 at 10:47 PM, Ralf Habacker
wrote:
> Hi,
>
> I'm using the following patch to cross build kdoctools for windows
>
> https://build.opensuse.org/package/view_file/home:rhabacker:branches:windows:mingw:win32:KF536/mingw32-kdoctools/0001-Generate-xml-files-containing-relative-pathe
On Tue, Aug 22, 2017 at 10:18 PM, Luigi Toscano
wrote:
> Harald Sitter wrote:
>> Ahoy ahoy
>>
>> I've just stumbled upon a rather puzzling situation with kdoctools. It
>> has code branching to turn its assets relocatable [1] (i.e. resolve
>> paths relative rather than hardcode their location). Now
Hi,
I'm using the following patch to cross build kdoctools for windows
https://build.opensuse.org/package/view_file/home:rhabacker:branches:windows:mingw:win32:KF536/mingw32-kdoctools/0001-Generate-xml-files-containing-relative-pathes-to-dtd.patch?expand=1
It requires only a little platform spec
Harald Sitter wrote:
> Ahoy ahoy
>
> I've just stumbled upon a rather puzzling situation with kdoctools. It
> has code branching to turn its assets relocatable [1] (i.e. resolve
> paths relative rather than hardcode their location). Now the weird bit
> about this is that it is only used on windows
On Tue, Aug 22, 2017 at 11:32 AM, Ben Cooksley wrote:
> On Tue, Aug 22, 2017 at 9:25 PM, Harald Sitter wrote:
>> Ahoy ahoy
>
> Hi Harald,
>
>>
>> I've just stumbled upon a rather puzzling situation with kdoctools. It
>> has code branching to turn its assets relocatable [1] (i.e. resolve
>> paths
On Tue, Aug 22, 2017 at 9:25 PM, Harald Sitter wrote:
> Ahoy ahoy
Hi Harald,
>
> I've just stumbled upon a rather puzzling situation with kdoctools. It
> has code branching to turn its assets relocatable [1] (i.e. resolve
> paths relative rather than hardcode their location). Now the weird bit
>
Ahoy ahoy
I've just stumbled upon a rather puzzling situation with kdoctools. It
has code branching to turn its assets relocatable [1] (i.e. resolve
paths relative rather than hardcode their location). Now the weird bit
about this is that it is only used on windows.
The reason this puzzles me is
13 matches
Mail list logo
