-
Notifications
You must be signed in to change notification settings - Fork 49
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
Issues using libevtx as a library #15
Comments
Can you provide more information about the compilation steps you are following. Also see: https://github.com/libyal/libevtx/wiki/Building |
I was able to download and compile using your build instructions. That is:
I copied evtxtools/evtxtools.c into a file called src/main.cpp. I then ran the following command
And got the following error:
As far as I can tell there is no libcerror.h in the libevtx git repo (even after all dependencies are downloaded). Do you have any suggestions? |
My first question is why do you copied this code? The reason that you get the error is that you're not passing the correct pre-compiler definitions. Also see: You compilation configuration expects libcerror to be a stand-alone library. Setting up the proper build environment and setting is handled by |
Hi,
I am able to compile (from the git repo) and use evtxtools as intended. However, I would like to use libevtx as a library to parse and convert evtx files in my own code. I'm attempting to use parts of evtxtools/evtxtools.c. However, when I try to compile (I have included all the appropriate dependency directories) I am getting many errors such as:
/home/user/Documents/libevtx/evtxtools/evtxtools_libcerror.h:45:23: fatal error: libcerror.h: No such file or directory
When I run a find command looking for "libcerror.h" it does not find anything. However, it appears that there is a libcerror_error.h file. If I modify the include a similar error pops up for a different file. I have downloaded all the dependencies using synclibs.sh. Do you have any suggestions? Thanks!
The text was updated successfully, but these errors were encountered: