-
Notifications
You must be signed in to change notification settings - Fork 87
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
Ford build updates #116
Ford build updates #116
Conversation
Current coverage is
|
939c27e
to
fb11a98
Compare
BTW, @jacobwilliams, please let me know if you want me to do a better job of separating FORD related stuff from other fixes and improvements. I can rebase this PR and pull commits unrelated to FORD out into a separate PR… with a separate feature branch. |
7cce2cc
to
14f8d44
Compare
Yes, if we can keep just the FORD stuff in this PR then that would be great. If it's too much trouble at this point though, then don't worry about. |
OK, I’ll branch out some of the more incidental stuff to their own branches… we’ll just need to be careful when we start pulling changes into master that we have merged changes from accepted PRs into outstanding PRs, or rebase outstanding PRs against master. (The latter approach is my preference… but can be a little tricky to resolve conflicts.) |
6339980
to
105296f
Compare
- Restrict example programs in README.md to be named example* to prevent confusion with other .md files when renaming extracted programs from README.md - Fixes a problem where new .md files are being interpreted as f90 sources
- Outputs still dynamically computed at configure time - Outputs not deleted after configure since FORD build is slower - FORD outputs cached so that running CMake again doesn't recompute them unless they need to be. - Small issue with some of the modification time of FORD files, see https://github.com/cmacmackin/ford/issues/55
- new meta data - added TOC - preprocessor macro workaround in json_module.F90 so that USE_UCS4 macro is not expanded in the documentation when unicode is enabled
105296f
to
ae2cb3f
Compare
I’ve cherry picked the unrelated commits into their own branches and submitted PRs against master for those… Once you merge them into master, you should either rebase the
I think 🙏 that my PRs against master won’t cause any merge conflicts when you do that… Let me know if they do and I can help you sort them out and any other git issues you run into. |
Cross your fingers.. |
example*