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

[WIP] fmi4cpp: add new package #47240

Closed
wants to merge 10 commits into from

Conversation

prudhomm
Copy link
Contributor

I also pushed the changes for libzip from #47230, if this PR is merged then remains only the changes for fmi4cpp

Comment on lines +60 to +63
variant("bzip2", default=True, description="Enable bzip2 support")
variant("lzma", default=True, description="Enable lzma support")
variant("openssl", default=True, description="Enable openssl support")
variant("zstd", default=True, description="Enable zstd support")
Copy link
Contributor

@bernhardkaindl bernhardkaindl Oct 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some initial questions:
fmi4cpp/package.py has: depends_on("libzip")
So fmi4cpp does not need all those variants enabled by default, correct?

I moved the remaining questions to the PR where those changes should only be: #47230 (review)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bernhardkaindl I set the same defaults as in the cmake of libzip.

please the PR for libzip is actually here #47230 could you please that one instead. I made the mistake to merge the libzip branch to the develop branch on feelpp/spack ( I needed it for some other work but now it spreads through the other PR I made from feelpp/spack

Copy link
Contributor Author

@prudhomm prudhomm Oct 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bernhardkaindl all the variant are enabled by default by libzip so if they are not installed by spack, libzip will have a look on the host system and use that. That's what happened to me and it created havock in my apps at linking stage because of conflicting libs. the previous versions of libzip spack package were not very good from this point of view.

I checked up to version 1.7 of libzip and all the variants are enabled:
https://github.com/nih-at/libzip/blob/v1.7.1/CMakeLists.txt#L10

self.define_from_variant("ENABLE_GNUTLS", "gnutls"),
self.define_from_variant("ENABLE_MBEDTLS", "mbedtls"),
self.define_from_variant("ENABLE_OPENSSL", "openssl"),
self.define_from_variant("ENABLE_BZIP2", "bz2"),
Copy link
Contributor

@bernhardkaindl bernhardkaindl Oct 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This variant does not exist. Its current name is "bzip2":

==> Installing libzip-1.11.1-5aupui6t6j4ve3d6i3ffgslk3okyxkcf [28/29]
==> Error: KeyError: '"bz2" is not a variant of "libzip"'

It looks you should uninstall these recipes and install them from source to be sure to catch such errors before you submit a PR, I think.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah ok may be I was too fast to rename bz2 to bzip2 and didn't cheeck it now it is fixed in #47230

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd just let this PR wait for now.
(you can just close it, and re-open it again before you update it) until #47230 is merged.

It looks like can just remove the changes to libzip as this package does not depend on the new variants, which are the only change that is in that PR AFAICS.

So I wonder: Why you even add those variants?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fmi4cpp doesn't care about the variants of libzip, I agree. However it is, IMHO, necessary to add them to libzip and properly define the relationship with them otherwise we get libzip depends from the host libs and from spack libs that libzip depend upon.

@bernhardkaindl bernhardkaindl marked this pull request as draft October 27, 2024 12:42
@bernhardkaindl bernhardkaindl changed the title fmi4cpp: add new package [WIP] fmi4cpp: add new package Oct 27, 2024
@prudhomm prudhomm closed this Oct 27, 2024
@prudhomm prudhomm deleted the 11-fmi4cpp-add-package branch October 27, 2024 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fmi4cpp: add package fmi4cpp: add new package
2 participants