Optimize Go builds #116

New Issue

Closed

opened 2022-05-14 19:33:10 +02:00 by RubenKelevra · 3 comments

RubenKelevra commented

2022-05-14 19:33:10 +02:00

Contributor

Go 1.18 introduced GOAMD64 env variable, which can be added to makepkg.conf before building.

It's pretty easy for our usecase, at it would just be GOAMD64=v2 or GOAMD64=v3 :)

Should be a no brainer.

Go 1.18 introduced GOAMD64 env variable, which can be added to makepkg.conf before building. It's pretty easy for our usecase, at it would just be GOAMD64=v2 or GOAMD64=v3 :) Should be a no brainer.

👍 1

anonfunc added the

enhancement

label 2022-05-14 21:45:32 +02:00

RubenKelevra commented

2022-05-14 21:48:53 +02:00

Author

Contributor

Btw: Is there an easy way to see how the final makepkg.conf looks which runs on the build-server?

anonfunc commented

2022-05-14 21:49:23 +02:00

Owner

Not right now, but that should be easy to add I guess.

RubenKelevra commented

2022-05-15 00:07:54 +02:00

Author

Contributor

It's just that "ack"ing through the source code to find out what it's currently doing isn't really a great method of checking what flags etc are currently used.

I'll create a ticket for tracking this. :)

#118

It's just that "ack"ing through the source code to find out what it's currently doing isn't really a great method of checking what flags etc are currently used. I'll create a ticket for tracking this. :) https://somegit.dev/ALHP/ALHP.GO/issues/118

👍 1