Re: Desktop file and exec path

Andreas Schwab pronuncio' le seguenti parole il 08/02/2007 17:55: Benoit Sigoure <[EMAIL PROTECTED]> writes: Although two ways of solving this issue have been proposed already, there is also another way out: using an AC_CONFIG_FILES. glpegsolitaire.desktop.in ---

Re: Desktop file and exec path

Quoting Andreas Schwab <[EMAIL PROTECTED]>: Benoit Sigoure <[EMAIL PROTECTED]> writes: Although two ways of solving this issue have been proposed already, there is also another way out: using an AC_CONFIG_FILES. glpegsolitaire.desktop.in ---

Re: $(datadir) and @datadir@

On Thu, Feb 08, 2007 at 08:13:18PM +0100, Enrico Sardi wrote: > I've read autoconf and automake manuals but I've not yet fully > understand a thing...what's the difference between writing $(datadir) > and @datadir@ in a makefile.am? If you use $(datadir), the user can override it at build time (

$(datadir) and @datadir@

Hi all, I've read autoconf and automake manuals but I've not yet fully understand a thing...what's the difference between writing $(datadir) and @datadir@ in a makefile.am? Many thanks Enrico

Re: AM_LIBADD

Hello Akim, * Akim Demaille wrote on Thu, Feb 08, 2007 at 10:54:56AM CET: > >>> "RW" == Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > Hello Akim, > > Hi Ralk, I missed your answer :) Hehe, interesting typo. Ralph is a mo

Re: Desktop file and exec path

Hello Andreas, all, I think most was already said in this thread. Let me add a small nit: * Andreas Schwab wrote on Thu, Feb 08, 2007 at 02:04:10PM CET: > > Use @DATADIR@ in glpegsolitaire.desktop.in and put this in your makefile: > > glpegsolitaire.desktop: $(srcdir)/glpegsolitaire.desktop.in

Re: Desktop file and exec path

Benoit Sigoure <[EMAIL PROTECTED]> writes: > Although two ways of solving this issue have been proposed already, there is > also another way out: using an AC_CONFIG_FILES. > > glpegsolitaire.desktop.in > -- > [Desktop Entry] > Name=Pe

Re: Desktop file and exec path

Quoting Enrico Sardi <[EMAIL PROTECTED]>: I have a desktop file like this: glpegsolitaire.desktop -- [Desktop Entry] Name=Peg Solitaire Comment=A "Peg Solitaire" for Gnome Exec=glpegsolitaire Icon=glpegsolitaire.png Terminal=false T

Re: Desktop file and exec path

Enrico Sardi <[EMAIL PROTECTED]> writes: > glpegsolitaire.desktop > -- > [Desktop Entry] > Name=Peg Solitaire > Comment=A "Peg Solitaire" for Gnome > Exec=glpegsolitaire > Icon=glpegsolitaire.png > Terminal=false > Type=Application >

AW: Desktop file and exec path

Dear listmembers, dear Enrico, IMHO this is a sed-job to be called from within automake: cutcutcutcutcutcutcutcutcutcutcutcutcutcutcutcutcutcutcutcutcutcutcutcut #!/bin/sh MYNAME=$1 cp -p desktop desktop.save sed "s/Exec=.*/Exec=${MYNAME}/g" desktop.save > desktop rm -f desktop.save cutcutcutcutcu

Re: Desktop file and exec path

Ralf Wildenhues pronuncio' le seguenti parole il 05/02/2007 20:35: Hello Enrico, * Enrico Sardi wrote on Sun, Feb 04, 2007 at 11:56:07PM CET: Is there a way to set the "Exec" path in a .desktop file from an automake variable? I don't understand this question, sorry. It's possible both

Re: custom install rules

* Ralf Wildenhues wrote on Thu, Feb 08, 2007 at 12:53:29PM CET: > Almost. It should be > fooplug_LIBTOOLFLAGS = --tag=disable-static Erm. fooplug_la_LIBTOOLFLAGS.

Re: make portability issue

Hello Guillaume, * Guillaume Rousse wrote on Thu, Feb 08, 2007 at 10:44:35AM CET: > > I just found an issue in GNU make handling of empty variable in > substitutions: > A = foo > LIST = $(A) $(B) > LIST_H = $(LIST:=.h) > > all: > echo $(LIST_H) > > With GNU make 3.80, LIST_H is incorect

Re: custom install rules

* Christian Parpart wrote on Thu, Feb 08, 2007 at 10:45:13AM CET: > hm... okay, so assuming I've too DSOs in a directory, one shared library > (libfoo.so) and a plugin (fooplug.so), how would the rules then look like? > lib_LTLIBRARIES = libfoo.la > libfoo_la_SOURCES = libfoo.cpp > fooplugsdir =

make portability issue

Hello. I just found an issue in GNU make handling of empty variable in substitutions: A = foo LIST = $(A) $(B) LIST_H = $(LIST:=.h) all: echo $(LIST_H) With GNU make 3.80, LIST_H is incorectly expanded to "foo.h .h", whereas in make 3.81, this is correctly expanded to "foo.h" only. How t

Re: AM_LIBADD

>>> "RW" == Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Hello Akim, Hi Ralk, I missed your answer :) > * Akim Demaille wrote on Fri, Nov 03, 2006 at 05:56:16PM CET: >> >> For the records, I could use AM_LIBADD as a default value of >> libfoo_la_LIBADD. Currently it is not recognized.

Re: custom install rules

On Thursday 08 February 2007 09:29:13 Ralf Wildenhues wrote: > Hello Christian, > > * Christian Parpart wrote on Thu, Feb 08, 2007 at 07:18:18AM CET: > > I'd like to install some plugins, that usually do not need any .la or .a > > files to be installed (and even compiled). > > Use the `install-exec

Re: custom install rules

Hello Christian, * Christian Parpart wrote on Thu, Feb 08, 2007 at 07:18:18AM CET: > > I'd like to install some plugins, that usually do not need any .la or .a > files > to be installed (and even compiled). Use the `install-exec-local' target to extend Automake's install rules, don't override