[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#43182] [PATCH 3/3] gnu: nomad: Update to 0.2.0-alpha-100-g6a565d3.

From: Ricardo Wurmus
Subject: [bug#43182] [PATCH 3/3] gnu: nomad: Update to 0.2.0-alpha-100-g6a565d3.
Date: Mon, 07 Sep 2020 13:02:26 +0200
User-agent: mu4e 1.4.13; emacs 27.1

Mike Rosset <> writes:

>>> +                 `("GI_TYPELIB_PATH" ":" prefix (,gi-path ,(getenv 
>>> +                 `("GIO_EXTRA_MODULES" ":" prefix (,(getenv 
>> You can wrap a few lines here to stay under the 78 columns limit.
>>> +                 `("GST_PLUGIN_SYSTEM_PATH" ":" prefix ,gst-plugins)
>>> +                 `("NOMAD_WEB_EXTENSION_DIR" ":" prefix (,ext-path)))
>> If NOMAD_WEB_EXTENSION_DIR is wrapped, it is up to the user to set
>> it. Don't we want to keep it as a native-search-paths so that any
>> extension package to nomad is automatically added to this variable?
> No, web extension is a GTK term for extending the WebKit process
> which runs outside of the GTK/Glib process.
> The extensions are dynamic libraries and you need to tell the
> WebKitWebContext where to look for them. Normally I'd just substitute
> in the $(libexecdir).  But we need to use the libs in the build directory for
> testing.  And I can't use libtool --mode=execute -dlopen. Because the
> WebKit process does the dlopen.

During the build you could use LD_LIBRARY_PATH, no?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]