Replies: 5 comments 10 replies
-
Yes
definitely should be, can you run cmake with
Shouldn't need these either, vcpkg will build both Proj & libpq. Note that if you switch an existing build directory to |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I've had another crack after cleaning up some stuff in /usr/local - old libgit from the previous build requirements I think and from a clean clone of kart with the couple of additions @craigds made I get as far as step 18/38 in the build then it blows up with Which looks to be caused by .python-version specifying 3.7.8 and that not being installed - removing that file allows things to get through the configuration stage but then during the build stage things blow up in psycopg wheel building I believe this is a python version issue - psycopg/psycopg2@442f300 Macros were originally changed in 3.10 but backed out and then put back in for 3.11 (which it looks like the build has found on my machine) - python/cpython#83754. It looks like psycopg2 2.9.5 has support for 3.11 https://github.com/psycopg/psycopg2/releases/tag/2_9_5 |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
For curiosity's sake, can you install Python 3.10.9 from https://www.python.org/downloads/macos/ and then (with a clean build dir) do: |
Beta Was this translation helpful? Give feedback.
-
|
Sure thing, will do in the next few hours. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting message running that... It does look to be using the correct python though |
Beta Was this translation helpful? Give feedback.
-
|
I did a It looks like the compiler toolchain knows about the SDK path and there is a unistd.h but... there isn't a /usr/include (MacOS having separate SDK paths for targeted builds) so maybe the cmake config isn't passing through the correct path to includes??? |
Beta Was this translation helpful? Give feedback.
-
|
I've hit this before but was never sure if it was just a messed up xcode environment or a reproducible issue. Explanation - use the C compiler instead of the C++ compiler since it is more likely to be able to find unistd.h (although it seems the C++ compiler can find it too sometimes - don't know why). However we still need the C++ std library to be linked in so that's the other change. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
I’ll give that a go. |
Beta Was this translation helpful? Give feedback.
-
|
No joy with that I'm afraid - made the change after removing build, ran the configure step then the build and got the same error. I'm travelling at the moment but will try on a non-ARM machine when I get back. |
Beta Was this translation helpful? Give feedback.
-
|
@olsen232 @rcoup Some more info on this... I get the same build failures on an Intel Mac but have been able to get it to go all the way through with the following (master as of a few minutes ago):
This is on MacOS 13.1 with Xcode 14.1 and |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
On an ARM Mac, running macOS 13.0.1/XCode 14.2, I have no One suggestion is to try installing the Python 3.10 universal release from python.org and see if that makes a differemnce. CMake should find it first, but if it doesn't adding There's some known quirks if you change Python interpreters once CMake is configured, so start from a fresh build directory. |
Beta Was this translation helpful? Give feedback.
-
|
I thought it might have been the particular Python install, something to do with being a Framework build and will try again with that download. |
Beta Was this translation helpful? Give feedback.
-
|
It should work with Homebrew Python (and it definitely does for some people), just trying to narrow down the options. macOS CI (intel/x64 though) runs against the Python.org release. |
Beta Was this translation helpful? Give feedback.
-
|
Yep, the build I had which went through was from Homebrew but that needed the SDKROOT variable - I'll update after trying the python.org release. |
Beta Was this translation helpful? Give feedback.
-
|
I've got back to trying with the Python.org python and still there is the same issue, things don't build with a |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@rcoup @olsen232
Hi guys.
Would you expect a Mac OS build to work on master currently?
Following https://github.com/koordinates/kart/blob/master/CONTRIBUTING.md#building-the-development-version-with-cmake I need to add a
brew install git swig pandoc- the OS git version isn't found by cmake and add a couple of paths ascmake -B build -S . -DWITH_VCPKG=ON -DCMAKE_PREFIX_PATH=/Applications/Postgres.app/Contents/Versions/15 -DPROJ_DATADIR=/opt/homebrew/Cellar/proj/9.1.1/share/proj. With that the setup step runs with some warningsAfter that running
cmake --build buildthings go a bit pear shaped.There are a whole bunch of errors around 'undeclared identifier'.
Is it worth trying to build master at this point or should I hold off there?
Beta Was this translation helpful? Give feedback.
All reactions