go ldflags set variable value not working












0














I'm trying to use go build to update a variable inside my project:



full project path:



c:goprojectssrcdeploymentclappsappName


run from c:goprojectssrc



 go install -ldflags="-X main.GitRev=adaf66c" deploymentclappsappName...


In the go project I have:



package main
var GitRev = "oldvalue"


func main() {
fmt.Println("variable contents: ", GitRev)
}


Then from the command line I run:



..binappName.exe


I'm expecting to see the value:



adaf66c


What I get: variable contents:



oldvalue









share|improve this question






















  • Are you sure you are running the binary you just built?
    – zerkms
    Nov 20 at 23:06












  • yes, I can change the value of GitRev from 'oldvalue' to 'oldvalue1' and see that it changes the next time I build the appName.exe binary
    – buildmaestro
    Nov 20 at 23:10










  • I took your code, and: 1) ➜ go build -ldflags="-X main.GitRev=adaf66c" 2) ➜ ./so-53402640 variable contents: adaf66c (it's linux though)
    – zerkms
    Nov 20 at 23:32












  • ya it should work. maybe related to the paths. I also have a large project with many imports too, but shouldn't matter.
    – buildmaestro
    Nov 20 at 23:41
















0














I'm trying to use go build to update a variable inside my project:



full project path:



c:goprojectssrcdeploymentclappsappName


run from c:goprojectssrc



 go install -ldflags="-X main.GitRev=adaf66c" deploymentclappsappName...


In the go project I have:



package main
var GitRev = "oldvalue"


func main() {
fmt.Println("variable contents: ", GitRev)
}


Then from the command line I run:



..binappName.exe


I'm expecting to see the value:



adaf66c


What I get: variable contents:



oldvalue









share|improve this question






















  • Are you sure you are running the binary you just built?
    – zerkms
    Nov 20 at 23:06












  • yes, I can change the value of GitRev from 'oldvalue' to 'oldvalue1' and see that it changes the next time I build the appName.exe binary
    – buildmaestro
    Nov 20 at 23:10










  • I took your code, and: 1) ➜ go build -ldflags="-X main.GitRev=adaf66c" 2) ➜ ./so-53402640 variable contents: adaf66c (it's linux though)
    – zerkms
    Nov 20 at 23:32












  • ya it should work. maybe related to the paths. I also have a large project with many imports too, but shouldn't matter.
    – buildmaestro
    Nov 20 at 23:41














0












0








0







I'm trying to use go build to update a variable inside my project:



full project path:



c:goprojectssrcdeploymentclappsappName


run from c:goprojectssrc



 go install -ldflags="-X main.GitRev=adaf66c" deploymentclappsappName...


In the go project I have:



package main
var GitRev = "oldvalue"


func main() {
fmt.Println("variable contents: ", GitRev)
}


Then from the command line I run:



..binappName.exe


I'm expecting to see the value:



adaf66c


What I get: variable contents:



oldvalue









share|improve this question













I'm trying to use go build to update a variable inside my project:



full project path:



c:goprojectssrcdeploymentclappsappName


run from c:goprojectssrc



 go install -ldflags="-X main.GitRev=adaf66c" deploymentclappsappName...


In the go project I have:



package main
var GitRev = "oldvalue"


func main() {
fmt.Println("variable contents: ", GitRev)
}


Then from the command line I run:



..binappName.exe


I'm expecting to see the value:



adaf66c


What I get: variable contents:



oldvalue






go






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 20 at 22:37









buildmaestro

344622




344622












  • Are you sure you are running the binary you just built?
    – zerkms
    Nov 20 at 23:06












  • yes, I can change the value of GitRev from 'oldvalue' to 'oldvalue1' and see that it changes the next time I build the appName.exe binary
    – buildmaestro
    Nov 20 at 23:10










  • I took your code, and: 1) ➜ go build -ldflags="-X main.GitRev=adaf66c" 2) ➜ ./so-53402640 variable contents: adaf66c (it's linux though)
    – zerkms
    Nov 20 at 23:32












  • ya it should work. maybe related to the paths. I also have a large project with many imports too, but shouldn't matter.
    – buildmaestro
    Nov 20 at 23:41


















  • Are you sure you are running the binary you just built?
    – zerkms
    Nov 20 at 23:06












  • yes, I can change the value of GitRev from 'oldvalue' to 'oldvalue1' and see that it changes the next time I build the appName.exe binary
    – buildmaestro
    Nov 20 at 23:10










  • I took your code, and: 1) ➜ go build -ldflags="-X main.GitRev=adaf66c" 2) ➜ ./so-53402640 variable contents: adaf66c (it's linux though)
    – zerkms
    Nov 20 at 23:32












  • ya it should work. maybe related to the paths. I also have a large project with many imports too, but shouldn't matter.
    – buildmaestro
    Nov 20 at 23:41
















Are you sure you are running the binary you just built?
– zerkms
Nov 20 at 23:06






Are you sure you are running the binary you just built?
– zerkms
Nov 20 at 23:06














yes, I can change the value of GitRev from 'oldvalue' to 'oldvalue1' and see that it changes the next time I build the appName.exe binary
– buildmaestro
Nov 20 at 23:10




yes, I can change the value of GitRev from 'oldvalue' to 'oldvalue1' and see that it changes the next time I build the appName.exe binary
– buildmaestro
Nov 20 at 23:10












I took your code, and: 1) ➜ go build -ldflags="-X main.GitRev=adaf66c" 2) ➜ ./so-53402640 variable contents: adaf66c (it's linux though)
– zerkms
Nov 20 at 23:32






I took your code, and: 1) ➜ go build -ldflags="-X main.GitRev=adaf66c" 2) ➜ ./so-53402640 variable contents: adaf66c (it's linux though)
– zerkms
Nov 20 at 23:32














ya it should work. maybe related to the paths. I also have a large project with many imports too, but shouldn't matter.
– buildmaestro
Nov 20 at 23:41




ya it should work. maybe related to the paths. I also have a large project with many imports too, but shouldn't matter.
– buildmaestro
Nov 20 at 23:41












1 Answer
1






active

oldest

votes


















0














I believe you are just declaring a variable and not a flag. Import the flag package and assign it like so.



import "flag"
var GitRev = flag.String("GitRev", "oldvalue", "what it represents")





share|improve this answer

















  • 1




    I'm sure you misunderstand the question
    – zerkms
    Nov 20 at 23:05










  • There is a good chance that is the case.
    – cooljoe
    Nov 20 at 23:20











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53402640%2fgo-ldflags-set-variable-value-not-working%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














I believe you are just declaring a variable and not a flag. Import the flag package and assign it like so.



import "flag"
var GitRev = flag.String("GitRev", "oldvalue", "what it represents")





share|improve this answer

















  • 1




    I'm sure you misunderstand the question
    – zerkms
    Nov 20 at 23:05










  • There is a good chance that is the case.
    – cooljoe
    Nov 20 at 23:20
















0














I believe you are just declaring a variable and not a flag. Import the flag package and assign it like so.



import "flag"
var GitRev = flag.String("GitRev", "oldvalue", "what it represents")





share|improve this answer

















  • 1




    I'm sure you misunderstand the question
    – zerkms
    Nov 20 at 23:05










  • There is a good chance that is the case.
    – cooljoe
    Nov 20 at 23:20














0












0








0






I believe you are just declaring a variable and not a flag. Import the flag package and assign it like so.



import "flag"
var GitRev = flag.String("GitRev", "oldvalue", "what it represents")





share|improve this answer












I believe you are just declaring a variable and not a flag. Import the flag package and assign it like so.



import "flag"
var GitRev = flag.String("GitRev", "oldvalue", "what it represents")






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 20 at 22:46









cooljoe

113




113








  • 1




    I'm sure you misunderstand the question
    – zerkms
    Nov 20 at 23:05










  • There is a good chance that is the case.
    – cooljoe
    Nov 20 at 23:20














  • 1




    I'm sure you misunderstand the question
    – zerkms
    Nov 20 at 23:05










  • There is a good chance that is the case.
    – cooljoe
    Nov 20 at 23:20








1




1




I'm sure you misunderstand the question
– zerkms
Nov 20 at 23:05




I'm sure you misunderstand the question
– zerkms
Nov 20 at 23:05












There is a good chance that is the case.
– cooljoe
Nov 20 at 23:20




There is a good chance that is the case.
– cooljoe
Nov 20 at 23:20


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53402640%2fgo-ldflags-set-variable-value-not-working%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Wiesbaden

Marschland

Dieringhausen