yaml-cpp: tie recipe to git revision instead of dynamicly generated tarball
Since Github's auto-generated tarballs aren't garanteed to be identical over time it's better to tie the recipe to a git revision. closes #552 Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
This commit is contained in:
parent
c34a5e84a4
commit
dfeb9aa136
|
@ -8,11 +8,11 @@ DEPENDS = "boost"
|
|||
|
||||
PR = "r0"
|
||||
|
||||
S = "${WORKDIR}/yaml-cpp-release-${PV}"
|
||||
S = "${WORKDIR}/git"
|
||||
|
||||
SRC_URI = "git://github.com/jbeder/${PN}.git;branch=master;protocol=git"
|
||||
SRCREV = "b57efe94e7d445713c29f863adb8c23438eaa217"
|
||||
|
||||
SRC_URI = "https://github.com/jbeder/yaml-cpp/archive/release-${PV}.tar.gz"
|
||||
SRC_URI[md5sum] = "64200ca0bf5e0af065804d8d3e8f6d42"
|
||||
SRC_URI[sha256sum] = "ac50a27a201d16dc69a881b80ad39a7be66c4d755eda1f76c3a68781b922af8f"
|
||||
|
||||
EXTRA_OECMAKE = "-DBUILD_SHARED_LIBS=ON"
|
||||
|
||||
|
|
Loading…
Reference in New Issue