cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
alexdel
Pilgrim

Problem building FlexNet Publisher on Windows 7 x64 (evaluation product)

Hi,

I am trying to build the FlexNet Publisher Licensing Toolkit (11.14.1.1, evaluation product) for the first time on a Windows 7 x64 platform. The evaluation tutorials work fine.
I am following the Development Environment Guide. I have performed the following steps:

1. Download and extract the zip to my "C:\Program Files" folder. The zip contains a machind and a x64_n6 folder (among other folders).
2. Open VS2015 x64 command prompt (as administrator) and go the installation folder.
3. Launch the following command : "nmake -f makefile clean all".

A lot of LNK2001 and LNK2019 error are generated, here is a small excerpt from the console output:

        cl /c /nologo /c /I..\machind /I. /MTd  -I../h lmcode.c
lmcode.c
LINK /nologo /NODEFAULTLIB /OPT:NOREF /NXCOMPAT /DynamicBase /DEBUG /subsystem:CONSOLE lmnewgen.obj lmcode.obj libsimplifier.lib .\activation\lib\libnoact.lib lmgr_trl.lib libcrvs.lib libsb.lib libredir_std.lib oldnames.lib kernel32.lib user32.lib netapi32.lib gdi32.lib comdlg32.lib comctl32.lib wsock32.lib shell32.lib Rpcrt4.lib oleaut32.lib Ole32.lib Wbemuuid.lib wintrust.lib crypt
32.lib Ws2_32.lib iphlpapi.lib Psapi.lib advapi32.lib Shlwapi.lib dhcpcsvc.lib userenv.lib lmgr_dongle_stub.lib libcmtd.lib /out:lmnewgen.exe
lmnewgen.obj : error LNK2019: symbole externe non résolu remove référencé dans la fonction main
lmgr_trl.lib(flex_file.obj) : error LNK2001: symbole externe non résolu remove
lmnewgen.obj : error LNK2019: symbole externe non résolu rename référencé dans la fonction main
lmgr_trl.lib(flex_file.obj) : error LNK2001: symbole externe non résolu rename
lmnewgen.obj : error LNK2019: symbole externe non résolu fputs référencé dans la fonction main
lmgr_trl.lib(lm_rand3.obj) : error LNK2001: symbole externe non résolu fputs
lmgr_trl.lib(l_lfgets.obj) : error LNK2001: symbole externe non résolu fclose
lmgr_trl.lib(flex_file.obj) : error LNK2001: symbole externe non résolu fclose
lmgr_trl.lib(l_read_lfile.obj) : error LNK2001: symbole externe non résolu fclose
lmgr_trl.lib(cmn_vm_FakeVMDetection.obj) : error LNK2001: symbole externe non résolu fclose
lmnewgen.obj : error LNK2001: symbole externe non résolu fclose
lmgr_trl.lib(l_prikey.obj) : error LNK2001: symbole externe non résolu fclose
lmgr_trl.lib(lm_free_job.obj) : error LNK2001: symbole externe non résolu fclose
lmgr_trl.lib(lm_rand3.obj) : error LNK2001: symbole externe non résolu fclose
lmnewgen.obj : error LNK2019: symbole externe non résolu perror référencé dans la fonction main
lmgr_trl.lib(l_prikey.obj) : error LNK2001: symbole externe non résolu perror
lmgr_trl.lib(cmn_vm_FakeVMDetection.obj) : error LNK2001: symbole externe non résolu fopen
lmnewgen.obj : error LNK2001: symbole externe non résolu fopen
lmgr_trl.lib(l_prikey.obj) : error LNK2001: symbole externe non résolu fopen
lmgr_trl.lib(lm_rand3.obj) : error LNK2001: symbole externe non résolu fopen
lmgr_trl.lib(flex_file.obj) : error LNK2001: symbole externe non résolu fopen
lmgr_trl.lib(lm_chk_conf.obj) : error LNK2001: symbole externe non résolu sprintf


I tried to open and build the project from the Visual Studio interface, and I face similar issues. For example, I have noticed that the "lc_cryptstr" method is declared in lmclient.h but never defined anywhere. Therefore, I am wondering if I am lacking some source files.

Is there anything I am missing?

Thanks for any help,

Alexandre
Labels (1)
0 Kudos
2 Replies
ogarry
Flexera beginner

Re : Problem building FlexNet Publisher on Windows 7 x64

Hello,

I have the same error here. How did you solve it ?

Olivier
0 Kudos
Flexera Aparashar
Flexera

Try using a lower version of Visual Studio

Hi,

From the elease documents, i am not sure if VS 2015 is a supported compiler for FNP 11.14.1.1. Moreover in VS2010 - VS2012 - VS2015 there have been some fundamental changes (like location of header files and all..). So i would recommend using a supported VS compiler, for starter VS 2010 and check if build is fine.

Regards,
AP
0 Kudos