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".
  • Platform SDK Development - Mer Wiki
    things may change Platform SDK needs to be able to function without an OBS account or access to an OBS Offline compilation must be possible Clearly document the difference between platform SDK and application SDK separation of user home and sdk need short path from code build deploy boo minimal http server to SDK for built rpm repo serving Sources and packages COBS project Mer Tools Testing https build pub meego com project monitor project Mer 3ATools 3ATesting basic kickstart https build pub meego com project show project Mer 3ATools 3ATesting rootfs an mount script https img merproject org images the script s git version is hosted at https github com lbt sdk kickstarter configs SDK team meeting minutes 13 1 2012 http mer bfst de meetings mer meeting 2012 mer meeting 2012 01 13 18 02 html 28 1 2012 http mer bfst de meetings mer meeting 2012 mer meeting 2012 01 28 10 04 log html 24 2 2012 http mer bfst de meetings mer meeting 2012 mer meeting 2012 02 24 16 01 html 9 3 2012 http mer bfst de meetings mer meeting 2012 mer meeting 2012 03 09 10 01 html 16 3 2012 http

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

  • Platform SDK - Mer Wiki
    image Check https img merproject org images mer sdk for the name of the latest KickStart file and use it in the first command below for chroot version curl k o mer latest sdk rolling chroot ks https img merproject org images mer sdk mer latest sdk rolling chroot ks sudo mic create fs mer latest sdk rolling chroot ks o pkgmgr zypp arch i486 pack to mer latest sdk rolling chroot tar bz2 for VM version curl k o mer next sdk rolling vm ks https img merproject org images mer sdk mer next sdk rolling vm ks sudo mic create raw mer next sdk rolling vm ks o pkgmgr zypp arch i486 Please check bugzilla if you encounter problems extlinux issue https bugs merproject org show bug cgi id 576 Running osc This section needs to be improved Since your home directory has been linked into the SDK then osc commands should work as normal osc A API URL ls Where API URL can be https api merproject org Mer Community OBS https api ci merproject org Mer s continous integration OBS not for regular use or the API url for your own or your company s OBS Compiling with the SDK Mer and the SDK uses Scratchbox2 as a cross compile tool it can be installed into a minimal SDK by installing a cross build environment suitable for your project You should install one or more of the following SB2 patterns to get a suitable environment sudo zypper in t pattern Mer SB2 armv6l sudo zypper in t pattern Mer SB2 armv7l sudo zypper in t pattern Mer SB2 armv7hl sudo zypper in t pattern Mer SB2 armv7tnhl sudo zypper in t pattern Mer SB2 mipsel NOTE in case of facing not enough disk space left or similar the problem is most probably that the kernel on your host is too old To run Mer SDK you should be running kernel 2 6 37 or newer on your host These patterns provide sb2 configurations qemu gcc and binutils for your architecture Once the SDK is setup see the documentation on using the Platform SDK and SB2 Packaging The SDK includes tools needed to create rpm packages for Mer See https build merproject org package files package sdk kickstarter configs project mer tools 3Atesting Hosting repositories To make installing created packages easier you can host your own rpm repository with the SDK and install packages to your target device from there TODO SDK contents The platform SDK s rootfs has some useful packages preinstalled that are listed below If you re missing something you can use zypper to install the needed extra packages or if not available in the repositories compile them yourself osc and build mic spectacle vim Adding New Tools New tools can be installed using sudo zypper in package or sudo zypper in t pattern pattern The following patterns are available Mer SB2 armv6l Mer SB2 armv7l Mer SB2 armv7hl Mer SB2 mipsel Cross build

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

  • View source for Platform SDK - Mer Wiki
    sdk mer latest sdk rolling chroot ks sudo mic create fs mer latest sdk rolling chroot ks o pkgmgr zypp arch i486 pack to mer latest sdk rolling chroot tar bz2 for VM version curl k o mer next sdk rolling vm ks https img merproject org images mer sdk mer next sdk rolling vm ks sudo mic create raw mer next sdk rolling vm ks o pkgmgr zypp arch i486 Please check bugzilla if you encounter problems extlinux issue https bugs merproject org show bug cgi id 576 Running osc This section needs to be improved Since your home directory has been linked into the SDK then osc commands should work as normal osc A API URL ls Where API URL can be https api merproject org Mer Community OBS https api ci merproject org Mer s continous integration OBS not for regular use or the API url for your own or your company s OBS Compiling with the SDK Mer and the SDK uses Scratchbox2 as a cross compile tool it can be installed into a minimal SDK by installing a cross build environment suitable for your project You should install one or more of the following SB2 patterns to get a suitable environment sudo zypper in t pattern Mer SB2 armv6l sudo zypper in t pattern Mer SB2 armv7l sudo zypper in t pattern Mer SB2 armv7hl sudo zypper in t pattern Mer SB2 armv7tnhl sudo zypper in t pattern Mer SB2 mipsel NOTE in case of facing not enough disk space left or similar the problem is most probably that the kernel on your host is too old To run Mer SDK you should be running kernel 2 6 37 or newer on your host These patterns provide sb2 configurations qemu gcc and binutils for your architecture Once the SDK is setup see the documentation on using the Platform SDK and SB2 Packaging The SDK includes tools needed to create rpm packages for Mer See https build merproject org package files package sdk kickstarter configs project mer tools 3Atesting Hosting repositories To make installing created packages easier you can host your own rpm repository with the SDK and install packages to your target device from there TODO SDK contents The platform SDK s rootfs has some useful packages preinstalled that are listed below If you re missing something you can use zypper to install the needed extra packages or if not available in the repositories compile them yourself osc and build mic spectacle vim Adding New Tools New tools can be installed using sudo zypper in package or sudo zypper in t pattern pattern The following patterns are available Mer SB2 armv6l Mer SB2 armv7l Mer SB2 armv7hl Mer SB2 mipsel Cross build tools for various architectures Mer debug tools A range of low level debug tools Mer testing tools testrunner eat and qttas Mer python development all your slithery needs Mer ruby development to add sparkle Zypper search is useful to find available packages Upgrading

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

  • Revision history of "Platform SDK" - Mer Wiki
    2 987 Update to latest SDK tarballs remove meego references remove outdated warnings cur prev 00 38 25 December 2013 Merlin1991 Talk contribs m 3 Entering chroot fixed bash if ls was a leftover from last script version cur prev 18 02 7 December 2013 Merlin1991 Talk contribs m 3 Entering chroot prevent potential issues with spaced filenames cur prev 23 05 5 December 2013 Sledge Talk contribs 0 Packaging cur prev 23 21 12 November 2013 Sledge Talk contribs 58 WARNING cur prev 23 20 12 November 2013 Sledge Talk contribs m 2 tl dr cur prev 23 19 12 November 2013 Sledge Talk contribs m 10 Install on VirtualBox cur prev 23 19 12 November 2013 Sledge Talk contribs m 23 Mer platform SDK cur prev 23 17 12 November 2013 Sledge Talk contribs 158 Quick install using Virtual machine or install on a linux host cur prev 23 10 12 November 2013 Sledge Talk contribs m 2 Install on VirtualBox TYPOS cur prev 08 50 28 September 2013 Faenil Talk contribs 3 fix wrong profile cur prev 19 41 27 September 2013 Faenil Talk contribs 24 Building an image cur prev 17 29 10 August 2013 Mike7b4 Talk contribs 59 Quick install using Virtual machine or install on a linux host cur prev 17 24 10 August 2013 Mike7b4 Talk contribs 40 Quick install using Virtual machine or install on a linux host cur prev 17 14 10 August 2013 Mike7b4 Talk contribs 147 cur prev 16 40 1 August 2013 Sledge Talk contribs 306 big fat warning for tl dr cur prev 20 15 28 July 2013 Zmc Talk contribs 127 cur prev 07 52 24 July 2013 Jhamalai Talk contribs m 170 Add workaround note for sdk version cur prev 07 04 25 June 2013

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

  • Pages that link to "Platform SDK" - Mer Wiki
    The following pages link to Platform SDK View previous 50 next 50 20 50 100 250 500 Main Page links Building against Mer in Community OBS links Contribution in detail links Tools links Adaptation Guide Step by step links Spectacle links Nemo GettingStartedInFixingBugs links Nemo Creating Releases links Platform SDK and SB2 links Platform SDK Development links Zephyr links Getting Started links Osc Setup links User Tswindell Qt Creator And

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

  • Platform SDK - Mer Wiki
    the name of the latest KickStart file and use it in the first command below for chroot version curl k o mer latest sdk rolling chroot ks https img merproject org images mer sdk mer latest sdk rolling chroot ks sudo mic create fs mer latest sdk rolling chroot ks o pkgmgr zypp arch i486 pack to mer latest sdk rolling chroot tar bz2 for VM version curl k o mer next sdk rolling vm ks https img merproject org images mer sdk mer next sdk rolling vm ks sudo mic create raw mer next sdk rolling vm ks o pkgmgr zypp arch i486 Please check bugzilla if you encounter problems extlinux issue https bugs merproject org show bug cgi id 576 Running osc This section needs to be improved Since your home directory has been linked into the SDK then osc commands should work as normal osc A API URL ls Where API URL can be https api merproject org Mer Community OBS https api ci merproject org Mer s continous integration OBS not for regular use or the API url for your own or your company s OBS Compiling with the SDK Mer and the SDK uses Scratchbox2 as a cross compile tool it can be installed into a minimal SDK by installing a cross build environment suitable for your project You should install one or more of the following SB2 patterns to get a suitable environment sudo zypper in t pattern Mer SB2 armv6l sudo zypper in t pattern Mer SB2 armv7l sudo zypper in t pattern Mer SB2 armv7hl sudo zypper in t pattern Mer SB2 armv7tnhl sudo zypper in t pattern Mer SB2 mipsel NOTE in case of facing not enough disk space left or similar the problem is most probably that the kernel on your host is too old To run Mer SDK you should be running kernel 2 6 37 or newer on your host These patterns provide sb2 configurations qemu gcc and binutils for your architecture Once the SDK is setup see the documentation on using the Platform SDK and SB2 Packaging The SDK includes tools needed to create rpm packages for Mer See https build merproject org package files package sdk kickstarter configs project mer tools 3Atesting Hosting repositories To make installing created packages easier you can host your own rpm repository with the SDK and install packages to your target device from there TODO SDK contents The platform SDK s rootfs has some useful packages preinstalled that are listed below If you re missing something you can use zypper to install the needed extra packages or if not available in the repositories compile them yourself osc and build mic spectacle vim Adding New Tools New tools can be installed using sudo zypper in package or sudo zypper in t pattern pattern The following patterns are available Mer SB2 armv6l Mer SB2 armv7l Mer SB2 armv7hl Mer SB2 mipsel Cross build tools for various architectures Mer debug tools A range of

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

  • Platform SDK and SB2 - Mer Wiki
    where it creates a chroot within the SDK suitable for 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

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

  • View source for Platform SDK and SB2 - Mer Wiki
    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 https bugs merproject org show bug cgi id 238 bug 238 note lack of leading echo n armv7hl meego linux etc rpm platform Note that this may not affect all targets and will need an appropriate value

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