Add an Autotools build setup #2
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This should help code be more editable and encourage collaboration.
There does not seem to be overlap between the contents of the tarfiles. This brings the package in line with standard GitHub practice.
It should work; it's failing due to gfortran version mismatch now.
I forgot to do this the first time through. Also add a few of the files from the Autotools GNU standards. I may convert over to Gnits at some point.
LDFLAGS puts them too early
This apparently wasn't done earlier. I should probably look into changing this to MOSTLYCLEANFILES=*.mod at some point.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Extends #1
Include an Autotools build system, so that compilation in most cases will be
make distwill build tar files and zip files that include those files (so installing from those tar and zip files requires/bin/sh,make, and a Fortran compiler). We can then point people at those files if they want a given release, dropbuild-auxfrom this repository, and just require that anyone wanting to build from the latest development sources (or tar files and zip files generated by GitHub) have recent versions ofautoconfandautomake.Going this route somewhat complicates the build instructions.
This requires
/bin/shfor the configuration step on client machines.Many of these files are installed by
autoconfandautomake, so we can get rid of thebuild-auxdirectory if whoever is going to install this has recent versions of both. The files in them4directory are mostly fromAutoconf-archive, so we can drop that as well if the people installing or developing this have that package installed.Another alternative is to include all autotools-generated files in the repository, so that building from GitHub's "Download Here" button works the same way.
Advantages: only one set of build instructions
Disadvantages: Lots of generated files in the repository that are likely to change if the versions or
autoconforautomakechange. (Slightly larger repository, potential for log noise.)