Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[question] Architectures other than x86_64

See original GitHub issue

Looks like conan center is not going to have binaries for anything other than x86_64 anymore. What if I need them (say x86 and armv8) and don’t like to rebuild the world for every workstation / CI job? What would you recommend to make them available locally? Forking conan-center-index repo and recreating all CI infrastructure for Travis CI/AppVeyor doesn’t look a viable option.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

SSE4commented, Jun 10, 2020

we don’t build for all architectures, right now we only build for x86_64. it may change in future if there will be high demand for them. we also don’t test all compilers, operation systems, etc., only the most popular. for other architectures:

x86 appears to be slowly dying, e.g. it’s already deprecated on macOS and Linux distributive are also removing that
ARM doesn’t appear to be very frequently requested, but there are desktop systems moving to ARM (e.g. Apple might move their laptops to ARM in future, there are existing Android ARM laptops, etc.), so it might get more attention in the near feature
mips, PowerPC, Sparc even less popular right now

but we still accept patches and fixes for other configurations, such as x86, ARM, Android, iOS, MinGW, FreeBSD, etc.

0reactions

uilianriescommented, Jun 10, 2020

If I submit a PR to conan-center-index and something goes wrong, how will I know what fails exactly? All your CI logs are now internal and I see 403 Forbidden trying to look into someone’s CI failure, say ci-conan-prod.jfrog.team/job/conan-center-pull-request/job/PR-1856/15/display/redirect

You don’t need to access the CI log directly, because it’s available for download:

Screenshot_2020-06-10 Add open62541 1 0 1 by syoliver · Pull Request #1856 · conan-io conan-center-index

I’m very curious about how you organized your CI scripts. If I commit changes to one recipe, will you rebuild everything? Some time ago I tried to solve a similar problem locally via build=outdated bub did no succeed as conan always run test_package recipe even for up-to-date packages (conan-io/conan-package-tools#434). You should have some secret weapon, right?

Please, read https://github.com/conan-io/conan-center-index/issues/30