Building C++ Elektron SDK on our Linux platform
Our case is most similar to https://github.com/Refinitiv/Elektron-SDK/issues/86 but there does not seem to be any final resolution there. The issue is that prebuilt libraries seem to come only in two flavors, as above issue name suggests "C++ SDK dependency: builds for non RHEL6_64_GCC444 or OL7_64_GCC482"
We initially attempted approach similar to above forum issue by creating symlinks so named ( LIN3_64_GCC485 ) pointing to RHEL6_64_GCC444 under a few places where cmake / build stumbled, like installdb ; Cpp-C/Eta/Libs and Cpp-C/Ema/Libs.
Having to create symlinks does not sound like a great solution but it got us over this initial hurdle and then we encountered below error related to Dacs;
[ 27%] Built target Provider_shared
make[2]: *** No rule to make target `Elektron-SDK-BinaryPack_dacs_LIBRARY-NOTFOUND', needed by `/home/auser/Elektron-SDK-1.3.0.L1.linux/setup/Elektron-SDK-1.3.0.L1.linux.rrg/Cpp-C/Eta/Executables/LIN3_64_GCC485/Optimized/authlock'.
Stop. make[1]: *** [Cpp-C/Eta/Applications/Examples/AuthLock/CMakeFiles/authlock.dir/all] Error 2
The root cause seems to be that for dacs and ansi Utils libraries cmake step computed target names that are LIBRARY-NOTFOUND.
So this is where my colleague and I stopped for now; I am reluctant to start changing cmake files for now as I feel this should just work.
If I examine CMakeCache.txt, for example, we see that include path for ansi and dacs looks good but for some reason library path is not computed correctly by cmake even though it exists as Libs/RHEL6_64_GCC444/Optimized/libdacs.a and we created symlink based Libs/LIN3_64_GCC485/Optimized/libdacs.a
What is the right way to approach both issues: (1) initial issue -- building on Linux/gcc but different from anticipated build targets and (2) specifics dacs Cmake LIBRARY_NOT_FOUND issue
Any suggestions?
Best Answer
-
Refer to answer on Github https://github.com/Refinitiv/Elektron-SDK/issues/107, install lsb_release can resolve the compile error.
0
Answers
-
Hello @vladimir.tkach
The issue relates to how build the SDK on unsupported platform. I strongly suggest you create a new issue on GitHub issue page to contact Development team directly.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 370 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛