Styjun

Did any compiler fully use 80-bit floating point?

How to make triangles with rounded sides and corners? (squircle with 3 sides)

Determine whether an integer is a palindrome

How could a hydrazine and N2O4 cloud (or it's reactants) show up in weather radar?

Why is there so little support for joining EFTA in the British parliament?

Found this skink in my tomato plant bucket. Is he trapped? Or could he leave if he wanted?

Adapting the Chinese Remainder Theorem (CRT) for integers to polynomials

Getting representations of the Lie group out of representations of its Lie algebra

Where and when has Thucydides been studied?

3D Masyu - A Die

Random body shuffle every night—can we still function?

Any stored/leased 737s that could substitute for grounded MAXs?

What is "Lambda" in Heston's original paper on stochastic volatility models?

How do you write "wild blueberries flavored"?

First paper to introduce the "principal-agent problem"

newbie Q : How to read an output file in one command line

Fit odd number of triplets in a measure?

Marquee sign letters

Why can't fire hurt Daenerys but it did to Jon Snow in season 1?

"Destructive power" carried by a B-52?

What does 丫 mean? 丫是什么意思？

Is there a verb for listening stealthily?

NIntegrate on a solution of a matrix ODE

Calculation of line of sight system gain

Expanding path variable in makefile using SED on Windows

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

1

1

On Windows machine, a makefile is taking path option and creating another file by appending this path value.

My problem is that path variable is not expanding correct in resultant file.

For example

$ make var=c:testkernel

by using below makefile code this $(var) value is being appending to output file

all:
 @sed -i '1 iexport PATH := $(var)' output.txt

Expected result

export PATH := c:testkernel

But instead I'm getting

export PATH := c: estkernel

So, how I can fix this problem in makefile?

regex sed cmd makefile

share|improve this question

edited Mar 22 at 14:45

Taylor Spark

3610

asked Mar 22 at 12:30

Equation SolverEquation Solver

179113

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Looks like the t in c:testkernel is interpreted as a tab, escape the backslashes (with another one)
  
  – LotPings
  Mar 22 at 12:43
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What are you running that provides sed, make, and a shell? cygwin, mingw, ???
  
  – lit
  Mar 22 at 12:53
  

  
  
  
  

add a comment | 

1

1

On Windows machine, a makefile is taking path option and creating another file by appending this path value.

My problem is that path variable is not expanding correct in resultant file.

For example

$ make var=c:testkernel

by using below makefile code this $(var) value is being appending to output file

all:
 @sed -i '1 iexport PATH := $(var)' output.txt

Expected result

export PATH := c:testkernel

But instead I'm getting

export PATH := c: estkernel

So, how I can fix this problem in makefile?

regex sed cmd makefile

share|improve this question

edited Mar 22 at 14:45

Taylor Spark

3610

asked Mar 22 at 12:30

Equation SolverEquation Solver

179113

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Looks like the t in c:testkernel is interpreted as a tab, escape the backslashes (with another one)
  
  – LotPings
  Mar 22 at 12:43
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What are you running that provides sed, make, and a shell? cygwin, mingw, ???
  
  – lit
  Mar 22 at 12:53
  

  
  
  
  

add a comment | 

On Windows machine, a makefile is taking path option and creating another file by appending this path value.

My problem is that path variable is not expanding correct in resultant file.

For example

$ make var=c:testkernel

by using below makefile code this $(var) value is being appending to output file

all:
 @sed -i '1 iexport PATH := $(var)' output.txt

Expected result

export PATH := c:testkernel

But instead I'm getting

export PATH := c: estkernel

So, how I can fix this problem in makefile?

regex sed cmd makefile

share|improve this question

edited Mar 22 at 14:45

Taylor Spark

3610

asked Mar 22 at 12:30

Equation SolverEquation Solver

179113

$ make var=c:testkernel

all:
 @sed -i '1 iexport PATH := $(var)' output.txt

export PATH := c:testkernel

export PATH := c: estkernel

share|improve this question

edited Mar 22 at 14:45

Taylor Spark

3610

asked Mar 22 at 12:30

Equation SolverEquation Solver

179113

share|improve this question

edited Mar 22 at 14:45

Taylor Spark

3610

asked Mar 22 at 12:30

Equation SolverEquation Solver

179113

edited Mar 22 at 14:45

Taylor Spark

3610

edited Mar 22 at 14:45

Taylor Spark

3610

asked Mar 22 at 12:30

Equation SolverEquation Solver

179113

asked Mar 22 at 12:30

Equation SolverEquation Solver

179113

1 Answer
1

active

oldest

votes

2

First, I strongly urge you to always use forward slashes in paths even on Windows, especially when working with make. There are very few programs on Windows that won't work with forward-slashes (mainly old-school CMD commands etc.) and using backslashes in tools which have their provenance in UNIX will always be an uncomfortable fit.

For your situation you can do something like this:

all:
 @sed -i '1 iexport PATH := $(subst ,\,$(var))' output.txt

to convert your backslashes to escaped backslashes.

share|improve this answer

answered Mar 22 at 13:05

MadScientistMadScientist

48.4k55470

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  you really save my day, big thanks
  
  – Equation Solver
  Mar 22 at 13:19
  

  
  
  
  

add a comment | 

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

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55299646%2fexpanding-path-variable-in-makefile-using-sed-on-windows%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

2

First, I strongly urge you to always use forward slashes in paths even on Windows, especially when working with make. There are very few programs on Windows that won't work with forward-slashes (mainly old-school CMD commands etc.) and using backslashes in tools which have their provenance in UNIX will always be an uncomfortable fit.

For your situation you can do something like this:

all:
 @sed -i '1 iexport PATH := $(subst ,\,$(var))' output.txt

to convert your backslashes to escaped backslashes.

share|improve this answer

answered Mar 22 at 13:05

MadScientistMadScientist

48.4k55470

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  you really save my day, big thanks
  
  – Equation Solver
  Mar 22 at 13:19
  

  
  
  
  

add a comment | 

2

First, I strongly urge you to always use forward slashes in paths even on Windows, especially when working with make. There are very few programs on Windows that won't work with forward-slashes (mainly old-school CMD commands etc.) and using backslashes in tools which have their provenance in UNIX will always be an uncomfortable fit.

For your situation you can do something like this:

all:
 @sed -i '1 iexport PATH := $(subst ,\,$(var))' output.txt

to convert your backslashes to escaped backslashes.

share|improve this answer

answered Mar 22 at 13:05

MadScientistMadScientist

48.4k55470

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  you really save my day, big thanks
  
  – Equation Solver
  Mar 22 at 13:19
  

  
  
  
  

add a comment | 

First, I strongly urge you to always use forward slashes in paths even on Windows, especially when working with make. There are very few programs on Windows that won't work with forward-slashes (mainly old-school CMD commands etc.) and using backslashes in tools which have their provenance in UNIX will always be an uncomfortable fit.

For your situation you can do something like this:

all:
 @sed -i '1 iexport PATH := $(subst ,\,$(var))' output.txt

to convert your backslashes to escaped backslashes.

share|improve this answer

answered Mar 22 at 13:05

MadScientistMadScientist

48.4k55470

all:
 @sed -i '1 iexport PATH := $(subst ,\,$(var))' output.txt

share|improve this answer

answered Mar 22 at 13:05

MadScientistMadScientist

48.4k55470

answered Mar 22 at 13:05

MadScientistMadScientist

48.4k55470

answered Mar 22 at 13:05

MadScientistMadScientist

48.4k55470