-
Notifications
You must be signed in to change notification settings - Fork 799
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
nad2bin being run while building prevents cross compiling #1235
Comments
I haven't got an answer to your question. But I have a counter-question to my fellow PROJ developers: Do we still have a need for |
The Debian package for PROJ 5.2 builds fine on arm*, including tests. This issue doesn't have enough information to determine what causes the issue. It may be a cross-compilation issue. |
We can move |
@sebastic I'd be happy to provide more info, what would you need? Or do you have a reference to a script that build on arm? cheers! |
@sebastic It compiles on ARM in the Debian case. Not cross-compilation ? I can indeed see that nad/Makefile.am assumes to be able to run the nad2bin executable that it has compiled, which can be problematic with cross-compilation indeed. But I don't see why it would have worked better in 4.9 as you mentionned in your email @3nids . Maybe you need to tweak nad/Makfile.am to run a nad2bin executable of the architecture on which you build on. |
In my opinion it belongs in the PROJ source tree. No need to complicate the proj-datumgrid project by having to build C programs.
Details about your build environment & full build logs for starters.
See the Debian package sources.
On, build and target architectures are the same. There are arm64 build daemons that also build armhf packages. |
Maybe asking this differently, is there a way to use the cmake option |
No, you'll have to hack into nad/Makefile.am to disable the use of nad2bin |
Thanks @rouault |
I'm running Xenial too. No problem for me with hacking Makefile.am. You probably just need to run ./autogen.sh |
Any chance this might land in a release soon? I just encountered it myself under the exact same circumstances--attempting to cross-compile from Ubuntu to Android. Thanks! |
See #1267. |
This breaks cross-compiled Bazel builds due to OSGeo#1235. We appear to never need `nad2bin`, so we can safely just exclude this entire directory.
We need to teach `bazci` about the configurations and add a new script to support this. Also run both the Linux cross job and the Windows cross job with `-c opt`, so we can start getting optimized builds. Also add a small hack to `proj` to work around OSGeo/PROJ#1235. Closes cockroachdb#66208 Closes cockroachdb#66209 Release note: None
66455: build: add script for cross-compilation job to windows via bazel r=rail a=rickystewart We need to teach `bazci` about the configurations and add a new script to support this. Also run both the Linux cross job and the Windows cross job with `-c opt`, so we can start getting optimized builds. Also add a small hack to `proj` to work around OSGeo/PROJ#1235. Closes #66208 Closes #66209 Release note: None 66498: roachprod: update to recommended ubuntu focal image r=rail a=rickystewart The previous version was deprecated -- see #66183 for context. Release note: None Co-authored-by: Ricky Stewart <[email protected]>
I am trying to compile Proj 5.2 for Android and I am facing this error:
It tries to run nad2bin on the environnement, but nad2bin has been compiled for Android.
What is the proper approach?
I am using autotools, but I failed to disable building nad2bin (is it possible?). But is it the right approach?
The text was updated successfully, but these errors were encountered: