Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add -j support to diy #2573

Closed
krafczyk opened this issue Dec 13, 2016 · 5 comments
Closed

Add -j support to diy #2573

krafczyk opened this issue Dec 13, 2016 · 5 comments

Comments

@krafczyk
Copy link
Contributor

-j and other install options should be available when using spack diy.

@citibeth
Copy link
Member

What does -j do?

@krafczyk
Copy link
Contributor Author

It allows parallel builds with a specific number of threads. This is especially useful when a diy package requires a bunch of prerequisites which all need to be compiled.

Basically, I feel that spack diy should behave the same way as spack install and take the same arguments to do the same thing. As is, spack diy builds packages in 'verbose' mode automatically among other things such as the fact that it doesn't listen to -j like I mentioned above.

@citibeth
Copy link
Member

Thank you. In the past, command line args have been inconsistent between Spack commands because someone added it to one command and neglected to add the same arg to others. This is most likely what's going on here. A git blame on the lines in spack install that implement the -j flag might be telling in this respect.

Does anyone know of any reason that -j should NOT be available for spack diy?

As for the verbose mode... that's something probably worth discussing further.

@citibeth
Copy link
Member

citibeth commented Feb 12, 2017 via email

@alalazo
Copy link
Member

alalazo commented Dec 5, 2019

This has been solved (now the command is called dev-build):

$ spack dev-build -h
usage: spack dev-build [-hinq] [-j JOBS] [-d SOURCE_PATH] [--keep-prefix]
                       [--skip-patch] [-u UNTIL] [--clean | --dirty]
                       ...

developer build: build from code in current working directory

positional arguments:
  spec                  specs to use for install. must contain package AND version

optional arguments:
  -h, --help            show this help message and exit
  -j JOBS, --jobs JOBS  explicitly set number of parallel jobs
  -d SOURCE_PATH, --source-path SOURCE_PATH
                        path to source directory. defaults to the current directory
  -i, --ignore-dependencies
                        don't try to install dependencies of requested packages
  -n, --no-checksum     do not use checksums to verify downloaded files (unsafe)
  --keep-prefix         do not remove the install prefix if installation fails
  --skip-patch          skip patching for the developer build
  -q, --quiet           do not display verbose build output while installing
  -u UNTIL, --until UNTIL
                        phase to stop after when installing (default None)
  --clean               unset harmful variables in the build environment (default)
  --dirty               preserve user environment in the spack build environment (danger!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants