You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only way to have a shimgen started in its own directory is by adding --shimgen-usetargetworkingdirectory to the command line options when starting the shim. This means you will have to provide a scriptl which adds this option + the other command line arguments.
One of the advantages of shim is not needing those wrapper scripts, which mess up quotes and spaces.
Passing "-c --shimgen-usetargetworkingdirectory" to shimgen itself, does not work. It passes the argument without evaluating it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The only way to have a shimgen started in its own directory is by adding
--shimgen-usetargetworkingdirectory
to the command line options when starting the shim. This means you will have to provide a scriptl which adds this option + the other command line arguments.One of the advantages of shim is not needing those wrapper scripts, which mess up quotes and spaces.
Passing "-c --shimgen-usetargetworkingdirectory" to shimgen itself, does not work. It passes the argument without evaluating it.
Beta Was this translation helpful? Give feedback.
All reactions