Comments (5)
fair enough. But as you get older and use more and more makefiles, it gets tedious to "more" the makefile. SO I'm now using a technique advocated by software carpentry to make the makefile self-documenting. I mean, who wants to read a README when there's a Makefile :-) You can add that as the first "help" target. I now employ this to all my (new) projects. Here's an example of that implementation
https://github.com/teuben/teunix/blob/master/Makefile
from supernovas.
yes, that sounds like a good compromise.
from supernovas.
Hi Peter,
The default make
target is the api
, which includes the static and shared libraries, the cio_bin
file and the doxygen documentation -- the basic pieces for operation and documentation. I don't think it's very relevant what the default build target is. You can pick and choose each part individually. Quoting from the README
:
you can build select components of the above with the make targets
static
,shared
,cio_file
, anddox
respectively
So, if you want just the static library, just use
$ make static
And, if there is a good reason why the default build target should be different, then that change can be made to the next feature release (e.g. 1.1.0). It will however require adjusting the both the documentation and the CI to match...
I hope that answers the question,
-- Attila.
from supernovas.
PS. Alternatively, I could make the dox
part of the build conditional on the presence of doxygen
. That way nothing much else needs to change beyond the Makefile
...
from supernovas.
Hi Peter,
Check out PR #22, and see if that does the trick for you. If it satisfies you, I'd be happy to include that in the next update (in ~3 months)...
I'll also think about the make help
idea. The trouble here is that the make requires a fair bit of customization (owing to the not so user-friendly history of the library, and the desire to be both back compatible but also more flexible). So, it's probably best if people actually look at the README before just blindly typing make
, or else what they build may not be what they need exactly....
from supernovas.
Related Issues (9)
- refract_astro() in v0.9 is incorrect.
- Typo in example HOT 1
- Unit conversion of ut1_to_tt in cirs_to_itrs(), itrs_to_cirs(), tod_to_itrs(), and itrs_to_tod() HOT 4
- Numerical value of AU HOT 1
- Changes to build to make packaging easier
- SUPERNOVAS_VERSION_STRING ill defined in novas.h
- d_light() bug when called with zero position HOT 1
- Invalid results on some platforms (e.g. ARM, PowerPC) HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from supernovas.