Correction to Maemo 4.01 installation instruction
Hi, installation instructions at http://tablets-dev.nokia.com/4.0.1/INSTALL.txt seem to be updated to reflect few problems that are present at least in Ubuntu systems. There is one caveat though which should be clearly noted: 2.3 Known limitation of scratchbox states that e.g Ubuntu Hardy users should disable vdso and also lower the mmap_min_addr. The problem is that mmap_min_addr is only present in very recent kernels. If this is set in earlier kernels they simply die during boot. Ubuntu Hardy is ok with this but Gutsy gets nuked if you set this in the sysctl.conf. So, please add a warning or note that people just don't blindly set these in their sysctl.conf. And yeah, Ubuntu Hardy gets nuked too if you boot it using older kernel so this is _kernel_ specific and not distribution specific. -- Wellu ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Hi Just to let you know that I sometimes get this type of error : [2008-06-06 10:25:01] Processing package gnokii-gconf 0.6.2. Uploader: fredoll, builder: builder1 [2008-06-06 10:25:01] REJECTED: 'File size for /var/www/extras-devel/incoming-builder/chinook/gnokii-gconf_0.6.2.tar.gz does not match that specified in .dsc' It goes away if I retry the dput without changing anything ... Fred ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Having trouble installing the scratchbox development environment.
Oops, I thought your link led to http://maemovmware.garage.maemo.org/ - it's a preconfigured VMWare image that is ready to be used out of the box. Sorry for confusing. Been there, done that, have a working scratchbox. (Actually, two, because http://maemo-sdk.garage.maemo.org/install.html also worked for me, and seems a bit simpler to set up. It's not the official way though, and it's an early alpha version, so beware.) I believe using vmware image should be an official way for beginners - it's much, MUCH easier to install and use and does not need your system to be Ubuntu or any other debian - I use it on my wife's laptop with WinXP at home. -- Sincerely, Eugene ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: DSP SBC encoder task
Just a quick note to say that the DSP task encodes the test .au file correctly. Still a minor ;) issue that the DSP crashes after the DSP has finished the encoding task (I think this is probably due to a non-existent semaphore being written to, will have to test my theory tomorrow). snip in case of using GStreamer, you should provide a GStreamer element that allows you to offload the SBC encoding to the DSP. Currently we are using sbcenc which will do it for us. Atm we have to use ALSA to produce A2DP output, is the data sent thought here simply piped straight into sbcenc running standalone? I'd like to make sure that the people who currently use it (e.g. from mplayer) are also able to continue doing so using the DSP. Certainly a GStreamer wrapper is next on the list of ToDos after I stop the DSP from crashing ;). Cheers, Simon ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Hi Hi, Just to let you know that I sometimes get this type of error : [2008-06-06 10:25:01] Processing package gnokii-gconf 0.6.2. Uploader: fredoll, builder: builder1 [2008-06-06 10:25:01] REJECTED: 'File size for /var/www/extras-devel/incoming-builder/chinook/gnokii-gconf_0.6.2.tar.gz does not match that specified in .dsc' It goes away if I retry the dput without changing anything ... This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Fred -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Hello Maemo - CFSONID 2008
ext Kees Jongenburger wrote: The community itself is not organized in what can we do to achieve xyz. they and I expect zyx to be maemo.org. They might even think : if maemo.org behaves like xyz THEY would be doing the right thing. it is not exactly easy to currently do anything for maemo.org (rember the bus where you are not the driver?). Are we missing a strong community leader? There is something missing, but I think it is more a matter of common understanding. It would be silly from Nokia's side to push business reasons in the maemo project without considering a sustainable approach to the free software community needs. But it is not much more clever from the community side to push software freedom reasons without considering a sustainable approach to the business company needs. maemo is expected by some people to be 100% free, and this is a fair and challenging goal. maemo is also expected by some people to beat the competition so the coolest OSS developers decide to invest their time, skills and attention in this project - which is also a fair and challenging goal. In addition to this, Nokia expects to make a sustainable/profitable business around the maemo platform and compatible devices. It is perhaps just a coincidence that those betting on 100% of software freedom as a guarantee of commercial success are not the ones making the big investment hiring a team and shipping devices. It's always easier to say change your business when you have no money invested in it. So please, relax and try to understand also the other side. Nokia is betting more in open source today than yesterday, and tomorrow more than today. Glacial speed? Depends how you look at it. A lot has been done between the 770 launch 3 years ago and today, even in terms of open source strategy. Unsatisfied about the speed and/or about the lack of a 100% freedom software delivered by Nokia? You can provide the speed and full scope yourselves, asking Nokia to remove any obstacles in your way. In the meantime we will keep trying shipping software, development platform and devices exciting not only the open source community but many more people out there. In fact you also want us to do so. -- Quim Gil marketing manager, open source maemo software @ Nokia ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Having trouble installing the scratchbox development environment.
On Thu, Jun 05, 2008 at 07:25:09PM +, Hendrik Boom wrote: On Thu, 05 Jun 2008 21:56:58 +0300, Marius Gedminas wrote: On Thu, Jun 05, 2008 at 03:46:28PM +, Hendrik Boom wrote: I'm following the instructions in http://inz.fi/blog/2007/10/22/multi-target-development-for-maemo/ as advised by Graham Cobb, and have run into a snag. Been there, done that, have a working scratchbox. I seem to off track now. Things are not behaving as I expect from the instructions. Running the next commend in the list gives me: [EMAIL PROTECTED]:~$ sb-conf rs mistral-armel /scratchbox/packages/mistral-armel-rootstrap.tgz You dont have active target in scratchbox chroot. Please create one by running sb-menu before continuing sb-conf: No such target: mistral-armel sbrsh-conf: No current target It looks to me as if you skipped one step from that list. The command sb-conf st mistral-armel -c cs2005q3.2-glibc-arm \ -d debian-sarge:maemo3-tools:cputransp:doctools:perl:maemo3-debian \ -t qemu-arm-0.8.2-sb2 creates the mistral-armel target, and the next command sb-conf rs mistral-armel /scratchbox/packages/mistral-armel-rootstrap.tgz unpacks the rootstrap inside it. Then the last command sb-conf in mistral-armel -c -e -d -F does some extra configuration steps, but I've forgotten what those are (symlinking libc headers and tools like fakeroot into the appropriate places inside your target, IIRC). And sb-menu gives me a lot of choices without explaining what they mean. What, for example, is a target? Sort of like a chroot. A directory that contains all the tools needed for building packages for a particular Maemo version and CPU architecture. If 'mistral', 'bora', and 'chinook' are targets, isn't setting them up what these instructions I'm following are supposed to do? Yes. It looks as if things have changed since these instructions were written, or else that my installation has been derailed somehow and I should wipe it and start over, with a different debconf priority. Nah, forget debconf. You've got scratchbox installed -- check. You've got a scratchbox user -- check. Now you need to set up the targets for cross-compilation. If you screw up in a target, you can always nuke it with rm -r /scratchbox/users/$username/targets/$targetname* and start fresh with the sb-conf st/rs/in trio (or, to use longer command name aliases, sb-conf setup/rootstrap/install). I feel like I'minstalling slackware again, but without the handy few pages of paper telling me what's going on. Oh, yes. Some assembly required indeed. Is there documentation somewhere that could tell me what's going on behimnd the scenes? -- what all these commands do and need to do? Certainly! http://scratchbox.org/documentation/ By the way, if you run a recent distro with a recent kernel, you'll get other problems in the future. Errors like I'm running lenny with its up-to-date kernel. Thanks for warning me what's coming, Inconsistency detected by ld.so: rtld.c: 1192: dl_main: Assertion `(void *) ph-p_vaddr == _rtld_local._dl_sysinfo_dso' failed! are fixed by echo 0 | sudo tee /proc/sys/vm/vdso_enabled and mmap: Permission denied is fixed by echo 4096 | sudo tee /proc/sys/vm/mmap_min_addr Do these have to be reentered every time I reboot? Yes. If you don't want to do that, edit /etc/sysctl.conf and add vm.vdso_enabled = 0 vm.mmap_min_addr = 4096 in there, then those commands will be automatically executed on every reboot. HTH, Marius Gedminas -- Please note that I only check linux-utf8 on Tuesdays when they happen on a tenth of December, so please CC me with any replies. -- Juliusz Chroboczek signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Having trouble installing the scratchbox development environment.
On Thu, Jun 05, 2008 at 09:29:21PM +, Hendrik Boom wrote: On Thu, 05 Jun 2008 21:56:58 +0300, Marius Gedminas wrote: (Actually, two, because http://maemo-sdk.garage.maemo.org/install.html also worked for me, and seems a bit simpler to set up. It's not the official way though, and it's an early alpha version, so beware.) Had a look at http://maemo-sdk.garage.maemo.org/install.html, and found the following fateful lines: First, set up the following entry to your /etc/apt/sources.list file on your Debian host. This will add the maemo-sdk host build tools repository. If you have Ubuntu Gutsy 7.10 on your host, please, add the following line into /etc/apt/sources.list: deb http://maemo-sdk.garage.maemo.org/download/host ubuntu-gutsy free To install for Ubuntu Hardy 8.04, please, use the following URL: deb http://maemo-sdk.garage.maemo.org/download/host ubuntu-hardy free It seems to leave out the crucial line for a Debian host. After going to http://maemo-sdk.garage.maemo.org/download/host/dists I see three distros there: ubuntu-gutsy ubuntu-hardy experimental The install page also says This ALPHA-2.5 version of Maemo SDK+ has been tested on Ubuntu Gutsy and Hardy running on 32bit i386 architecture. It is recommended to use Ubunty Gutsy/Hardy Server but maemo SDK+ should work also with Debian unstable and testing. Is anyone from the maemo-sdk garage project reading this list? Anyway, they have their own list, and forums, and a bug tracker, so you may want to raise the question about Debian support there. Marius Gedminas -- I once asked an older coworker and Solaris guru what happened with the Unix-haters list. He told me that it stopped being quite so funny once Windows NT came along. -- the gnat at slashdot signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Hello Maemo - CFSONID 2008
Hi Quim, you said In addition to this, Nokia expects to make a sustainable/profitable business around the maemo platform and compatible devices. Exactly, so there is no other way to solve that problem not hurting developers but to enter into the Global Alliance on Free Software/ Open Source Free Software New Global Open Source Alliance by corporations, developers, IP protection international organizations, patent offices (USPTO, Europeannbsp; Patent Office ...), Free Software Foundation, Microsoft, TomTom, Apple and Linux giants as well as others to discuss nd find the solution to have both corporate's and developer's business protected and have developer's IPs protected anyway. Nokia's corporate business is not exactly the business of developers working for free to let Nokia make business and generate profit. Maemo is to much about poetry, philosophy and business strategies. I remember, when I asked for the first time, who stayed for maemo.org Nobody was able to say - it was Nokia. Today we have a new business model (subject to patent application or already patented). Corporations setting up Internet communities, to have free workers working on projects set up by the corportions. I joined another community of developers and some guys come from a business corporation, developing the same project/s and some get founding from other organizations too. It's not bad as long as everyone is fully aware of his/her role and knows business terms in advance, before joining in. Working for free is not bad idea for students. But working for free for businesses to make final market product is really special idea subject to urgent discussion. One questions should be answered. Do developers need Nokia to develop their open soruce free software or does Nokia need developers to develop maemo platform commercial product. Global Alliance on Open Source Software forum is open, you are free to read, post, join, comment, send your proposals Group email [EMAIL PROTECTED] phone (+48) 886 424 624 Darius Global Alliance on Open Source Software http://groups.google.com/group/globalalliance4u?hl=en --- On Fri, 6/6/08, Quim Gil lt;[EMAIL PROTECTED]gt; wrote: From: Quim Gil lt;[EMAIL PROTECTED]gt; Subject: Re: Hello Maemo - CFSONID 2008 To: ext Kees Jongenburger lt;[EMAIL PROTECTED]gt; Cc: ext Robert Schuster lt;[EMAIL PROTECTED]gt;, maemo-developers@maemo.org Date: Friday, 6 June, 2008, 1:01 PM ext Kees Jongenburger wrote: gt; The community itself is not organized in what can we do to achieve xyz. gt; they and I expect zyx to be maemo.org. They might even think : if gt; maemo.org behaves like xyz gt; THEY would be doing the right thing. it is not exactly easy to gt; currently do anything for maemo.org gt; (rember the bus where you are not the driver?). Are we missing a gt; strong community leader? There is something missing, but I think it is more a matter of common understanding. It would be silly from Nokia's side to push business reasons in the maemo project without considering a sustainable approach to the free software community needs. But it is not much more clever from the community side to push software freedom reasons without considering a sustainable approach to the business company needs. maemo is expected by some people to be 100% free, and this is a fair and challenging goal. maemo is also expected by some people to beat the competition so the coolest OSS developers decide to invest their time, skills and attention in this project - which is also a fair and challenging goal. In addition to this, Nokia expects to make a sustainable/profitable business around the maemo platform and compatible devices. It is perhaps just a coincidence that those betting on 100% of software freedom as a guarantee of commercial success are not the ones making the big investment hiring a team and shipping devices. It's always easier to say change your business when you have no money invested in it. So please, relax and try to understand also the other side. Nokia is betting more in open source today than yesterday, and tomorrow more than today. Glacial speed? Depends how you look at it. A lot has been done between the 770 launch 3 years ago and today, even in terms of open source strategy. Unsatisfied about the speed and/or about the lack of a 100% freedom software delivered by Nokia? You can provide the speed and full scope yourselves, asking Nokia to remove any obstacles in your way. In the meantime we will keep trying shipping software, development platform and devices exciting not only the open source community but many more people out there. In fact you also want us to do so. -- Quim Gil marketing manager, open source maemo software @ Nokia ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers Send instant messages to your online friends http://uk.messenger.yahoo.com
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 09:24 +0200, ext Fred wrote: Hi Just to let you know that I sometimes get this type of error : [2008-06-06 10:25:01] Processing package gnokii-gconf 0.6.2. Uploader: fredoll, builder: builder1 [2008-06-06 10:25:01] REJECTED: 'File size for /var/www/extras-devel/incoming-builder/chinook/gnokii-gconf_0.6.2.tar.gz does not match that specified in .dsc' It goes away if I retry the dput without changing anything ... Thank you for reporting this. My guess is that autobuilder tries to pick up your package when this tarball is still being uploaded. I'll investigate this. Thank you. --- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 11:54 +0200, ext Niels Breet wrote: Just to let you know that I sometimes get this type of error : [2008-06-06 10:25:01] Processing package gnokii-gconf 0.6.2. Uploader: fredoll, builder: builder1 [2008-06-06 10:25:01] REJECTED: 'File size for /var/www/extras-devel/incoming-builder/chinook/gnokii-gconf_0.6.2.tar.gz does not match that specified in .dsc' It goes away if I retry the dput without changing anything ... This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Yep. That's what I'm thinking of. What is the current value? BTW, In which order do you put files into autobuilder incoming queue in Maemo Extras Assistant? The best way to do it is to put all files, than .dsc and .changes --- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Problems with larger buttons in HButtonBox
I'm quite new to this, and while I've managed to navigate installation, basic application building and using Glade to produce interface xml, I've run into a hitch. I have a horizontal button box that requests a size of 150x150 for it's children, and the buttons themselves are set to expand (and to try it, even set a request of 150x150 for each button) which shows up fine in Glade, but when I run it in the emulator, each button area is the full 150 by 150 pixels, but the button appearance is that of three and a bit buttons stacked on top of each other like bricks. They expand to fill the 150 width, but not the height. Instead, they repeat to fill the height. If I throw one button into the vbox, it will expand to fill the whole space, but not when I put it into a hbuttonbox inside the vbox. have tried this from Glade's xml, and from direct coding, and it doesn't seem to work for me either way. Thoughts? Thanks. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 11:54 +0200, ext Niels Breet wrote: Just to let you know that I sometimes get this type of error : [2008-06-06 10:25:01] Processing package gnokii-gconf 0.6.2. Uploader: fredoll, builder: builder1 [2008-06-06 10:25:01] REJECTED: 'File size for /var/www/extras-devel/incoming-builder/chinook/gnokii-gconf_0.6.2.tar .gz does not match that specified in .dsc' It goes away if I retry the dput without changing anything ... This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Yep. That's what I'm thinking of. What is the current value? 180, so that is pretty low. As it must at least be the time between 2 queue runs? BTW, In which order do you put files into autobuilder incoming queue in Maemo Extras Assistant? The best way to do it is to put all files, than .dsc and .changes That is what I do already. --- Ed - Niels ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Problems with larger buttons in HButtonBox
On Fri, Jun 06, 2008 at 07:55:14AM -0400, James Ferris wrote: I'm quite new to this, and while I've managed to navigate installation, basic application building and using Glade to produce interface xml, I've run into a hitch. I have a horizontal button box that requests a size of 150x150 for it's children, and the buttons themselves are set to expand (and to try it, even set a request of 150x150 for each button) which shows up fine in Glade, but when I run it in the emulator, each button area is the full 150 by 150 pixels, but the button appearance is that of three and a bit buttons stacked on top of each other like bricks. They expand to fill the 150 width, but not the height. Instead, they repeat to fill the height. Screenshot? I've seen something like this on osso-xterm with the vertical toolbar. Large toolbar buttons were drawn stacked, because the theme assumes a fixed button height. If I throw one button into the vbox, it will expand to fill the whole space, but not when I put it into a hbuttonbox inside the vbox. have tried this from Glade's xml, and from direct coding, and it doesn't seem to work for me either way. Marius Gedminas -- This host is a black hole at HTTP wavelengths. GETs go in, and nothing comes out, not even Hawking radiation. -- Graaagh the Mighty on rec.games.roguelike.angband signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 13:56 +0200, ext Niels Breet wrote: This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Yep. That's what I'm thinking of. What is the current value? 180, so that is pretty low. As it must at least be the time between 2 queue runs? It's 3 minutes. Not that low, I'd say. Let's set it to 240. If it's still not enough then we can increase it even more. -- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 14:16 +0200, ext Fred wrote: I managed to get gnokii-gconf to auto-build !!! Thanks a lot Thank you for using autobuilder! Now trying with phonelink ... It stops during the initial phase of configure ... ... checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /scratchbox/tools/bin/install -c configure: error: cannot run /bin/sh ./config.sub make: *** [configure-stamp] Error 1 Any idea ? My guess is that config.sub in your package is symlink which points to nowhere. Try to replace it (and may be some other autotools-related files) with the actual file[s]. -- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: DSP SBC encoder task
Simon Atm we have to use ALSA to produce A2DP output, is the data sent thought here simply piped straight into sbcenc running standalone? the alsa plugin with most of the bluez logic is a shared object, so the alsa audio client is effectively transmitting directly to the headset. I'd like to make sure that the people who currently use it (e.g. from mplayer) are also able to continue doing so using the DSP. Certainly a GStreamer wrapper is next on the list of ToDos after I stop the DSP from crashing ;). unlike the alsa plugin, the gstreamer stuff breaks up the problem. There is one gstreamer component for encoding and a separate one for transmission. You wouldn't have to change the transmission part. -- Brad ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 13:56 +0200, ext Niels Breet wrote: This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Yep. That's what I'm thinking of. What is the current value? 180, so that is pretty low. As it must at least be the time between 2 queue runs? It's 3 minutes. Not that low, I'd say. Let's set it to 240. If it's still not enough then we can increase it even more. I have set this to 240 now, let's see if this is enough to solve the problem. -- Ed - Niels ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Looks like it works ... Can this pb be linked to the fact that I have a passphrase associated with my ssh key and that I may not answer the passphrase question as soon as it arises ? Fred Niels Breet a écrit : On Fri, 2008-06-06 at 13:56 +0200, ext Niels Breet wrote: This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Yep. That's what I'm thinking of. What is the current value? 180, so that is pretty low. As it must at least be the time between 2 queue runs? It's 3 minutes. Not that low, I'd say. Let's set it to 240. If it's still not enough then we can increase it even more. I have set this to 240 now, let's see if this is enough to solve the problem. -- Ed - Niels ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
I have replaced the links with the actual files and it worked ... Thanks a lot for your support Fred Ed Bartosh a écrit : On Fri, 2008-06-06 at 14:16 +0200, ext Fred wrote: I managed to get gnokii-gconf to auto-build !!! Thanks a lot Thank you for using autobuilder! Now trying with phonelink ... It stops during the initial phase of configure ... ... checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /scratchbox/tools/bin/install -c configure: error: cannot run /bin/sh ./config.sub make: *** [configure-stamp] Error 1 Any idea ? My guess is that config.sub in your package is symlink which points to nowhere. Try to replace it (and may be some other autotools-related files) with the actual file[s]. -- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Hi, I try to be able to generate my projects for OS2007 as well as 0S2008 (with a few lines in configure.ac) But with the auto-builder, I have to specify hildon dev packages in debian/control ... which breaks my setup for OS2007 What would you recommend to keep this possibility ? Fred ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo Bug Jar #7
Am Donnerstag, 5. Juni 2008 schrieb [EMAIL PROTECTED]: Frederic Crozat wrote: Remember that most people are not used to Nokia policy to embargo any date (even estimate) regarding software (or hardware) release. For simplicity's sake, I don't know when Diablo will be released. Quality first! Releasing shouldn't _only_ be a management decision. When the quality is as expected then the (scrum ?) team should hand over the responsibility to the management. They can then powerpoint the great event ;-) Personally I consider fix release dates as contra productive. Quality it the key to success. Cheers Krischan ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Friday 06 June 2008 14:31:21 Fred wrote: I try to be able to generate my projects for OS2007 as well as 0S2008 (with a few lines in configure.ac) But with the auto-builder, I have to specify hildon dev packages in debian/control ... which breaks my setup for OS2007 What would you recommend to keep this possibility ? What I do is to use MUD to prepare my packages. MUD has the capability to modify lines in debian/control and to do it differently for different SDKs (in fact, I added that capability when the autobuilder was created specifically for this problem!). It does mean that I end up creating different source packages for different SDKs, of course. Of course, for now the solution is easy: there is no autobuilder for OS2007 so just set up the line correctly for OS2008 and pity anyone who tries to use your source package to build an OS2007 version! Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Hello Maemo - CFSONID 2008
On Fri, 2008-06-06 at 11:44 +, ext Darius Jack wrote: Nokia's corporate business is not exactly the business of developers working for free to let Nokia make business and generate profit. You have been adviced some time ago to check what's the reality around you. Looks like you didn't do your homework ... -- Cheers, Igor --- Igor Stoppa Nokia Devices RD - Helsinki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Fred wrote: Hi, I try to be able to generate my projects for OS2007 as well as 0S2008 (with a few lines in configure.ac) But with the auto-builder, I have to specify hildon dev packages in debian/control ... which breaks my setup for OS2007 What would you recommend to keep this possibility ? Hello Fred, I know nothing about the syntax of debian/control, but I looked at how others have done it. In maemo-mappers debian/control I found out that it is possible to have or conditions, like this: Build-Depends: hildon-libs-dev | libhildon1-dev, hildon-fm-dev | libhildonfm2-dev Try this out. BR. Julius ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo Bug Jar #7
Am Freitag, 6. Juni 2008 schrieben Sie: Hi, Krischan Keitsch wrote: Quality first! Releasing shouldn't _only_ be a management decision. When the quality is as expected then the (scrum ?) team should hand over the responsibility to the management. They can then powerpoint the great event ;-) Personally I consider fix release dates as contra productive. Quality it the key to success. While I still think we've wandered miles off topic here, I have to depend good project management practices. Release dates help with decision making - features to keep, features to drop. I agree that quality is a must, of course, but it's not the only parameter - last minute feature additions affect quality, or insisting on doing every feature on a checklist that is established at the start of the planning process. A release date helps you ship a smaller number of high quiality components, rather than spending years getting a required quality level on an ever-expanding feature list. Cheers, Dave. PS. As I understand it, the question here is that some bugs are fixed in the platform, but the patches aren't made available straight away. Have I misunderstood the issue? Yes this is becomming offtopic ;-) I also agree what you mean. That is why I consider scrum as a perfect project development philosophy. Release often, get feedback, count on quality, comunicate, plan regularily and then release again :-) (I guess we could go on forever which agile development 'method' is best and why waterfall is so 2003 - but this is offtopic.) Cheers Krischan ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: DSP SBC encoder task
Simon I have been thinking more about this and I think another approach could be considered. It would be easier to plug your work into everything else if you wrote it up as a patch to the regular sbc.c so it transparently chooses the soft or dsp codec at runtime. It would work with the alsa plugin, gst, and eventually pulse without extra work. Marcel will have to weigh in if it's to be accepted upstream. In any case, we'd need an override. It could be done with an environment variable like SBC_CODEC with values eg soft, dsp, auto with auto the default if it's not set. This does step around gstreamer a little, but anyway, alsa and pulse don't have the greatest gstreamer integration to start with... Brad ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: DSP SBC encoder task
Hi Chaps, I have been thinking more about this and I think another approach could be considered. It would be easier to plug your work into everything else if you wrote it up as a patch to the regular sbc.c so it transparently chooses the soft or dsp codec at runtime. It would work with the alsa plugin, gst, and eventually pulse without extra work. Marcel will have to weigh in if it's to be accepted upstream. In any case, we'd need an override. It could be done with an environment variable like SBC_CODEC with values eg soft, dsp, auto with auto the default if it's not set. This does step around gstreamer a little, but anyway, alsa and pulse don't have the greatest gstreamer integration to start with... Yes, that sounds like a good idea. At the moment I'm effectively running all of sbcenc.c on the DSP, while I should just be doing sbc_encode() + whatever init and clean-up routines are needed to handle the DSP on the ARM and to pass it the stream format data. I've started looking at the Bluez code and it looks like it should be reasonably easy (he says!) to have just these bits running on the DSP (expect lots of questions still though). What do you mean by it stepping around GStreamer? From my quick look at the code, the same init/clean-up and sbc_encode() routines seem to be used for both GStreamer and the ALSA bits; what more does GStreamer need to know? Cheers, Simon ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: DSP SBC encoder task
Simon I only say stepping around gstreamer since the gst way would be to make one gst plugin for soft and one for dsp codec and let gst choose one when building a pipeline. ie, they're prepared for multiple implementations of a given codec. -- Brad ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: DSP SBC encoder task
I only say stepping around gstreamer since the gst way would be to make one gst plugin for soft and one for dsp codec and let gst choose one when building a pipeline. ie, they're prepared for multiple implementations of a given codec. Ah, ok, I'm with you now. Well as you said before, let's not worry to much about complying with that way of doing things hey :) Simon ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Hello Maemo - CFSONID 2008
Hey guys, Just wanted to let you know I have a list of points I'd like to address with the look feel, and interface dynamics coming on the way. I'll be travelling tomorrow and have a lot of work to finish before then so it may be a few days. But just wanted to let you know, and it's a good motivator when I tell people aloud what I need to do. :) All the best, Paul ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
