| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
| |
Make devtool happy patches
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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-3831
https://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>
|
