Re: [mer-general] Platform SDK improvement brainstorming meeting Tueday 18 Sep
hi David; I'm not sure exactly what the problem you're trying to solve is but I'm pretty sure this is not the right approach in general. The SDK is a standalone environment which should have no links to the host binaries. Please revert that patch from your SDK setup and either log a bug with the problem you're encountering or come and discuss it on #mer so we can help find the correct approach. Sorry, my bad, I did not post link to related bug, here it goes: https://bugs.merproject.org/show_bug.cgi?id=567 PS. Though you are on Cc list in there ;) -- Aliaksei David On 13/09/12 07:40, Aliaksei Katovich wrote: hi; would it be possible to apply patch in attachment. The problem it fixes is related to 64-bit systems, where /lib32 and /lib64 dirs are present. Otherwise compilation of e.g. standalone kernel modules is not possible. -- Aliaksei Hi We'll be having a brainstorming meeting to get ideas on how to improve the platfrom SDK and it's usability. If you cannot attend the meeting and have some input, please send your thoughts by replying to this mail. Meeting will be held Tuesday 18 September from 9:00 to 10:00 UTC in #mer-meeting @freenode ps. in addtion to sharing thoughts we welcome helping hands to implement and test the improvements :) BR, Timo -- Don't worry, you'll be fine; I saw it work in a cartoon once...
Re: [mer-general] Platform SDK improvement brainstorming meeting Tueday 18 Sep
Hi David, Let me answer your questions. This URL https://img.merproject.org/images/sdk/ actually lies into my face. mer-sb2sdk-i486-chroot-latest.tar.bz2 is by far not the latest release at all. It was very confusing that I downloaded the latest image, then had to upgrade it... because it was not the latest. Please fix this. Actually that is the latest release - however, although I have been doing quite a bit of work on improving the SDK I've not actually had time to make another proper release. Not it's not the latest. If it were the latest, then no upgrades would be required. Some other thought: After I restart my machine, simply calling '/srv/mer/sdks/sdk/mer-sdk-chroot mount' doesn't work. I have to unmount it first. (Despite it saying that it's not mounted.) Thanks for the bug report. Ideally you should file this in https://bugs.merproject.org/ If you do that could you clarify doesn't work ... does it give any error message? No error messages at all, it just drops me into an empty, useless terminal. I wasn't sure whether this is a bug or a feature, thus I didn't file a bug report. Cheers, Timur
Re: [mer-general] Platform SDK improvement brainstorming meeting Tueday 18 Sep
hi;
would it be possible to apply patch in attachment. The problem it
fixes is related to 64-bit systems, where /lib32 and /lib64 dirs
are present.
Otherwise compilation of e.g. standalone kernel modules is not
possible.
--
Aliaksei
Hi
We'll be having a brainstorming meeting to get ideas on how to improve
the platfrom SDK and it's usability. If you cannot attend the meeting
and have some input, please send your thoughts by replying to this
mail.
Meeting will be held Tuesday 18 September from 9:00 to 10:00 UTC in
#mer-meeting @freenode
ps. in addtion to sharing thoughts we welcome helping hands to
implement and test the improvements :)
BR,
Timo
--- /srv/mer/sdks/sdk/mer-sdk-chroot.orig 2012-09-10 18:30:46.0
+0300
+++ /srv/mer/sdks/sdk/mer-sdk-chroot2012-09-10 18:32:50.0 +0300
@@ -181,6 +181,16 @@ prepare_mountpoints() {
mount --bind /var/lib/dbus ${sdkroot}/var/lib/dbus
mount --bind /var/run/dbus ${sdkroot}/var/run/dbus
+if [ -d /lib32 ]; then
+ mkdir -p ${sdkroot}/lib32
+ mount --bind /lib32 ${sdkroot}/lib32
+fi
+
+if [ -d /lib64 ]; then
+ mkdir -p ${sdkroot}/lib64
+ mount --bind /lib64 ${sdkroot}/lib64
+fi
+
if [[ $bind_mount_root == yes ]] ; then
echo Mounting / as /parentroot
mkdir -p ${sdkroot}/parentroot
Re: [mer-general] Platform SDK improvement brainstorming meeting Tueday 18 Sep
Hi 2012/9/13 Aliaksei Katovich aliaksei.katov...@gmail.com hi; would it be possible to apply patch in attachment. The problem it fixes is related to 64-bit systems, where /lib32 and /lib64 dirs are present. Otherwise compilation of e.g. standalone kernel modules is not possible. could you file a bug against the sdk and attach the proposed patch to it? https://bugs.merproject.org/enter_bug.cgi?product=Mer%20Integration%20Tools%20%28MINT%29 Thanks, Timo -- Aliaksei Hi We'll be having a brainstorming meeting to get ideas on how to improve the platfrom SDK and it's usability. If you cannot attend the meeting and have some input, please send your thoughts by replying to this mail. Meeting will be held Tuesday 18 September from 9:00 to 10:00 UTC in #mer-meeting @freenode ps. in addtion to sharing thoughts we welcome helping hands to implement and test the improvements :) BR, Timo
Re: [mer-general] Platform SDK improvement brainstorming meeting Tueday 18 Sep
I'm not sure exactly what the problem you're trying to solve is but I'm pretty sure this is not the right approach in general. The SDK is a standalone environment which should have no links to the host binaries. Please revert that patch from your SDK setup and either log a bug with the problem you're encountering or come and discuss it on #mer so we can help find the correct approach. David On 13/09/12 07:40, Aliaksei Katovich wrote: hi; would it be possible to apply patch in attachment. The problem it fixes is related to 64-bit systems, where /lib32 and /lib64 dirs are present. Otherwise compilation of e.g. standalone kernel modules is not possible. -- Aliaksei Hi We'll be having a brainstorming meeting to get ideas on how to improve the platfrom SDK and it's usability. If you cannot attend the meeting and have some input, please send your thoughts by replying to this mail. Meeting will be held Tuesday 18 September from 9:00 to 10:00 UTC in #mer-meeting @freenode ps. in addtion to sharing thoughts we welcome helping hands to implement and test the improvements :) BR, Timo -- Don't worry, you'll be fine; I saw it work in a cartoon once...
Re: [mer-general] Platform SDK improvement brainstorming meeting Tueday 18 Sep
On 12/09/12 11:35, Timo Härkönen wrote: Hi We'll be having a brainstorming meeting to get ideas on how to improve the platfrom SDK and it's usability. If you cannot attend the meeting and have some input, please send your thoughts by replying to this mail. Meeting will be held Tuesday 18 September from 9:00 to 10:00 UTC in #mer-meeting @freenode ps. in addtion to sharing thoughts we welcome helping hands to implement and test the improvements :) BR, Timo Some thoughts on the matter: 1. Documentation can be improved to explain more clearly how SDK is used with combination of Scratchbox2 and different targets. For example how it works with using various Mer core and target related repositories, and how updating them works (i.e. updating the core SDK vs the target part). Presenting it more clearly will benefit developers who aren't familiar with Mer infrastructure, and will help them to dive into using the SDK for their targets of interest. 2. Installation (including adding more targets) is rather manual, it can be more automated, even possibly with some optional UI which will propose potential SB2 targets and other settings. 3. Workflow of development for Mer and derivatives if somewhat obscure at the moment. Using purely manual method with make, cmake etc. is one way, but how it combines for example with something created in Qt Developer? Or should it combine? What paths various developers should take, some for example are using IDEs for development, others don't (or use them just for UI prototyping). Describing various approaches would be useful. 4. Would be good to provide a method how to run an application built for some target using Qemu and Xephyr (similar to how Harmattan SDK did it). Otherwise the only option is to build it for x86, but it defeats the purpose to make sure that other arch builds work (ARMv7hl, ARMv7l and so on). Providing a streamlined recipe at least to see that something works in the target arch build without a device will be a good option. Regards, Hillel.
Re: [mer-general] Platform SDK improvement brainstorming meeting Tueday 18 Sep
Fist thought: This URL https://img.merproject.org/images/sdk/ actually lies into my face. mer-sb2sdk-i486-chroot-latest.tar.bz2 is by far not the latest release at all. It was very confusing that I downloaded the latest image, then had to upgrade it... because it was not the latest. Please fix this. Some other thought: After I restart my machine, simply calling '/srv/mer/sdks/sdk/mer-sdk-chroot mount' doesn't work. I have to unmount it first. (Despite it saying that it's not mounted.) Cheers, Timur On Wed, Sep 12, 2012 at 5:35 PM, Timo Härkönen timop.harko...@gmail.comwrote: Hi We'll be having a brainstorming meeting to get ideas on how to improve the platfrom SDK and it's usability. If you cannot attend the meeting and have some input, please send your thoughts by replying to this mail. Meeting will be held Tuesday 18 September from 9:00 to 10:00 UTC in #mer-meeting @freenode ps. in addtion to sharing thoughts we welcome helping hands to implement and test the improvements :) BR, Timo
Re: [mer-general] Platform SDK improvement brainstorming meeting Tueday 18 Sep
+1 on both, but Timur perhaps the latter should be filed as a bug? :) -Sivan On Thu, Sep 13, 2012 at 12:34 AM, Timur Kristóf timur.kris...@gmail.com wrote: Fist thought: This URL https://img.merproject.org/images/sdk/ actually lies into my face. mer-sb2sdk-i486-chroot-latest.tar.bz2 is by far not the latest release at all. It was very confusing that I downloaded the latest image, then had to upgrade it... because it was not the latest. Please fix this. Some other thought: After I restart my machine, simply calling '/srv/mer/sdks/sdk/mer-sdk-chroot mount' doesn't work. I have to unmount it first. (Despite it saying that it's not mounted.) Cheers, Timur On Wed, Sep 12, 2012 at 5:35 PM, Timo Härkönen timop.harko...@gmail.com wrote: Hi We'll be having a brainstorming meeting to get ideas on how to improve the platfrom SDK and it's usability. If you cannot attend the meeting and have some input, please send your thoughts by replying to this mail. Meeting will be held Tuesday 18 September from 9:00 to 10:00 UTC in #mer-meeting @freenode ps. in addtion to sharing thoughts we welcome helping hands to implement and test the improvements :) BR, Timo -- -Sivan
Re: [mer-general] Platform SDK improvement brainstorming meeting Tueday 18 Sep
Hi 2012/9/13 Timur Kristóf timur.kris...@gmail.com Fist thought: This URL https://img.merproject.org/images/sdk/ actually lies into my face. mer-sb2sdk-i486-chroot-latest.tar.bz2 is by far not the latest release at all. It was very confusing that I downloaded the latest image, then had to upgrade it... because it was not the latest. Please fix this. Pondering if is this is a tar ball naming issue or a hic-up in releasing. In any case, one of the things that needs improving. Filing a bug about this but need to consult David about first. Some other thought: After I restart my machine, simply calling '/srv/mer/sdks/sdk/mer-sdk-chroot mount' doesn't work. I have to unmount it first. (Despite it saying that it's not mounted.) This is one of the things I personally want to see improved. I use a simple mount-enter-umount script to work around this. Added that tip to the wiki page [1]. Thanks, Timo [1] https://wiki.merproject.org/wiki/Platform_SDK#Entering_chroot Cheers, Timur On Wed, Sep 12, 2012 at 5:35 PM, Timo Härkönen timop.harko...@gmail.comwrote: Hi We'll be having a brainstorming meeting to get ideas on how to improve the platfrom SDK and it's usability. If you cannot attend the meeting and have some input, please send your thoughts by replying to this mail. Meeting will be held Tuesday 18 September from 9:00 to 10:00 UTC in #mer-meeting @freenode ps. in addtion to sharing thoughts we welcome helping hands to implement and test the improvements :) BR, Timo
