-
Notifications
You must be signed in to change notification settings - Fork 15
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
Build issue on OS X #24
Comments
For debugging this one, we may bypass Maven completely and invoke
The message gives the impression that compilation succeeded and that it was at the time of linking to PROJ that a problem occurred (maybe the library has not been found). Is that the case? |
The output seems similar, but maybe you can make sense of it. I am seeing similar errors on Windows by the way. Also in a conda environment similar to this so that probably should be expected. |
This is on openjdk 11:
Do I need to install openjdk 13 or should this also work on 11? |
I think this is a C/C++ issue here; Java is not involved at all in |
conda is usually my first stop since it is easy to isolate environments. It is entirely possible that some env vars are set incorrectly by the various conda packages or that some additional env vars needs to be set. Tomorrow I will try a more conventional Windows build and see if I can make that work. |
I see only PROJ C++ API in the symbols not found, which is new in PROJ 6. So my current hypothesis is that the linker found an earlier version of PROJ. Maybe a matter of search order in some |
Possibly, although I can't figure out which env var to change if that is the case
|
Did you compiled PROJ with
(On MacOS, it may be necessary to search also in
We need to make sure that the linker links the ".15" version. |
I did not compile PROJ at all - conda installs prebuild packages. Conda installs everything in the environment base library, e.g. |
At least on Fedora, PROJ 6 is not yet available in the pre-built packages last time a checked; it installed PROJ 5 only. This is why I had to build PROJ 6 locally. It should be possible to recognize in which situation we are by the number in the library filename. If |
I of course install the most recent version of PROJ. conda is generally up to date as there is no concept of long-term releases etc. |
For what it's worth, the following steps seemed to work on macOS 10.15:
|
This is probably not super unexpected since this has not been tested on OS X at all. Anyway, it is possibly a problem that occurs on more that OS X.
My setup using conda:
and then running maven in the PROJ-JNI repository root:
The text was updated successfully, but these errors were encountered: