Unresolved symbol errors after upgrading SDK
I have a C++ EMA project built with Visual Studio 2017 and the Elektron SDK v1.3.1 (Elektron-SDK-1.3.1.L1.win.rrg.zip) It builds and executes and has been in use for over a year. I recently tried to rebuild it using the latest SDK (Real-Time-SDK-2.0.1.L1.win.zip).
After changing the namespace from thompsonreuters:: to refinitv:: it compiles with no errors but the link step generates 148 unresolved symbol errors, all referenced by modules in emalib.lib. Most of the unresolved symbols begin with 'rssl' but there are some that begin with 'xml'. With v1.3.1 I was linking with three libraries: libema.lib, librssl.lib, and librsslVA.lilb. In the new SDK there is only one library, emalib.lib.Could I be missing a library?
NOTE: The project uses static linking and source file that references EMA classes and functions defines __EMA_STATIC_BUILD__
I don't remember where I read about them, but for V1.3.1 I defined two environment variables, EMAInstall and ElektronSDKInstallPath. Do those need to be updated or replaced?
Best Answer
-
It requires the following libraries.
C:\...\Cpp-C\Ema\Libs\WIN_64_VS141\Release_MD\libema.lib
C:\...\Cpp-C\Eta\Libs\WIN_64_VS141\Release_MD\librsslVA.lib
C:\...\Cpp-C\Eta\Libs\WIN_64_VS141\Release_MD\librssl.lib
C:\...\installdb\WIN_64_VS141\lib\libxml2_a.libReal-Time-SDK contains both EMA and ETA libraries. The librsslVA.lib and librssl.lib libraries should be in the Eta folder.
0
Answers
-
Thank you for pointing out that the librssl and librsslVA are in the ETA, not the EMA, folder. It was the same way in the old project as well so that was my bad. Thanks. Now it fails with just 3 unresolved symbol errors, as shown below. (ElekApiLib is the name of a project library.)
2>ElekApiLib.lib(rsslSocketTransportImpl.obj) : error LNK2001: unresolved external symbol GetTcpTable
2>ElekApiLib.lib(rsslSocketTransportImpl.obj) : error LNK2001: unresolved external symbol GetPerTcpConnectionEStats
2>ElekApiLib.lib(rsslSocketTransportImpl.obj) : error LNK2001: unresolved external symbol SetPerTcpConnectionEStats
Note that none these functions are called from with the ElekApiLib source code. I presume they are called from one of the SDK libraries. Any ideas?
0 -
I found these functions in the Windows IPHLPAPI.LIB. Now that I have added that library it builds. I will mark the first answer as the resolution.
0
Categories
- All Categories
- 6 AHS
- 37 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
- 367 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛