Skip to content
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.

Sign up for GitHub

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

Jump to bottom

DRAFT: ISIS IO Remove QT Dep #5610

Draft
wants to merge 103 commits into
base: dev
Choose a base branch
from
Draft

DRAFT: ISIS IO Remove QT Dep #5610

wants to merge 103 commits into from

Conversation

amystamile-usgs
Copy link
Contributor

Description

Related Issue

How Has This Been Validated?

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 GitHub Actions
Copy link

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

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

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.

7 similar comments
@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

4 similar comments
@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

AustinSanders and others added 16 commits September 20, 2024 13:28
@AustinSanders @amystamile-usgs
Added history comment.
fb1ee15
@amystamile-usgs
Initial move to core
259b6ca
@amystamile-usgs
Removed Pvl cmakelists
c16ee07
@amystamile-usgs
Removed more cmakelists.txt
b1d7ac5
@amystamile-usgs
Add subdirectory
807c8e6
@AustinSanders @amystamile-usgs
Fully modularized core
43e8c77
@AustinSanders @amystamile-usgs
Fully modularized core
c655525
@AustinSanders @amystamile-usgs
replaced PvlEditDialog that was accidentally removed in prev commit
31ca2b5
@AustinSanders @amystamile-usgs
Initial constants unit gtest
d39a9f5
@jessemapel @amystamile-usgs
Fixed pvl core test config (DOI-USGS#4349)
7c666f2 
* Fixed pvl core test config

* Changed cmake_source to project_source for submodule
@jessemapel @amystamile-usgs
Fixed pvl core test config
46a087a
@jessemapel @amystamile-usgs
Changed cmake_source to project_source for submodule
f00c7b9
@AustinSanders @amystamile-usgs
First working swig wrappers
5b502d4
@AustinSanders @amystamile-usgs
Rebased off of pvl_core
17ecf1f
@jessemapel @amystamile-usgs
Moved old ISIS unitTests into core (DOI-USGS#4351)
1625dee 
* First pass at old unitTests

* re-removed old files

* Slim down and unittest port

* installing IsisPreferences

* Fixed tests in a full build
@acpaquette @amystamile-usgs
Finished swig wrapper with some syntax sugar for ease of use in python (
8992636 
DOI-USGS#4352)
@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

1 similar comment
@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

@github-actions GitHub Actions
Copy link

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

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

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@amystamile-usgs @AustinSanders @jessemapel @acpaquette @scsides