-
Notifications
You must be signed in to change notification settings - Fork 90
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
Cannot build using MinGW #21
Comments
Use the source package or follow the instructions on how to create the configure script and make files: https://github.com/libyal/libesedb/wiki/Building#git |
Thank you for your answer. |
That's not it. From: https://github.com/libyal/libesedb/wiki/Building#source-package
See actual wiki page for the link. One note though, it's currently experimental versions that are available so to be verbose:
|
I'm also having problems using msys when running make I get:
|
@sudofly which Windows API version (WINVER) ? |
i'm compiling on Windows 10 and I set the WINVER var to 0x0501 as follows:
|
Yes, however the issue seems to be somewhere else: c:\mingw\include\winioctl.h IOCTL_DISK_GET_LENGTH_INFO is just a convenience macro for CTL_CODE
Indicates that something is acting up in the MinGW definitions. |
hmm.. we are wandering out of my skillset now :-) is there a better way I can compile a windows executable, or even better somewhere where I can download pre-built binaries ? Thanks |
Use Visual Studio
Not officially, the project status is experimental and a single person effort, maintaining binary builds, especially for Windows, it too time consuming. |
case and point I guess! I'll try and find an instance of VB and build from there. Cheers all! |
I tried both Sections in https://github.com/libyal/libesedb/wiki/Building:
"Using Minimalist GNU for Windows (MinGW)" and "Using MSYS-MinGW"
(Yes, I use the msys shell and not the native Windows shell)
The problem is
" ./configure . No such file or directory"
make reports that no makefile is present, even though makefile.am is in the directory.
The text was updated successfully, but these errors were encountered: