Skip to main content
12 events
when toggle format what by license comment
May 29, 2019 at 11:00 comment added Bodo Without seeing how you define the variables it is impossible to tell if your code is correct with respect to using $(...) or ${...}
May 29, 2019 at 8:42 vote accept robbie70
May 29, 2019 at 8:41 vote accept robbie70
May 29, 2019 at 8:42
May 29, 2019 at 8:41 vote accept robbie70
May 29, 2019 at 8:41
May 29, 2019 at 7:41 comment added robbie70 @Bodo yes I define the Make variables at the top of the script and yes I take one of the shell variables and do some manipulation on it to create the Make variables..this works ok.
May 28, 2019 at 15:40 answer added Bodo timeline score: 1
May 28, 2019 at 15:27 comment added Bodo Your commands contain both shell variables like ${IMAGE} and Make variables like $(IMAGE). Do you intend to use Make variables? You should show how you define these variables.
May 28, 2019 at 15:02 comment added robbie70 @Bodo - thanks for your comment. I am using Jenkins. I was going try to do this in my Jenkinsfile but I read a comment that that wasnt the place for it either - so thought I would delegate this to a Makefile.
May 28, 2019 at 15:01 answer added Stephen Kitt timeline score: 4
May 28, 2019 at 14:53 answer added Mathieu timeline score: 1
May 28, 2019 at 14:49 comment added Bodo Why do you want to implement this in a Makefile? The main purpose of make is to run commands depending on comparisons of file modification dates. You don't do this in your Makefile. A shell script (or a set of shell scripts) might be better suited for your use case.
May 28, 2019 at 14:34 history asked robbie70 CC BY-SA 4.0