There are two other possible ways to run GUI apps in WSL, other than WSLg: Make sure that your Windows 10 system is up-to-date, then proceed to Optional Updates, and KB5020030 should be available for installation.īoth Windows 10 and Windows 11 users should then be able to install or update via: wsl -install Currently, you'll need the KB5020030 optional Preview update for Windows 10. With the release of the WSL application (which is installed from the Microsoft Store), WSLg is now available to Windows 10 users as well, as long as your build number ends in. Ironically, however, it does use the Remote Desktop Protocol (with extensions) behind the scenes to do this. WSL on Windows 11 introduced a new feature called WSLg that provides a Wayland/Weston/Xwayland distribution to enable running GUI apps directly on the Windows desktop. While you don't mention which Windows version you are using, it would appear from the second error that you are probably running Windows 10. While there are multiple options for running GUI apps under WSL, the only one that is "integrated with the system" is WSLg. okĬhecking how to run the C preprocessor.Some people suggested that I could use it through Remote Desktop Connection, but I want it to be integrated with the system. stripĬhecking command to parse /usr/bin/nm -B output from gcc object. printf %s\nĬhecking for archiver support. pass_allĬhecking how to associate runtime and link libraries. rĬhecking how to recognize dependent libraries. func_convert_file_noopĬhecking for /usr/bin/ld option to reload object files. func_convert_file_noopĬhecking how to convert x86_64-unknown-linux-gnu file names to toolchain format. yesĬhecking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format. yesĬhecking whether the shell understands " =". 1572864Ĭhecking whether the shell understands some XSI constructs. BSD nmĬhecking the maximum length of command line arguments. usr/bin/nm -BĬhecking the name lister (/usr/bin/nm -B) interface. yesĬhecking for BSD- or MS-compatible name lister (nm). usr/bin/ldĬhecking if the linker (/usr/bin/ld) is GNU ld. bin/sedĬhecking for grep that handles long lines and -e. x86_64-unknown-linux-gnuĬhecking for a sed that does not truncate output. x86_64-unknown-linux-gnuĬhecking host system type. $/lib/python2.6/dist-packagesĬhecking build system type. yesĬhecking whether we are using the GNU Objective C compiler. usr/bin/pkg-configĬhecking pkg-config is at least version 0.9.0. noĬhecking for _FILE_OFFSET_BITS value needed for large files. (cached) yesĬhecking for special C compiler options needed for large files. none neededĬhecking for style of include used by make. yesĬhecking for gcc option to accept ISO C89. noĬhecking whether we are using the GNU C compiler. a.outĬhecking whether we are cross compiling. yesĬhecking for C compiler default output file name. gnutarĬhecking whether to enable maintainer-specific portions of Makefiles. yesĬhecking how to create a ustar tar archive. bin/mkdir -pĬhecking whether make sets $(MAKE). usr/bin/install -cĬhecking whether build environment is sane. configure, the error came up and here is what it says:Ĭhecking for a BSD-compatible install. configure # run the `configure' scriptĪnd after I run. % cd gedit-3.0.3 # change to the toplevel directory % gzip -cd gedit-3.0.3.tar.gz | tar xvf - # unpack the sources PyGobject 2.28.x and gobject-introspection 0.9.0 are required to enable python Gedit requires GTK -3.0.x and GtkSourceView 3.0.x and libpeas 1.0.x libraries. I want to install gedit 3.0.3 and I just followed all steps in the README: My system is newly installed 10.10 ubuntu with all updates patched.
0 Comments
Leave a Reply. |