cmake package

[aerorahul]

Keeping up with the packaging work of @kgerheiser, this PR adds that capability to CRTM.
Since there is no develop branch, this PR is merging into release/public-v1
There are no changes necessary downstream.

[DusanJovic-NOAA]

Let's create develop branch to make this repository consistent with other NCEPLIBS-* and make it easy to write install scripts that loop over all libraries.

[aerorahul]

Let's create develop branch to make this repository consistent with other NCEPLIBS-* and make it easy to write install scripts that loop over all libraries.

I have no issues with creating a develop branch so long as it is understood that this project is not under development. I would sooner rather than later move over to the authoritative CRTM repository and decommission this.

[DusanJovic-NOAA]

I see this repository is not a GitHub fork of another repository. Where is CRTM's authoritative repository and who maintains it?

[aerorahul]

I see this repository is not a GitHub fork of another repository. Where is CRTM's authoritative repository and who maintains it?

This is the CRTM's authoritative repository here
JCSDA maintains a releases from there.

[DusanJovic-NOAA]

I get "Page not found" error when I click here. Is this public repository?

[DusanJovic-NOAA]

I compiled successfully this branch on WCOSS Dell and linked ufs-weather-model using crtm::crtm imported target.

[aerorahul]

I get "Page not found" error when I click here. Is this public repository?

It is under the JCSDA organization. Nevertheless, the repository looks nothing like this one. It is hopeless to expect a cleaned up repository that we can simply fork and use for our purpose in any reasonable amount of time. I say, park this issue and move ahead. Please review and give a 👍 / 👎 .

[DusanJovic-NOAA]

How about creating develop branch?

[aerorahul]

How about creating develop branch?

done.

[BenjaminTJohnson]

Public repositories on the JCSDA github are coming "soon". Seems that I cannot push for this hard enough to make it happen, but it definitely has to happen around Oct 23: JEDI public release, CRTM v2.4.0 public release. I already have a REL_2.3.0_emc build release (not the development structure that we use internally).

Of course, anyone who is interested can have access to the private repository to have a look, just send me your github username.

As soon as there's an update on the public availability, I will let you all know.