Project Task Script and Portablity #805
Unanswered
phreed
asked this question in
Feature Requests & Ideas
Replies: 1 comment 1 reply
-
|
I prefer
The module ( #!/usr/bin/env nu
use jank-mod.nu *
def --wrapped main [
--profile: string = "debug" # Build profile: "debug" or "release"
--jobs (-j): int = 0 # Parallel jobs; 0 = half of logical CPUs rounded up
...args: string
] {
compile --profile $profile --jobs $jobs ...$args
}vs. #!/usr/bin/env bash
set -euo pipefail
here="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
build_dir="${here}/../build"
cmake --build "${build_dir}" "$@"The
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This issue is connected to the Windows packaging issue, yet it is distinct.
Presently the majority of the project management scripts are written in
bash.bashis well known but lacks portability to Windows.I have only found three ways to accommodate this deficiency:
*.batThe MSYS2 tooling and compilers produce binaries which are incompatible with MSVC libraries.
I have not tried Git Bash.
There are some candidates for alternate scripting languages:
Beta Was this translation helpful? Give feedback.
All reactions