If you are encountering issues while using and/or compiling Browser Window, this page is here to help you fix them. If your issues isn't explained in here, please file the issue here.
TODO: Paste console error here...
This error means that the GTK development files are not available.
./src/err.h:8:10: fatal error: 'stdlib.h' file not found
./src/err.h:8:10: fatal error: 'stdlib.h' file not found, err: true
thread 'main' panicked at 'Unable to generate FFI bindings! ...
bindgen
might fail when clang
isn't properly installed.
To fix this for Debian-like systems, try apt install libclang-dev
.
To fix this on Windows, install clang here.
src/application/win32.h:18:10: fatal error: 'Windows.h' file not found
This error occurs when the MSVC compiler can't find the Windows SDK headers.
This could mean that you didn't install the Windows SDK.
If you did, it could also mean that MSVC environment variables aren't set properly.
This tends to happen when using bindgen
(see feature bindgen
).
To fix this, call cargo
from within the 'Cross Tools Command Prompt for VS 20**'.
If you want to work with another type of console, like that of Msys2 for example, you can do to following.
Run vcvarsall.bat
(usually located in C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Auxiliary\Build
) from the command line with your architecture and SDK version provided as arguments. Run it without arguments for more information.
When this is done, your console should be able to build browser-window-c
.
But this needs to be done for every console that you want to build Browser Window with, so this is not actually a long-term solution.
libcpmt.lib(winapisupp.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MT_StaticRelease' doesn't match value 'MD_DynamicRelease' in libbrowser_window_ffi-d71871b45632c28d.rlib(cef.o)
LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of other libs; use /NODEFAULTLIB:library
This happends when you didn't follow the getting started guide properly.
You need to built CEF with the /MD
flag.
Sometimes you may run into (weird) C++ compilation errors when building Browser Window. If you are using a published version of Browser Window, this should generally not happen. In case it does happen, it is likely to be a incompatibility with the CEF API. CEF release new major version very regurarely.
Try using a version of CEF that is stated as being the latest version known to work, as stated in the getting started guide.
If that doesn't work, please submit an issue.
thread 'main' panicked at 'Unable to initialize application: c(bw) error: [1] unable to execute CEF process (are all required files located near the executable?)', ...
This may be because the library and resource files were not copied to your executable directory.
If this is not done, your program will not get past Application::initialize
.
Execute setup-cef-files.sh
or setup-cef-files.bat
.