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
- :
- Flexlm api
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
Jul 06, 2020
04:34 AM
Flexlm api
lmgr_md.lib, libcrvs.lib ... not compile with VS2015.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 06, 2020
01:15 PM
@Stevens33 , can you confirm if you are fresh building the toolkit or was it built at a different system and you are trying to rebuild it/ run it using VS 2015?
If it was built earlier, then it would be worth confirming the VS used to build it in the first place or you can try a clean build as "nmake -f makefile clean all".
(If my response assists with your questions , then please click "ACCEPT AS SOLUTION" or 'Kudos' so that it help others.)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 07, 2020
02:26 AM
It am trying to rebuid it.
It was built earlier with VS 2018, and now I need to build it with VS 2015. There are errors such as "unknown symbol imp__sys_errlist" and many others. Which is normal because this function is deprecated. So, are there any new flexlm api lib that are safier and compile with VS 2015 and upper? And where can I find it?
It was built earlier with VS 2018, and now I need to build it with VS 2015. There are errors such as "unknown symbol imp__sys_errlist" and many others. Which is normal because this function is deprecated. So, are there any new flexlm api lib that are safier and compile with VS 2015 and upper? And where can I find it?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 07, 2020
04:27 AM
@Stevens33 , since these are windows symbols and deprecated , hence it would be needed to build it using same VS compiler or perform a clean build with command shared earlier.
(If my response assists with your questions , then please click "ACCEPT AS SOLUTION" or 'Kudos' so that it help others.)