Building XFCE on Cygwin

Maarten Boekhold boekhold at
Wed Jul 14 16:22:26 CEST 2004

Brian J. Tarricone wrote:

>>So, there's a few things to decide:
>>(1) Can we add G_MODULE_{EXPORT|IMPORT} to all relevant functions

> sounds fine to me.

OK, I'll start working on this. I must note however that (1) I don't 
have much spare time (wife doesn't really like "all this computer 
stuff", esp. since my day job also involves computer, must be a familiar 
problem to many) and (2) I'm going on vacation on monday. So if anybody 
else wants to have a go at it, feel free.

>>(2) How do we pass the .def file through libtool to the linker
> you could also try whatever_LIBADD, or maybe something like this:
>   whatever_LINK = $(LIBTOOL) --mode=link $(CCLD) $(AM_CFLAGS $(CFLAGS) \
> 	$(AM_LDFLAGS) $(LDFLAGS) $(def_file) -o $@
> endif

Wll have to test this...

> i don't think this is a problem.  the plugin sources are dependent on 
> the mcs-manager or panel header files.  the .def file could be installed 
> like just another header (on win32 anyway).  the problem is that we'll 
> need some automake magic so that the $(def_file) variable in 
> gets populated with the _full path_ to this file.

$(include)/whatever.def (or whatever the variable name is?)

> on the other hand, we can distribute it as data (e.g., 
> /usr/share/xfce4/devel/plugin.def), and then plugin authors can 
> copy and include this with their plugin.  if exports are added to the 
> panel later (they shouldn't be, but let's just say...), it really 
> doesn't matter if the plugin's copy gets updated since the plugin 
> wouldn't be using them anyway (obviously, if the plugin author decides 
> to use one of these new interfaces, they have to get a new plugin.def 
> file).

Makes total sense, and I vote for installing the .def file(s) in devel. 
Is there any documentation that needs to be updated for this for plugin 


More information about the Xfce4-dev mailing list