I've been battling with building gstreamer on my ubuntu 14.04 system.
I recently found out about the very promising-looking gst-uninstalled scripts as outlined here: http://arunraghavan.net/2014/07/quick-start-guide-to-gst-uninstalled-1-x/
Unfortunately I've run into a bit of a snag when the script attempts to build audioconvert:
https://gist.github.com/anonymous/2bedadba1c03c8223e5a
Looking at the actual gst-uninstalled script here: http://cgit.freedesktop.org/gstreamer/gstreamer/tree/scripts/gst-uninstalled
I see no switches for a "stable" version. Any suggestions?
__tim from #gstreamer pushed fix. Working.
Related
first time publishing there !
I first want to say that I'm a real noob to yocto, and I'm trying to add greengrass to my yocto project.
The issue is, my core layer is thud, but there aren't any meta-aws in thud, starting at zeus.
How I can I still go though and install my meta-aws on my yocto ?
Thx,
I found meta-aws available for thud here. Just git clone -b thud git#github.com:aws/meta-aws.git into your layers directory, then bitbake-layers add-layer /path/to/meta-aws, then you should be able to use their recipes.
After downloading updates it shows a error that can't install updates .
An error occurred while uninstalling
session context was:(profile=epp.package.cpp, phase=org.eclipse.equinox.internal.p2.engine.phases.Uninstall, operand=[R]org.eclipse.rcp.configuration_root.win32.win32.x86_64 1.0.0.v20130521-1847 --> null, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CleanupzipAction).
Backup of file D:\eclipse\eclipse.exe failed.
Can not remove : D:\eclipse\eclipse.exe
I'm running it under win7 and jdk1.7.0_21 64bit .
How fix it ?
Solution extracted from the forum linked in Anonymous answer:
Run eclipse
Rename eclipse exe to eclipse.exe.back
Run updates
Updates executed successfully
To match so guidelines:
Always quote the most relevant part of an important link, in case the target site is unreachable or goes permanently offline.
Refer this post: http://www.eclipse.org/forums/index.php/t/487240/. It helped in solving this problem for me.
Shown below for your convenience :
I had same issue with updating Kepler. W7 with admin.
How to solve:
Run eclipse Rename eclipse exe to eclipse.exe.back
Run updates
Updates executed successfully
Premysl Fiala
Create a new workspace. Eclipse Kepler does cause a problem if we work on the older workspace. Worked for me.
I'm learning to create meteor application on my windows machine now. Everything is working fine because http://win.meteor.com have windows installation that I can try with.
The problem I have is now I want to have routing capability in my app. From my research the Meteor-Router package can add by using meteorite. So here's what I've done
Install node.js for windows --> everything looks OK, I can type node -v to look at node version
Install meteorite by type npm install -g meteorite --> every working fine up until async module installation that complain about "c:\Microsoft.Cpp.Default.props" was not found
I've try googling to looking for the answer but have no luck.
Any idea for me to solve this problem?
According to meteorite's official documentation, Meteorite does not work in Windows as of time of writing this. Sorry.
... However, meteorite's git based approach runs counter to the MSI installation that's required to get it working. So meteorite does not work under windows right now. Pull Requests which change this would be gladly accepted!
I just downloaded the source code of facebook's scribe. I'm new to it and having read the readme.build file , I can say I could barely understand how to build it. Could anyone give me the step by step procedures? thanks... :)
All you need to do is follow the readme/build instructions that came with the package. If you don't have Linux installed in your PC, you can simply use a VM and install linux in it...
I wrote a detailed tutorial on how to build Scribe from the source on Linux (Fedora) here:
http://www.alphadevx.com/a/84-Installing-Facebook-Scribe-on-Fedora-8
It is pretty complex to install frankly, so hopefully the steps above will help you out.
http://code.google.com/r/hectorchu-go-windows/source/list
If you could compile it successfully, I like to know the procedures of how to.
Assuming you are using Hector's source tree:
Install MinGW and MSYS, along with MSYS Bison and any other tools you think you'll find useful (vim, etc).
Install ed from the GNUWin32 project.
Install Python and Mercurial.
Clone the [hectorchu-go-windows mercurial repository](https://hectorchu-go-windows.googlecode.com/hg/ hectorchu-go-windows) to C:\Go.
Run an MSYS shell (or rxvt). The rest of these are bash commands...
mkdir $HOME/bin
export PATH=$HOME/bin:$PATH
export GOROOT=C:\\Go
export GOARCH=386
export GOOS=mingw
cd /c/Go/src
./all.bash
Correct errors as it spits them out at you, repeat step 10 until it starts building.
It's the same idea as on Linux or MacOS, basically.
However, I still stand by what I said in my comment above: this isn't necessarily going to generate anything that actually works yet. You'd be better served by waiting until this effort has merged into the main Go tree before tackling it, unless your interest is in assisting with the porting effort.
Update: there is now a mostly-functional pre-built windows port available, for those not interested in building the compiler themselves. However, given the rate of change of the project, the lack of formal releases (other than the hg "release" tag), and the possibility of Hector's changes being merged into the main branch soon, keeping up with development via source builds is likely to produce better results over time.
Just FYI, there is seems official one now.
http://code.google.com/p/go-windows/
Hector said he was only able to get as far as being able to compile and run an empty main. See issue 107:
http://code.google.com/p/go/issues/detail?id=107
There is still a lot of work to do in porting that, especially since the code has lots of dependencies on ptrace and syscall, not to mention the different threading models between Linux/BSD and Windows.
Update:
There's a new thread on golang-nuts (started 26.03.2010) with a link to a recent build and some current building instructions (using MinGW+MSYS).