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

Autotools integration #306

Open
mikebentley15 opened this issue Dec 12, 2019 · 0 comments
Open

Autotools integration #306

mikebentley15 opened this issue Dec 12, 2019 · 0 comments
Labels
documentation Involves touching documentation enhancement make Involves touching GNU Makefiles python Involves touching python code tests Involves touching tests

Comments

@mikebentley15
Copy link
Collaborator

Feature Request

Describe the new feature:
Right now, FLiT only has GNU Make integration and experimental Ninja Build integration.

What about projects using Autotools? As it is now, we could have the flit-config.toml and custom.mk be input files that Autotools can populate (i.e., flit-config.toml.in and custom.mk.in). I think this is the only reasonable approach, but I'm not too familiar with how Autotools works.

Suggested change:
Somehow make it easy to generate flit-config.toml and custom.mk from an Autotools setup. Perhaps there's a way to define functions with Package Config. Perhaps just document how users can do it with their own *.in files. I'm not sure.

@mikebentley15 mikebentley15 added enhancement python Involves touching python code make Involves touching GNU Makefiles documentation Involves touching documentation tests Involves touching tests labels Dec 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Involves touching documentation enhancement make Involves touching GNU Makefiles python Involves touching python code tests Involves touching tests
Projects
None yet
Development

No branches or pull requests

1 participant