-
Notifications
You must be signed in to change notification settings - Fork 27
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
Building from sources works in buster docker image but does not in bullseye #116
Comments
I have managed to build However, I then build Valhalla. On the latest
When I instead clone RUN git clone --depth 3 --recursive https://github.com/kevinkreiser/prime_server.git && cd prime_server && git checkout 43715e5 && \
cmake -B build . && cmake --build build && make -C build install |
haha we just merged a pr that handles the install directories (#115 ) seems like, at least on bullseye, this doesnt work properly. my question to you would be, can you see what directory the headers are installed into? are there in |
The headers are indeed installed in FROM node:16-bullseye as build
### Compilation de Valhalla
RUN apt-get update && \
apt-get install -y cmake make libtool pkg-config g++ gcc curl unzip jq lcov protobuf-compiler \
vim-common locales libcurl4-openssl-dev zlib1g-dev liblz4-dev libprotobuf-dev && \
apt-get install -y libgeos-dev libgeos++-dev libluajit-5.1-dev libspatialite-dev libsqlite3-dev wget sqlite3 spatialite-bin python3-shapely && \
apt-get install -y libsqlite3-mod-spatialite python3-pip
WORKDIR /home/prime-server
RUN apt-get install -y git cmake autoconf automake pkg-config libtool make gcc g++ lcov libcurl4-openssl-dev libzmq3-dev libczmq-dev
RUN git clone --depth 1 --recursive https://github.com/kevinkreiser/prime_server.git && cd prime_server && \
cmake -B build . && cmake --build build && make -C build install
RUN ls /usr/local/include
RUN ls /usr/local/include/prime_server
|
Awesome thanks for confirming I'll fix it this evening! |
@azarz should be fixed now, i tested with a clean install via docker to verify (at least on ubuntu, should work in debian as well) |
I can confirm this works, thanks! |
Linked to #83 I think
I'm building prime_server from source using a Dockerfile.
From the
node:16-buster
image, the compilation worksHowever, from
node:16-bullseye
, if fails with th following error:The text was updated successfully, but these errors were encountered: