Hi Marek,

I have some problem to build the last update on your channel, using the 
protocol in my last email.

I have an error on hash for https://github.com/xrash/smetrics : 


 l'empreinte r:sha256 ne correspond pas pour 
/gnu/store/514zq4lshhnxrqh7z5vw7fx30qcgfy2w-git-checkout :
  empreinte attendue : 057wgbz16n416zp23j5iv2lsd0nidbd92r4f1h8s3c1svkkqvk0a
  empreinte obtenue :  0rzqss8zjmhfgjbhpn3kicxqsyaw2732bv1hqm9w5xiqk3rg84kx
 

I use the guix commit : guix time-machine -C channels.scm 
--commit=823010478c4253f32c0b4d979881dbc6d7d08179 -- build -v 3 proton-bridge 
--cores=1

Do you have some plan to push your great work to codeberg using pull request ?

Best regards,
SR

Le lundi 13 janvier 2025 à 4:31 PM, sebastien <ml-...@reycoyrehourcq.me> a 
écrit :

> 

> 

> 

> Hi Marek,
> 

> Thanks for your work Marek, i try to compile on my guix system, and that 
> works (build & install) !
> 

> 

> For others interested to try :
> 

> a) create a directory proton-bridge & cd into
> b) clone sovereign.git with "git clone 
> https://git.marekpasnikowski.pl/sovereign.git/";
> 

> c) create a .channel file with this content :
> 

> 

> (cons
> 

> (channel
> (name 'sovereign)
> (url "xxx/sovereign") ; => replace xxx by your pwd
> 

> (branch "master"))
> %default-channels
> )
> 

> d) Run "guix time-machine -C channels.scm -- build -v 3 proton-bridge 
> --cores=1"
> e) Replace xxx by derivation builded in d) : "guix time-machine -C 
> channels.scm -- install /gnu/store/xxx"
> f) Run Desktop-Bridge
> 

> 

> Best regards,
> SR
> 

> 

> 

> 

> 

> 

> 

> 

> 

> 

> Le mardi 10 décembre 2024 à 11:28 AM, Marek Paśnikowski 
> ma...@marekpasnikowski.pl a écrit :
> 

> > I successfully built target bridge-nogui .
> 

> > The last step required implementation of a 'make' phase in the go build
> > process. I considered splitting out the go component into its own package, 
> > to
> > be an input of a qt package, but was not able to do it correctly.
> > Implementation of a go process in the gnu, or qt, build system is not even
> > worth considering. Thus I settled on invocation of "make" with some flags to
> > make it work in the go build system.
> 

> > I also decided against any further optimization of the make invocation,
> > because I am planning to implement all the build targets defined by 
> > upstream,
> > if possible.
> 

> > At this point, I need to rest a little. I will test the binary I built, see
> > if it even works. After that I am going to rewrite the module in a single
> > style. Only then I will work on the other targets.
> 

> > I also need to properly learn the peculiarities of the Go build system. I
> > would not be able to go this far without using random elements found in 
> > other
> > Go packages. It is unfortunate, that the build system reference page is
> > missing some key concepts in the Go process.
> > https://guix.gnu.org/manual/en/html_node/Build-Systems.html
> 

> > Marek Pasnikowski

Attachment: publickey - s.rey.coyrehourcq@proton.me - 0xC3237850.asc
Description: application/pgp-keys

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to