Age | Commit message (Collapse) | Author | Files | Lines |
|
methods add_target_from_string and add_operating_system_from_string
|
|
|
|
|
|
|
|
|
|
compiler_for_spec uses operating system strategy
|
|
|
|
|
|
target
|
|
|
|
instance from dictionary just using name without the version attached. Object will stil display as name+version
|
|
|
|
|
|
|
|
|
|
|
|
absolute import'
|
|
dictionary already so got rid of d['architecture']
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
called CNL for compute node linux (name will probably change because I can't find docs on the EXACT name)
|
|
|
|
strategy is set correctly
|
|
|
|
platform dictionary
|
|
|
|
|
|
are used my operating system subclasses
|
|
|
|
|
|
|
|
|
|
abstract.architecture.target.concrete
|
|
|
|
|
|
of spec.target
|
|
of the arch tuple
|
|
so any time we need access to target we do architecture.target.
|
|
|
|
|
|
checks whether each piece of string is a valid platform, operating system and target. If the operating system or target are none it will use the defaults. Updated the documentation for that method. One thing that bothers me is how to account for the multitude of operating systems when cross compiling. If someone wants to compile with another operating system not found on current platform. How can spack check to see if it is valid?
|
|
weren't going to be used anyway
|