>Hello. I just did an sbuild on unstable and got the following error: > >dh_auto_configure: cd obj-x86_64-linux-gnu && cmake >-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None >-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var >-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON >-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run >"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON >-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_INSTALL_LIBDIR=lib >-DLIBCLANG_T=/usr/lib/llvm-8/lib/libclang.so >-DLIBCLANG_INCLUDE_T=/usr/lib/llvm-8/include .. returned exit code 1 make[1]: >*** [debian/rules:31: override_dh_auto_configure] Error 2 make[1]: Leaving >directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:28: binary] Error 2 >dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
>Trying to build your .dsc using cowbuilder, I get the following: > >-- LIBSSH_LIB is set to /usr/lib/x86_64-linux-gnu/libssh.so >-- Some or all of the gtk libraries were not found. (missing: GTK2_GTK_LIBRARY >GTK2_GTK_INCLUDE_DIR GTK2_GDK_INCLUDE_DIR GTK2_GDKCONFIG_INCLUDE_DIR >GTK2_GDK_LIBRARY) CMake Error at CMakeLists.txt:252 (message): > Could not locate GTK. > >Looks like the CMakeLists looks for GTK2, even though you're building >against GTK+3 version of wxWidgets. Thank you both for your input. I didn't notice this because I was building in a virtualbox guest with both GTK+ 2 and 3 wxWidgets versions installed, and had used update-alternatives to select 3. Testing with sbuild I get the same issue as you, and it is indeed caused by the wrong wxWidgets version being found. That seems to be due to codelite's dependency on libwxsqlite3-3.0, which still Depends on the GTK+2 version even though wxsqlite3 itself now uses the GTK+3 one. So apt installs both wxWidgets versions and the GTK+2 one wins the alternatives race. That's easily solved conflict in a normal situation, but not (iiuc) in sbuild/cowbuilder. Perhaps it could be fixed kludgily in the codelite d/rules, but it's really a wxsqlite bug which I'll report. Regards, David Hart
