-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
Failing to compile libosmium: 'protozero/types.hpp' file not found #342
Comments
Looks like there is an error somewhere in what you did but from your vague description ("latest version of libosmium and protozero", "set up everything properly", "manually edited the protozero include path") we can't figure out what that is. Show us all the commands you used and their output. Maybe we can figure it out then. |
I cloned the latest version of libosmium and protozero from GitHub, and they are saved in the same directory. Then in the libosmium directory, I created the
After that, I compiled the script under examples ( That's pretty much all the steps I took just to try running osmium_read.cpp under the examples directory. Here is the version of GCC and Clang that I have:
I'm not sure where I messed up, and I hope that's enough information. |
You can't just compile a program using |
Ok I see. That works for me now, thanks! Now, I still have the same file not found problem when I try to create my own project using osmium. I simply just inserted
When I compiled with
|
Sorry, this isn't a C++ help line, but a bug tracker for Osmium. Help on how to set up your own CMake configuration is waay beyond what we can provide here. |
Hi, I'm using the latest version of libosmium and protozero, and am currently trying to set up everything. I tried to run
osmium_read.cpp
under theexamples
directory and receive the error:I followed through the guide and set up everything properly. I also saw this ticket here (osmcode/osmium-tool#127) and manually edited the protozero include path, but I still get this error. How can I resolve this issue?
The text was updated successfully, but these errors were encountered: