SDK 9.2
 

Hi,

I am trying to setup SDK9.2 from full source.
So far I got:


They forgot to include the manuals !!!!

Having trouble with lmcrypt............

Does anyone have them ?
Programmers Guide would be a good start.




-------------------------------------------
For Cooking one needs ingredients.:rolleyes:

>>nmake /f lmutil.mak gives me ERROR

what kind of error did you get, what is your dev env (OS, tools, etc)

Hi,

System Windows 10 Pro 64-bit en
VS2005
VS2013
VS2019


After following the previous mentioned procedure lmcrypt.exe does not update my test lic files.

The option '/YX' error is a mistery as I could not find what this option does for nmake !!!

This is de link for the used SDK :

HTML Code:

---

https://mega.nz/file/xuZ03DrC#KZeq0EpbTijX7brlFWOdagKycKs0ATu1sN6Zxzz8wiI

---

Visual Studio 2005 Command Prompt_x86












-------------------------------------------
For Cooking one needs ingredients.:rolleyes:

Well, what happened at the end?

I looked at the CLR code of the program and I patched some bytes to bypass the lc_* calls.

It still asks for a license file/path but no checking is done any more after that.

very interesting what they are doing.
Until before version 11.4 of FlexLM, the process is the same as it exists in all the manuals.
In version 11.6 some things changed, I'm still studying.
I have questions:
1.- You found the seeds of your daemon vendor (mips)
did you follow the normal process to find it (is there a pdf file to do it)? If the answer is no, how did you do it?
2.- From your examples, I see that you know how to create the license depending on the BITS that the license uses.
But they all have SIGN=
There are some softwares that use SIGN2=
It would be nice if you tried

I will continue reading this post

Any update ?
 

@sendersu

Hi,

Any update ?

Hi @Gede
if you are asking about 1 year old quesiton on " Building lmutil.exe"
then it's obvious - one of your include paths has got spaces in it, so you have to enclose it into quotes

this one -

/I C:\Program Files (x86)\Microsoft Visual Studio\Common\MSDev98\INCLUDE

Tip
 

Hi@Sendersu

So easy to overlook.
Wil test it if I can find some time, to busy.


Any idea what this /YX option is for ?
Can not find any reference, no manual for this version.

VS2005 release 2005
VS2003 release 2003
VS6 release 1998

flexlm sdk v9.2 release 2003

so vs6 or VS2003 maybe have /YX

or maybe the developer bug =)
https://learn.microsoft.com/en-us/cpp/build/reference/y-precompiled-headers?view=msvc-170

some hint for you

/YX is very very old compiler switch
remove it and don't worry


---
/YX compiler option has been removed. Use /Yc (Create Precompiled Header File) or /Yu (Use Precompiled Header File) instead. If you remove /YX from your build configurations and replace it with nothing, it can result in faster builds.

Some compiler games
taget sys: W7, VS2019, your archive from mega


next steps:
- removed pdb
- src/lmgrdll.mak - removed /YX inside it
- h\pc.mak - removed /YX as well



ran nmake /f pc.mak again - no any issues observed