-
Notifications
You must be signed in to change notification settings - Fork 6
Autotools integration #306
Copy link
Copy link
Open
Labels
documentationInvolves touching documentationInvolves touching documentationenhancementmakeInvolves touching GNU MakefilesInvolves touching GNU MakefilespythonInvolves touching python codeInvolves touching python codetestsInvolves touching testsInvolves touching tests
Metadata
Metadata
Assignees
Labels
documentationInvolves touching documentationInvolves touching documentationenhancementmakeInvolves touching GNU MakefilesInvolves touching GNU MakefilespythonInvolves touching python codeInvolves touching python codetestsInvolves touching testsInvolves touching tests
Type
Fields
Give feedbackNo fields configured for issues without a type.
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.tomland custom.mk be input files that Autotools can populate (i.e.,flit-config.toml.inandcustom.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.tomlandcustom.mkfrom 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*.infiles. I'm not sure.