Re: [go-nuts] ldflags -X

2023-11-08 Thread Stephen Illingworth
Yes. I agree that it's correct given the general rules. On Wednesday, 8 November 2023 at 15:42:25 UTC Jan Mercl wrote: > On Wed, Nov 8, 2023 at 4:01 PM Stephen Illingworth > wrote: > > > I would have expected the "main.A" string to require the same form. But > either way, that's the correct

Re: [go-nuts] ldflags -X

2023-11-08 Thread Jan Mercl
On Wed, Nov 8, 2023 at 4:01 PM Stephen Illingworth wrote: > I would have expected the "main.A" string to require the same form. But > either way, that's the correct solution. It is the correct form. Package main cannot be imported and has a special import path. Though I don't know where it is

Re: [go-nuts] ldflags -X

2023-11-08 Thread Stephen Illingworth
I would have expected the "main.A" string to require the same form. But either way, that's the correct solution. Thanks. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send

Re: [go-nuts] ldflags -X

2023-11-08 Thread Jan Mercl
On Wed, Nov 8, 2023 at 1:35 PM Stephen Illingworth < stephen.illingwo...@gmail.com> wrote: > > Hello, > > I'm trying to use the -X ldflag to set a string at compile time. I can do this successfully if the string is in the main package but it does not work if the string is in a subpackage. > > For

[go-nuts] ldflags -X

2023-11-08 Thread Stephen Illingworth
Hello, I'm trying to use the -X ldflag to set a string at compile time. I can do this successfully if the string is in the main package but it does not work if the string is in a subpackage. For illustration purposes, I have prepared a simple test project