bash-shell | OWenT 's Utils -- Bash & Shell branch | Script Programming library

you don't actually want to do this, and the packaging system tries very hard to prevent you from doing this.

the main hurdles:

• pip usually only runs setup.py once and then caches the result as a wheel
• pip will sometimes build your package in a directory unrelated to your git repository
• sometimes the library or tool won't be available (ordering) at the time of installation

and last of all, something that does this subverts the expectations of the python community -- that installation should not have side-effects outside of making the package available

ignoring all of that, you can trudge onwards and hack around the bits that attempt to prevent you

the rough stages for that are:

1. prevent wheeling of your package -- during the attempted wheeling make sure to exit, pip will usually fall back to just installing without wheeling
2. attempt to find the original working directory (either $PWD or via assumptions of the running executable
3. attempt to find the git repository you're running in
4. and lastly, make sure the tool is available

I've done all the dirty work for you, and I would strongly recommend not doing this -- https://github.com/pre-commit/pre-commit-installed

disclaimer, I created pre-commit, I also created pre-commit-installed but purely as a joke / proof of concept

You can try specifying the scriptName in your entry.js file to the name of your wrapper script. This may force generation of completion name using it. I haven't tried it but looking at the source code of yargs, it looks like the $0 parameter can be altered using scriptName, which in turn will affect how the completion-generation function generate the completion code:

In yargs-factor.ts:

Your code ...

When you assign to EP, the first section, $fixedFilePath leaves nothing on stdout for the pipe to take. What it does is executes the contents of that variable. You need to echo.

echo $fixedFilePath | rev | cut -d '.' -f 1 | rev

Now to capture that output you need to execute it as part of the assignment. There are various ways to go about this but what I found worked in your case was surrounding it in backticks:

When you have list diskletter, you don't need disknumber :

You can use brace expansion to alias multiple names into the same string:

You could use awk:

If cmake build setup is available, I usually use cmake for windows and setup the cmake via cmake-gui.exe. There you can set all needed variables and point to the correct location. The configure scripts only call cmake as much as I can see. From the cmake-gui you set the visual studio version and it will create a VS solution for you. Concerning qt, I suppose you should use the Maya specific version of qt, but I'm not sure where you can get them.

Use an image that has bash installed like CentOS or Ubuntu.