Suggestion: check for build files on new version
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 1.1k
- Forks
- 266
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 1
Description
On many revisions of rstan, in the past I had big problems getting everything to run again. This is most notable in the transition 2.16 to 2.17, and partly a problem of different CXX settings.
I have a sticker above my desk saying "don't forget Makevars", which is to remind me that something in that file or init.cpp or DLL import stuff may have changed. Whenever a new version comes out, I am supposed to create a skeleton and copy the relevant autogenerated files over to my projects (gastempt and breathteststan). However, I occasionally forget it, and then the trouble starts.
My suggestion: A function that updates the relevant build and auxillary files when a new version comes out.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review how Makevars, init.cpp, and DLL import files are generated or copied for rstan projects such as gastempt and breathteststan. Define which build and auxiliary files must be updated for a new version and how the proposed function should detect the relevant changes. Done means a project can update those files without manually recreating a skeleton.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100