Without CVE_PRODUCT set to apache:thrift cve-check was catching
CVEs form facebook:thrift that are not related with this product.
Now the report is correct.
Signed-off-by: Davide Gardenal <davide.gardenal@huawei.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Changelog:
==========
- C++ library don't work with HTTP (csharp server, cpp client; need cross test enhancement)
- Swift service generator doesn't support oneway
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
License-Update: Added new sections for new files
Configuration changes:
- BUILD_EXAMPLES - does not exist anymore
- WITH_SHARED_LIB -> BUILD_SHARED_LIBS, WITH_STATIC_LIB are not to be
allowed together
- WITH_AS3=OFF - adobe action script 3 not available
Added new options (disabled by default):
- javascript, nodejs
Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This is the result of automated script (0.9.1) conversion:
oe-core/scripts/contrib/convert-overrides.py .
converting the metadata to use ":" as the override character instead of "_".
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
- QT4 support was dropped
- Feature for switching between boost and std pointer was dropped
- only std pointers are supported since version 0.13.0
Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Remove the python library feature as it was never installed so nobody should
miss it.
The CMake patches are no longer needed as most of the underlying issue
is fixed in OE core.
The other patches are backports that are already upstream in 0.11.
OpenSSL 1.1 is supported by this version of thrift.
Also add a feature to use boost smart pointers instead of C++ std ones.
This is enabled by default to keep backwards compatibility with the
0.9.3 recipe. However projects depending on thrift might still need to set
FORCE_BOOST_SMART_PTR within their build CMake project to make sure the correct
headers are selected.
Further the different libraries are now split into separate packages.
Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The newest Thrift version has currently no fix for building with gcc>=6.
Rather posting supporting patches.
Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The libraries can also be build for native and nativesdk.
This is useful for running tests on the build machine.
Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
- use release tarball instead of git
- move libevent, python and glib into PACKAGECONFIG
- add NOTICE file to copyright check
- split into multiple packages
- libthrift for libaries
- thrift-compiler for compiler
- thrift pulls in everything as before
Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Without this, thrift will try to use system java to build it's java
bindings, which is both unexpected and may fail depending on the
version of system java.
Signed-off-by: Cody P Schafer <dev@codyps.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
thrift build issues on gcc-6 were essentially 2 issues:
- gcc-6 has stricter overflow checking on array declaration, and
thrift was using `char` when it should have used `signed char`
- gcc-6 is really picky about it's include paths (`-I`), and thrift
had a bad habbit of passing internal ones when it was cross compiled
due to how it was using `include_directories()`
This adds 2 patches (both variations of those submitted upstream, the
ones included here are rebased onto thrift-0.9.3).
https://issues.apache.org/jira/browse/THRIFT-3831https://issues.apache.org/jira/browse/THRIFT-3828
Signed-off-by: Cody P Schafer <dev@codyps.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* Run tested cpp bindings with GNU Radio Control Port.
* The patch forcible removes Qt5 from configure. The disable is correct,
but doesn't prevent a cmake error looking for qmake during configure.
We do not need Qt5, so remove check. I suspect the issue might be in
Qt5 cmake files.
Signed-off-by: Philip Balister <philip@balister.org>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
