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

List:       kde-windows
Subject:    Re: Binary factory for RKWard
From:       Hannah von Reth <vonreth () kde ! org>
Date:       2018-03-27 11:49:45
Message-ID: 356ea173-c4bf-223c-e224-5c7d83473975 () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/mixed)]


A source compilation would probably got to libs.

Yes the binary would go to

binary/_mac/r-base/

make sure to create the correct info.ini in that folder.

The signtool issue needs to be fixed yes.
You are the first one using mingw :) .


On 27/03/2018 13:38, Thomas Friedrichsmeier wrote:
> Hi,
>
> On Tue, 27 Mar 2018 12:50:03 +0200
> Hannah von Reth <vonreth@kde.org> wrote:
>> Hi the branch is merged now so you should be able to work directly on
>> master.
> And I see you already fixed the depends and triggered a build. Thanks!
> Unfortunately it fails at the very last minute:
>
> ----
> executing command: signtool.exe sign /v /n K Desktop Environment
> e.V. /tr http://timestamp.digicert.com /td SHA256 /fd SHA256 /a
> C:\Craft\BinaryFactory\windows-mingw_64-gcc\tmp\*.exe
>
> 'signtool.exe' is not recognized as an internal or external command,
> ----
>
>> I'd recommend to compile r-base somehow tell people to install r-base
>> them selves.
> Well, yes that does not even seem to be hard to do on Mac, but it would=

> mean that no pre-compiled add-ons will be installable, later. Ok for
> some users, not for others.
>
>> I think packagin a dmg isn't that easy but I have no experience with
>> it.
> I'll look into that. In either case I'm going to have to provide some
> Mac special casing. _If_ I get a dmg installer to work, that would now
> go into binary/_mac/r-base/, right? If I go for source compilation,
> should r-base be moved to dev-util, or is there a better category?
>
> Regards
> Thomas



["signature.asc" (application/pgp-signature)]

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