From: tumashu <tumashu@163.com>
To: 53008@debbugs.gnu.org
Subject: [bug#53008] Re: bug#53008: [PATCH 0/3] Add plugins to Thunar
Date: Mon, 14 Mar 2022 07:57:13 +0800 (CST) [thread overview]
Message-ID: <2c6ab28b.1ac.17f85b6f072.Coremail.tumashu@163.com> (raw)
In-Reply-To: <yguy23vv7c2.fsf@netpanic.org>
I think it is controled by: THUNARX_DIRECTORY.
```
./thunarx-provider-factory.c\0158: dp = g_dir_open (THUNARX_DIRECTORY, 0, NULL);
./thunarx-provider-module.c\0180: path = g_build_filename (THUNARX_DIRECTORY, type_module->name, NULL);
./Makefile\0699: -DTHUNARX_DIRECTORY=\"$(libdir)/thunarx-$(THUNARX_VERSION_API)\" \
./Makefile.in\0699: -DTHUNARX_DIRECTORY=\"$(libdir)/thunarx-$(THUNARX_VERSION_API)\" \
./Makefile.am\05: -DTHUNARX_DIRECTORY=\"$(libdir)/thunarx-$(THUNARX_VERSION_API)\" \
```
While THUNARX_DIRECTORY is defined in Makefile:
```
AM_CPPFLAGS = \
-I$(top_srcdir) \
-DG_LOG_DOMAIN=\"thunarx\" \
-DTHUNARX_COMPILATION \
-DTHUNARX_DIRECTORY=\"$(libdir)/thunarx-$(THUNARX_VERSION_API)\" \
$(PLATFORM_CPPFLAGS)
```
So, I think we should deal with this like xfce-panel-plugins.patch:
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/patches/xfce4-panel-plugins.patch
next prev parent reply other threads:[~2022-03-13 23:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 15:39 [bug#53008] [PATCH 0/3] Add plugins to Thunar Simon Streit
2022-01-04 15:50 ` [bug#53008] [PATCH 1/3] gnu: Add thunar-archive-plugin Simon Streit
2022-01-04 15:50 ` [bug#53008] [PATCH 2/3] gnu: Add thunarx-python Simon Streit
2022-01-04 15:51 ` [bug#53008] [PATCH 3/3] gnu: Add thunar-shares-plugin Simon Streit
2022-01-08 22:26 ` [bug#53008] [PATCH 0/3] Add plugins to Thunar Ludovic Courtès
2022-03-13 23:57 ` tumashu [this message]
2022-03-15 1:14 ` [bug#53008] Re: Re: bug#53008: " tumashu
2022-03-18 6:27 ` [bug#53008] " tumashu
2023-08-25 10:15 ` 宋文武 via Guix-patches via
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2c6ab28b.1ac.17f85b6f072.Coremail.tumashu@163.com \
--to=tumashu@163.com \
--cc=53008@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).