This page was inspired by a discussion on #meego (log@21:17) regarding MeeGo support of nonSSSE3 based hardware.
lbt added to the discussions with a timely blog post he had been working on http://mer-l-in.blogspot.com/2010/08/are-intel-subverting-meegocom.html.
mkdir mirror cd mirror wget -e robots=off --accept \*.rpm --mirror --no-parent --progress=dot --no-host-directories --cut-dirs=7 -nv http://mirrors.kernel.org/meego/releases/1.0/core/repos/source/
wget Meego-devel-tools-f11.repo sudo cp Meego-devel-tools-f11.repo /etc/yum.repos.d/ sudo yum --nogpgcheck install osc
edit /home/<user>/.oscrc to setup
apiurl = https://api.obs.maemo.org build-root = /home/fedora/tmp/build-root https://api.obs.maemo.org user = vgrade etc
Check that is working with
Setup a project
mkdir build-area cd build-area osc meta pkg -e home:<username> <package name> osc co home:<username>/<package name> cd home:<username> cd <package name> rpm2cpio *src.rpm|cpio -id osc addremove osc commit
cd home:vgrade cd uxlaunch
edit prjcfg on project (web tool) to remove ssse3 atom stuff
osc build MeeGo_1.0_Core - If this does not download the required packages then get them with- wget -e robots=off --accept \*.rpm --mirror --no-parent --progress=dot --no-host-directories --cut-dirs=7 -nv http://mirrors.kernel.org/meego/releases/1.0/core/repos/ia32/packages/i586/
So I can build a package without sssse3 and atom flags but how do I know that I don't have static libs built in which have code built with those flags? I suppose the order I build things in this way is important.
Add your #meego IRC nick below :-