This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Publisher
- :
- FlexNet Publisher Forum
- :
- Visaul Studio error LNK2005 appears on linkage to 3rd-party library protected by FlexLM too.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 30, 2020
03:00 AM
Visaul Studio error LNK2005 appears on linkage to 3rd-party library protected by FlexLM too.
We have faced with the next problem:
Our application is protected by FlexLM and statically linked with it (separate 'license.lib' was created for that).
We use another 3rd-party library that uses FlexLM too (statically linked).
As a result, we get a lot of errors LNK2005 like:
SomeLib.lib(l_error.obj) : error LNK2005: lc_err_info already defined in lmgr_trl.lib(l_error.obj)
What can we do to resolve this issue? It seems that FlexLM functions names are defined in our and 3rd-party library.
(0) Replies
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)