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

Make Pycicle work for any Project #7

Open
biddisco opened this issue Jan 22, 2018 · 2 comments
Open

Make Pycicle work for any Project #7

biddisco opened this issue Jan 22, 2018 · 2 comments
Assignees

Comments

@biddisco
Copy link
Owner

In order to use pycicle for projects other than HPX, there are some HPX specific variables/links that need to be made into options or configurable elements.

@biddisco
Copy link
Owner Author

biddisco commented Feb 7, 2018

@PDoakORNL PDoakORNL self-assigned this May 22, 2018
@PDoakORNL
Copy link
Collaborator

PDoakORNL commented May 22, 2018

  • Each trunk should not require a project level directory under config

I made the first steps toward item 4 in #23

One question to answer is the priority of args, various levels of config from CMake.
I would propose the following priority

  1. command line arguments
  2. pycicle/config//.cmake
  3. /pycicle_config/.cmake
  4. pycicle/config//.cmake

By priority I mean if a lower priority value is found, it is not reset by later files. Right now it is generally written but the order and number of time the config .cmake files is read I'm not entirely sure of.

PycicleParams should make it easy to read the .cmake files once and have clear precedence as far as pycicle.py is concerned.

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

2 participants