Isiscore build updates

[amystamile-usgs]

Description

Working isis_core conda-forge build

Related Issue

How Has This Been Validated?

passing CI tests on conda-forge staged recipes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation change (update to the documentation; no code change)
• Breaking change (fix or feature that would cause existing functionality to change)
• Infrastructure change (changes to things like CI or the build system that do not impact users)

Checklist:

• I have read and agree to abide by the Code of Conduct
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation and I have updated the documentation accordingly.
• I have added tests to cover my changes.
• I have added myself to the .zenodo.json document.
• I have added my user impacting change to the CHANGELOG.md document.

Licensing

This project is mostly composed of free and unencumbered software released into the public domain, and we are unlikely to accept contributions that are not also released into the public domain. Somewhere near the top of each file should have these words:

This work is free and unencumbered software released into the public domain. In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain.

• I dedicate any and all copyright interest in this software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

[github-actions]

The build and test suite have started for your pull request.

To view your build log, please reference the build with source version: "PR_6018".

Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch.

[Kelvinrr]

does this need to be ported into the RC branch and not dev?

[amystamile-usgs]

does this need to be ported into the RC branch and not dev?

It needs to be in both. But atleast in the RC branch for the next release.

[acpaquette]

To some extent this doesn't actually need to be part of ISIS at all since it will live on the feedstock. It largely depends on how we want the feedstock to work with the ISIS releases

[Kelvinrr]

We can make it seperate, but Im worried that would complicate the build system. Maybe we could make two seperate recipes for core and ISIS as a whole?

[acpaquette]

@Kelvinrr They currently exist like that. I should say that ISIS proper needs the changes to the CMakeLists.txt and the python library finding code. We just don't need the updated meta.yaml and build.sh code if we are going to release ISIS core off of conda-forges feedstocks