-
Notifications
You must be signed in to change notification settings - Fork 8
Create a user-friendly build interface #218
Copy link
Copy link
Open
Labels
good first issueGood for newcomersGood for newcomersstate: inactiveIssue is abandoned, but might become relavent at some pointIssue is abandoned, but might become relavent at some pointtype: featureBrand new functionality, features, workflows, endpoints, etcBrand new functionality, features, workflows, endpoints, etc
Metadata
Metadata
Assignees
Labels
good first issueGood for newcomersGood for newcomersstate: inactiveIssue is abandoned, but might become relavent at some pointIssue is abandoned, but might become relavent at some pointtype: featureBrand new functionality, features, workflows, endpoints, etcBrand new functionality, features, workflows, endpoints, etc
Sparsebase has many compile-time options (like header-only, data types). Furthermore, optional dependencies causes even more options to be selected by the users at compile-time. All of these options can also affect how the user needs to compile their own programs that use sparsebase as well.
The solution we are considering for this is to implement an easy-to-use and interactive script (preferably in Python) to build & install the library. This script can also provide users with build instructions, makefile templates etc. to properly link against sparsebase (this would also resolve #158).
A good example of the sort of thing we want here is the project creation for Nuxt (see here)
Here is a library that may be useful: PyInquirer
Note that this tool should be optional. If the users want to use cmake directly it should be possible.