Testing multiple operating systems (os, windows) with golangci-lint in CI

[leap-pea]

Hey,
what's the best way to run golangci-lint run for all OSs in the CI? Is there an option? Or do I need multiple invocations with GOOS=windows, etc?

[ldez]

Hi,

There is no option, golangci-lint relies on elements it has been compiled for.

Golangci-lint is not Go, using GOOS/GOARCH will not work as expected because of my previous explanation.

You can see examples inside the golangci-lint GitHub action: https://github.com/golangci/golangci-lint-action?tab=readme-ov-file#how-to-use

[wxiaoguang]

@ldez

I think the answer is not true.

golangci-lint uses Golang compiler (parser), and it supports "--build-tags"

When it lints, there is nothing related to "elements it has been compiled for"

Just like you can cross-compile a Go program on Linux for Windows, you can also use golangci-lint to lint "windows" code on Linux, as long as you can make the "Go compiler" have correct tags, the real example is:

# this perfectly works on Linux, just like `GOOS=windows go build` the source code
GOOS=windows golangci-lint run --build-tags=windows

[ldez]

THIS IS NOT RELATED TO USING PRE-COMPILED BINARY.

Please read again my previous post.

[wxiaoguang]

The user is JUST ASKING FOR "what's the best way to run golangci-lint run for all OSs in the CI? Is there an option? Or do I need multiple invocations with GOOS=windows, etc?"

So, pre-compile a binary, then it does run for all OSs in the CI, no need to use matrix, is it right?

Which point is off-topic?

[ldez]

So, pre-compile a binary, then it does run for all OSs in the CI, no need to use matrix, is it right?

No

Which point is off-topic?

I give up, your are deep into a wrong interpretation of what I'm saying.

I repeated, reworded several times, provided examples, now, feel free to think what you want, I did my best to explain, sorry to not be able to do better.

[wxiaoguang]

So, pre-compile a binary, then it does run for all OSs in the CI, no need to use matrix, is it right?

No

There is just no bad case from you, then you just said "provided examples".

You said "THIS IS NOT RELATED TO USING PRE-COMPILED BINARY". Any real example that the pre-compiled binary doesn't work? Just like Linus said: talking is cheap, show me the code.

[wxiaoguang]

What do you don't understand in this sentence:

As I already said, you could run golangci-lint with GOOS/GOARCH, it may work in some cases, but if any element compiled inside golangci-lint relies on a build tags it will not work as expected.

Could you show me a real such "element"? I'd like to learn the details to see what indeed it is doing, or maybe its design was wrong.