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.

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

New home, license, "cmake" driven build, and latest version #26

Merged
merged 23 commits into from Mar 8, 2023
Merged

New home, license, "cmake" driven build, and latest version #26

merged 23 commits into from Mar 8, 2023

Conversation

timcera
Copy link
Contributor

@timcera timcera commented Jan 19, 2023

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged. (which license file? The only license file in the original fork is for the feedstock. Am I supposed to include the license file of the g2clib package? Pointed to it in the README.md.

@conda-forge-webservices
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

  • The recipe must have some tests.
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).

For recipe:

  • License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-webservices
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

  • The recipe must have some tests.

@conda-forge-webservices
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-webservices
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

  • The recipe must have some tests.

@timcera
Copy link
Contributor Author

timcera commented Jan 21, 2023

@conda-forge-admin, please rerender
Because of conda/conda-build#4733 and conda-forge/conda-forge-pinning-feedstock#3973 I cannot run "conda-smithy rerender".

@timcera
Copy link
Contributor Author

timcera commented Jan 21, 2023

I have carried this as far as I can.

I thought the system wouldn't try to build Windows or OSX anymore, but I must misunderstand something. The current Windows successful build is empty.

Kind regards,
Tim

recipe/meta.yaml Outdated Show resolved Hide resolved
recipe/meta.yaml Outdated Show resolved Hide resolved
@conda-forge-webservices
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@xylar
Copy link
Contributor

xylar commented Jan 28, 2023

@conda-forge-admin, please rerender

conda-forge-webservices[bot] and others added 3 commits January 28, 2023 01:38
Make it more verbose, parallel and only run it when not cross compiling.
@xylar
Copy link
Contributor

xylar commented Jan 28, 2023

@conda-forge-admin, please rerender

@xylar
Copy link
Contributor

xylar commented Jan 28, 2023

That last commit refers to all unix architectures. We're still skipping Windows.

@xylar
Copy link
Contributor

xylar commented Jan 28, 2023

I think we'll want to wait for conda-forge/jasper-feedstock#41 to get ppc64le support. In the meantime, I'll try to get the rest of the tests working.

@xylar
Copy link
Contributor

xylar commented Jan 28, 2023

Failing tests for OSX may relate to old jasper, see:
NOAA-EMC/NCEPLIBS-g2c#398

@xylar
Copy link
Contributor

xylar commented Jan 28, 2023

@timcera, thank you for getting us this far! I wouldn't have been able to make any headway without you getting things started. The remaining problems both seem related to jasper. I'll see what I can do about them over at https://github.com/conda-forge/jasper-feedstock/pulls

@xylar
Copy link
Contributor

xylar commented Feb 7, 2023

OSX is installing the correct libpng:

    libpng:  1.6.39-ha978bb4_0 conda-forge

but then detects a much older version somehow in CMake:

-- Found PNG: $PREFIX/lib/libpng.dylib (found version "1.4.12") 

This then seems to cause issues in testing:

test 18
      Start 18: tst_addfield2

18: Test command: $SRC_DIR/build/tests/tst_addfield2
18: Working Directory: $SRC_DIR/build/tests
18: Test timeout computed to be: 1500
17: libpng warning: Application built with libpng-1.4.12 but running with 1.6.39
17: Testing PNG functions.
17: Testing enc_png() call...-1
17/21 Test #17: tst_png ..........................***Failed    0.11 sec
libpng warning: Application built with libpng-1.4.12 but running with 1.6.39
Testing PNG functions.
Testing enc_png() call...-1

test 19
      Start 19: tst_jpeg

19: Test command: $SRC_DIR/build/tests/tst_jpeg
19: Working Directory: $SRC_DIR/build/tests
19: Test timeout computed to be: 1500
18: libpng warning: Application built with libpng-1.4.12 but running with 1.6.39
18: Testing g2_addfield() some more.
18: Testing full message creation (expect and ignore error messages)...
18: g2_addfield: Sections 4-7 can only be added after Section 3 or 7.
18: g2_addfield: Section 1 was the last found in given GRIB message.
18: g2_addfield: Section byte counts don''t add to total.
18: g2_addfield: Sum of section byte counts = 37
18: g2_addfield: Total byte count in Section 0 = 5
18: pngpack: ERROR Packing PNG = -1
18/21 Test #18: tst_addfield2 ....................***Failed    0.11 sec
libpng warning: Application built with libpng-1.4.12 but running with 1.6.39
Testing g2_addfield() some more.

I don't know that could be causing this.

@xylar
Copy link
Contributor

xylar commented Feb 7, 2023

@ocefpaf, you're a maintainer of libpng, though I know you're involved in a lot of packages and that doesn't mean you have to be an expert on all of them! Any guesses?

@ocefpaf
Copy link
Member

ocefpaf commented Feb 7, 2023

@ocefpaf, you're a maintainer of libpng, though I know you're involved in a lot of packages and that doesn't mean you have to be an expert on all of them! Any guesses?

Not sure :-/ Maybe it is a bug in the cmake files?

@timcera
Copy link
Contributor Author

timcera commented Mar 8, 2023

For the osx_64 build only, would it make sense to just remove the system libpng? Then the only visible libpng would be the one installed by conda.

@xylar
Copy link
Contributor

xylar commented Mar 8, 2023

@timcera, feel free to give that a try.

@timcera
Copy link
Contributor Author

timcera commented Mar 8, 2023

Was able to make it work with cmake keywords. https://conda-forge.org/docs/maintainer/knowledge_base.html#using-cmake

@xylar
Copy link
Contributor

xylar commented Mar 8, 2023

Wonderful! Thanks and welcome @timcera.

@xylar xylar merged commit d6c9bac into conda-forge:main Mar 8, 2023
@timcera timcera deleted the newhome branch March 24, 2023 00:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants