archive-org.com » ORG » M » MERPROJECT.ORG

Total: 820

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Revision history of "Platform SDK and SB2" - Mer Wiki
    prev 14 49 29 January 2013 Sage Talk contribs 1 typo cur prev 14 41 29 January 2013 Sage Talk contribs 54 Make your own target cur prev 10 10 24 January 2013 Lbt Talk contribs 157 update to latest Mer target names cur prev 15 47 18 January 2013 Vesku Talk contribs 2 N950 Nemo Mobile cur prev 17 18 26 December 2012 Shmerl Talk contribs 6 Setup target cur prev 17 17 26 December 2012 Shmerl Talk contribs 10 Setup target cur prev 17 17 26 December 2012 Shmerl Talk contribs 97 Install some tools cur prev 17 16 26 December 2012 Shmerl Talk contribs 0 Setup target cur prev 17 16 26 December 2012 Shmerl Talk contribs 149 Setup target cur prev 15 34 26 December 2012 Shmerl Talk contribs 5 Install some tools cur prev 15 33 26 December 2012 Shmerl Talk contribs 102 Install some tools cur prev 10 31 25 December 2012 Shmerl Talk contribs 98 Setup target cur prev 02 47 25 December 2012 Shmerl Talk contribs 98 Setup target cur prev 02 46 25 December 2012 Shmerl Talk contribs 1 Initialize scratchbox2 cur prev 02 44 25 December 2012 Shmerl Talk contribs 8 Plasma Active cur prev 02 44 25 December 2012 Shmerl Talk contribs 751 Plasma Active example update cur prev 02 17 25 December 2012 Shmerl Talk contribs 24 Nemo Vivaldi cur prev 14 44 15 November 2012 Bijjal Talk contribs 144 Target Setup Adding the workaround here cur prev 14 06 31 October 2012 Simonasl Talk contribs m 19 bumped current sb2 error output cur prev 14 43 24 October 2012 Lbt Talk contribs 389 user info needed in targets cur prev 03 24 23 October 2012 Sage Talk contribs 261 More info about replacing BUILD ID with the

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=Platform_SDK_and_SB2&action=history (2016-02-01)
    Open archived version from archive

  • Pages that link to "Platform SDK and SB2" - Mer Wiki
    Wiki talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Filters Hide transclusions Hide links Hide redirects The following pages link to Platform SDK and SB2 View previous 50 next 50 20 50 100 250 500 Main Page links Platform SDK links Platform SDK and SB2 links User Tswindell Qt Creator And Mer Integration links View previous 50 next 50 20 50 100

    Original URL path: https://wiki.merproject.org/wiki/Special:WhatLinksHere/Platform_SDK_and_SB2 (2016-02-01)
    Open archived version from archive

  • Changes related to "Platform SDK and SB2" - Mer Wiki
    last 50 100 250 500 changes in last 1 3 7 14 30 days Hide minor edits Show bots Hide anonymous users Hide logged in users Hide my edits Show new changes starting from 16 45 1 February 2016 Namespace all Main Talk User User talk Mer Wiki Mer Wiki talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Invert selection Associated namespace

    Original URL path: https://wiki.merproject.org/wiki/Special:RecentChangesLinked/Platform_SDK_and_SB2 (2016-02-01)
    Open archived version from archive

  • Platform SDK and SB2 - Mer Wiki
    building a package When SB2 is enabled on the OBS as it is in the MeeGo public OBS then it also creates a suitable SB2 target So checkout the package from OBS start a local build setup the SB2 target osc co PROJECT PACKAGE cd PROJECT PACKAGE determine which repository architecture to build for osc repos Then run a build osc build chroot only REPO ARCH Note the build root from the above command or use this to find it osc chroot Check the directory of the osc chroot and use the target directory in there for your SB2 target cd CHROOT target sb2 init L sysroot C sysroot c usr bin qemu arm dynamic m sdk build n N t TARGETNAME opt cross bin armv7hl meego linux gnueabi gcc If you like you could move this to srv mer targets before running the cd sb2 init commands but then osc build wouldn t upgrade it anymore At this point you can go to your src package git directory and run sb2 t TARGETNAME make The advantage of this approach over a full rootfs target are that it s smaller it uses the osc package cache so can be updated with smaller downloads it works with packages that are changing on the OBS so can be run against branched projects it s probably more suitable for working with other people and collaborating via the OBS the rootfs can be upgraded and packages added using osc especially the x option The disadvantages are it is currently more manual it only installs the development packages that are listed by the spec file as build dependencies it s not as re useable across multiple packages N950 Nemo Mobile Nemo N950 rootfs can be found at http releases nemomobile org snapshots choose the armv7hl n950 images To setup cross compiling for N950 armv7hl do the following inside the sdk chroot Setup target Extract the Nemo N950 rootfs as a target and set file permissions sudo mkdir p srv mer targets n950rootfs cd srv mer targets n950rootfs sudo tar xjvf path to nemo n950 image tar bz2 sudo chown R USER note if you re doing this as the root user and not with sudo remember to replace USER with your regular username Initialize scratchbox2 cd srv mer targets n950rootfs sb2 init L sysroot C sysroot c usr bin qemu arm dynamic m sdk build n N t nemo n950 opt cross bin armv7hl meego linux gnueabi gcc Note If you installed the mer target armv7hl target earlier that will be your default target If you however like the nemo n950 to be your default target add the d switch to the command line above Notes some messages about cannot find ld and no gcc are expected running sb2 init again with the same name will just change the values for that name make sure each target is named uniquely We now need to work around bug 238 note lack of leading echo n armv7hl

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=Platform_SDK_and_SB2&printable=yes (2016-02-01)
    Open archived version from archive

  • File:Changelog ambianced.png - Mer Wiki
    Nazanin Talk contribs Edit this file using an external application See the setup instructions for more information File usage The following page links to this file FAQ Metadata This file contains additional information probably added from the digital camera or scanner used to create or digitize it If the file has been modified from its original state some details may not fully reflect the modified file Image height 943 px

    Original URL path: https://wiki.merproject.org/wiki/File:Changelog_ambianced.png (2016-02-01)
    Open archived version from archive

  • File:Changelog ofono.png - Mer Wiki
    using an external application See the setup instructions for more information File usage The following page links to this file FAQ Metadata This file contains additional information probably added from the digital camera or scanner used to create or digitize it If the file has been modified from its original state some details may not fully reflect the modified file Image height 936 px Image width 717 px Width 936

    Original URL path: https://wiki.merproject.org/wiki/File:Changelog_ofono.png (2016-02-01)
    Open archived version from archive

  • Vendor/Release Structure - Mer Wiki
    from two sources Internal Jolla developers deploy via git and push the changes to webhook The changes will then go through Jolla s OBS to be built At this stage for all the commits with bug numbers there will be a comment from CI bot automatically put to the bug so the bug will be committed Therefore the bugzilla status will be resolved committed Jolla picks the needed changes from Mer developers who also push commits to Jolla webhook These will again go through OBS However there are no bug numbers for the commits made from Mer side Some of the bug references currently showing up in the changelog are internal bugs of public things which need to move to the open After changes from Autodoc and translation servers also go through build OBS submits a request for package testing Packages go through VM tests and finally if all pass image will be built Testing Level Continuing from the previous level all the accepted packages go to the testing level along with a submit request which includes fixes from both Jolla and Mer developers On Jolla side for the commits including a bug number CI bot will post a comment to the related bug and change the status of the bug to Resolved Fixed Everything will go through Jolla testing repository and ready for tests The QA here is partially done automatically If needed there will be some manual testing done on this image by testers Release Level Continuing from the previous level all accepted changes will go to the release level The process is the same as two other levels Changes from Mer and Jolla developers will go through Jolla release repository after the submit request is done and image will be ready for release testing In this stage for commits which contribute to bugs CI bot will post a comment and change the status to Resolved Released The QA team do mostly manual testing in this level to make sure image is ready to be released to public The bug life cycle in Jolla bugzilla during the release process Bugzilla Integration to CI Process After a new bug is filed and assigned to a developer he starts developing a fix for it on Git What he does is to add the bug number like JB number at the end of the commit for the commits he pushes This will help CI bot to trigger which commit contributes to which bug and then comments automatically to the bug whenever needed After developers deploys a fix for a bug they can do two things Either they manually put a PR link to the bug and ask fellow sailors to review it and then push the commit or if no review is needed the fix will be committed In both cases the fix will be committed and CI bot changes the status of the bug to Resolved Committed This happens in devel and the fix goes to be tested in devel

    Original URL path: https://wiki.merproject.org/wiki/Vendor/Release_Structure (2016-02-01)
    Open archived version from archive

  • FAQ - Mer Wiki
    want to install one the projects that use Mer as base since in those projects usually target is to provide a complete OS with UI and HW adaptation See Community Workspace for information about available user experiences and HW adaptations As explained in What does Mer mean for End Users Mer itself is not targeted for end users so installing it makes only sense if you are developing Mer or porting the core itself to a new platform What license s is Mer under Mer itself does not impose any particular license to the packages it is composed of The packages use various FOSS licenses such as GPL LGPL BSD and MIT For details you can query lisences on Mer based image with rpm qa queryformat NAME has license s LICENSE n Frequently Asked Questions for Vendors Vendor Jolla Frequently Asked Questions How does Jolla currently track work required for a release An Example Changelog from a closed sourced package An Example Changelog from an open sourced package Currently in Jolla OBS changelog the commits for non open source packages are followed by a bug number which the commit contributes to Take the attached picture as an example of changelog with bug numbers for the ambianced package On the device the changelogs are reachable via rpm q changelog package name However for changes coming from open source packages the commits do not follow any bug numbers Existing open packages include some on Mer side such as mer core mer tools hybris hal common stuff essentially HADK https github com mer hybris some on Sailfish open bits https github com sailfishos and nemo mw In Mer projects looking at the changelog only shows the commit messages without any bug numbers so nothing is traceable from Jolla side by bug numbers When releases are made it s important to be able to track the changes from bugzilla Internal developers need to provide the release manager at least one bug which addresses to the changes they ve made for the new update As also mentioned earlier in Jolla s porposal as one of Mer s vendors Jolla would like to ask the Mer package maintainers and the Mer community to please adopt a policy to require bug numbers in some commits to Mer packages to support vendor tracking of changes in Mer To have this tracking mechanism also on the open side developers can file a bug on Mer Bugzilla explaining the issue they have a fix for and then provide the bug number e g MER 12345 in the commit message they push to git This will benefit both sides as Mer can provide same kind of automation and tracking Jolla can cut down the manual effort required for tracking the changes in the open parts Jolla can move planning of open components to mer bugzilla How can providing a bug number reduce the manual work in tracking Before having the bug numbers for commits from the Mer community changes on the

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=FAQ&oldid=5345 (2016-02-01)
    Open archived version from archive