Re: [maemo-developers] Building maemo_af_desktop
On 4/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >If you build to a different prefix (/usr/local) and the apps install > >their stuff in another prefix (the usual /etc), is it really a > >surprise they are not found? > > > >In any case you need a predefined location for the .desktops (so that > >app-devs will know where to put them), so what would be the benefit to > >have it in gconf? > > Is that not the case that on debian based systems it is the communly > used aproach that prefix defaults to /usr and sysconfdir defaults to > /etc right? No it is not. Not on any debians I've tried at least. They do have --prefix /usr and --sysconfdir /etc in their standard debian package build rules of course, but that's hardly the same thing... Besides, it depends on the system (autotools) the configure script has been generated with, which is not neccessarily the same as the build system ;) -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi Interesting stuff at http://syslog.movial.fi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo_af_desktop
Hi, On 4/5/06, Aaron Levinson <[EMAIL PROTECTED]> wrote: In order to get an empty menu structure, all I did was use ./configure without any options. An examination of the source code demonstrates that it uses the OTHERS_MENU_CONF_DIR define for the default menu location on disk, and OTHERS_MENU_CONF_DIR gets defined as $(sysconfdir)/others-menu. When using ./configure without any options, $(sysconfdir) (along with other directory variables) starts at /usr/local, and the 770 file structure doesn't use /usr/local for anything. At run-time, because it cannot find the others-menu directory, no menu entries are displayed. Too bad the others-menu location is hardcoded this way. Seems like it might be appropriate to use gconf for this. I think you mean "Too bad the others-menu location is build-time configurable" as that's what it is...? If you build to a different prefix (/usr/local) and the apps install their stuff in another prefix (the usual /etc), is it really a surprise they are not found? In any case you need a predefined location for the .desktops (so that app-devs will know where to put them), so what would be the benefit to have it in gconf? Is that not the case that on debian based systems it is the communly used aproach that prefix defaults to /usr and sysconfdir defaults to /etc right? Which is different from the default of the autoconf as annoying as it can be. The lesson to learn is that "make install" is bad and only "fakeroot dpk-buildpackage -nc" should be used when developing debian like stuff. :-) pkgconfig here is a nice thing to have for the applications. The bigger problem is that the actual desktop entry paths are not according to the latest standard described in freedesktop.org menu specification... Br, Sampo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo_af_desktop
On 4/5/06, Aaron Levinson <[EMAIL PROTECTED]> wrote: > In order to get an empty menu structure, all I did was use ./configure > without any options. An examination of the source code demonstrates that > it uses the OTHERS_MENU_CONF_DIR define for the default menu location on > disk, and OTHERS_MENU_CONF_DIR gets defined as $(sysconfdir)/others-menu. > When using ./configure without any options, $(sysconfdir) (along with > other directory variables) starts at /usr/local, and the 770 file > structure doesn't use /usr/local for anything. At run-time, because it > cannot find the others-menu directory, no menu entries are displayed. > > Too bad the others-menu location is hardcoded this way. Seems like it > might be appropriate to use gconf for this. I think you mean "Too bad the others-menu location is build-time configurable" as that's what it is...? If you build to a different prefix (/usr/local) and the apps install their stuff in another prefix (the usual /etc), is it really a surprise they are not found? In any case you need a predefined location for the .desktops (so that app-devs will know where to put them), so what would be the benefit to have it in gconf? -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi Interesting stuff at http://syslog.movial.fi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Building maemo_af_desktop
Hi Karoliina, Responses below. Aaron On Wed, 5 Apr 2006 [EMAIL PROTECTED] wrote: > Hello, > > Actually you should build the maemo-af-desktop with dpkg-buildpackage: > > dpkg-buildpackage -rfakeroot > > It has been explained in my blog from last year or so: > http://www.karoliinasalminen.com/blog/?page_id=16 > > If you install the built debian package, the menu structure should work. > Can you explain in more detail what did you do in order for making empty > menu? In order to get an empty menu structure, all I did was use ./configure without any options. An examination of the source code demonstrates that it uses the OTHERS_MENU_CONF_DIR define for the default menu location on disk, and OTHERS_MENU_CONF_DIR gets defined as $(sysconfdir)/others-menu. When using ./configure without any options, $(sysconfdir) (along with other directory variables) starts at /usr/local, and the 770 file structure doesn't use /usr/local for anything. At run-time, because it cannot find the others-menu directory, no menu entries are displayed. Too bad the others-menu location is hardcoded this way. Seems like it might be appropriate to use gconf for this. Aaron ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Building maemo_af_desktop
Hello, Actually you should build the maemo-af-desktop with dpkg-buildpackage: dpkg-buildpackage -rfakeroot It has been explained in my blog from last year or so: http://www.karoliinasalminen.com/blog/?page_id=16 If you install the built debian package, the menu structure should work. Can you explain in more detail what did you do in order for making empty menu? Best Regards, Karoliina Salminen http://www.karoliinasalminen.com/blog >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of ext >Aaron Levinson >Subject: [maemo-developers] Building maemo_af_desktop > >I recently needed to rebuild maemo_af_desktop (version 1.72 >used with maemo 1.1). Invoking the configure script without >any arguments will result in a "functional" binary. >working binary: ./configure --prefix=/usr --sysconfdir=/etc . > ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
