-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[fastgltf] Add versions 0.7.1, 0.7.2, 0.8.0 #22960
base: master
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
0667a81
to
3ffc908
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
# See https://github.com/spnda/fastgltf/commit/aa90dfac290584f35f47dd7c1634f23d376a7207 | ||
if Version(self.version) >= "0.6.0": | ||
self.requires("simdjson/3.7.0") | ||
else: | ||
self.requires("simdjson/3.2.1") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# See https://github.com/spnda/fastgltf/commit/aa90dfac290584f35f47dd7c1634f23d376a7207 | |
if Version(self.version) >= "0.6.0": | |
self.requires("simdjson/3.7.0") | |
else: | |
self.requires("simdjson/3.2.1") | |
self.requires("simdjson/3.7.0") |
Are the older versions incompatible with the latest simdjson?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I originally had what you are suggesting, but removed that since it caused build failures on older versions.
Version 3.2.2 moved around a lot of headers and includes, which broke my base64 decoders as they didn't include the headers properly, and the code only worked because simdjson.h
leaked the SIMD intrinsics. I fixed that in 0.6.0, which is why all versions since then have supported any of the more recent versions of simdjson. See simdjson/simdjson#2039.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As noted in #22960 (comment), I would be happy to remove these legacy versions of fastgltf since they're pretty old and include a large number of issues. And I don't think anybody actually uses them anymore.
I have updated this PR to now also include version data for 0.7.2 and 0.8.0. I didn't want to open a separate PR, so I've just included this here. @valgur could you please review this? @toge I saw #24168 and I would be totally fine with removing old versions of fastgltf, which would allow you to remove all of the old versions of simdjson. Only 0.5.0 and earlier required those versions of simdjson, and 0.5.0 came out in May 2023 so it can definitely be viewed as legacy in my opinion. |
Conan v1 pipeline ❌Failure in build 2 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. Conan v2 pipeline ❌
The v2 pipeline failed. Please, review the errors and note this is required for pull requests to be merged. In case this recipe is still not ported to Conan 2.x, please, ping Failure in build 2 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. |
Specify library name and version: fastgltf/0.7.1
Just a bugfix patch with minor additions, and I've bumped the simdjson version to 3.7.0 in this recipe because I think there's nothing wrong with telling it to use the latest version directly?