Exetools

Exetools (https://forum.exetools.com/index.php)
-   General Discussion (https://forum.exetools.com/forumdisplay.php?f=2)
-   -   Compile eror (https://forum.exetools.com/showthread.php?t=15089)

rcer 06-22-2013 08:31

Compile eror
 
I am trying to build lmcrypt on \i86_n3-11.9.1and am getting the following compile error.
I extensively googled this subject, but could not find any solution to this problem.

Any ideas or suggestions are welcome.


Setting environment for using Microsoft Visual Studio 2010 x86 tools.

c:\Program Files\Microsoft Visual Studio 10.0\VC>cd C:\Program Files\Flexlm\i86_
n3-11.9.1\i86_n3

C:\Program Files\Flexlm\i86_n3-11.9.1\i86_n3>build

C:\Program Files\Flexlm\i86_n3-11.9.1\i86_n3>echo off
***************************************************************************
Build.bat can be used in 3 ways *
build MT - This builds all of the files using the /MT compiler flag *
( Multi-threaded C Runtime as a static library ) *
build MD - This builds all of the files using the /MD compiler flag *
( Multi-threaded C Runtime as a DLL ) *
build DLL - This build all of the files to use the flexlm dll *
***************************************************************************

Building using the /MT flag

Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
Copyright (C) Microsoft Corporation. All rights reserved.

RC -r -fo scplmd.res scplmd.rc
Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385
Copyright (C) Microsoft Corporation. All rights reserved.

fatal error RC1109: error creating scplmd.res
NMAKE : fatal error U1077: '"c:\Program Files\Microsoft SDKs\Windows\v7.0A\bin\R
C.EXE"' : return code '0x1'
Stop.
C:\Program Files\Flexlm\i86_n3-11.9.1\i86_n3>

regards

rcer

Kerlingen 06-22-2013 15:17

Wild guess: You installed the source code in the "Program Files" directory which is by default read-only to all users expect admin, so the command line tools have no write rights and will fail instantly.

rcer 06-22-2013 19:26

Hi Kerlingen,

Your guess is right, but I have been running the command line as administrator, and I have checked that read & write access is O.K.

Anyway just to run a check I copied the SDK to the D drive, and I did get the same result.

From all the Googling I did, I understand that the problem is related to incorrectly set environment variables, but I haven't been able to figure out which variable(s) need to be set, and with what values?


regards

rcer

dirkmill 06-22-2013 22:00

hi rcer,

I don't have the 11.9.1 here atm but in my older makefiles (11.4) the only section using the resource compiler is
Code:

buildmsgfile
is that the same for you or do you see additional uses of
Code:

$(RC) -r -fo
?
what values are the variables
Code:

EVENTLOGMESSAGEFILE
EVENTLOGMESSAGEFILE2

set to ?

cheers,

dirkmill :B

dirkmill 06-22-2013 22:27

too late to edit my previous post :(

I just checked 11.9.1 i86_n3 out and initially got the same error message.
you basically have two options:
1. create a (potentially empty) resource file for your vendor daemon
2. edit the makefile to skip compiling and linking of the resource file for the vendor daemon

for option two just use the following as replacement of the daemon-section of your makefile:
Code:

daemon:        $(DAEMON)

$(DAEMON): $(XTRAOBJS) $(DAEMONLIBS) lsvendor.obj $(SRCDIR)\lsserver.h $(LMNEW_OBJ)
#          $(RC) -r -fo $(VENDORNAME).res $(VENDORNAME).rc
          $(LD) /subsystem:console /out:$(DAEMON) lsvendor.obj $(LMNEW_OBJ) \
#                  $(XTRAOBJS) $(DAEMONLIBS) $(CRT_LIB) $(XTRALIB1) $(DONGLELIB) $(ACTSTUB) $(VENDORNAME).res
                  $(XTRAOBJS) $(DAEMONLIBS) $(CRT_LIB) $(XTRALIB1) $(DONGLELIB) $(ACTSTUB)
                        $(EMBED_MANIFEST)

cheers,

dirkmill :B

Git 06-23-2013 05:16

Use the VC command shell (under Visual Studio Tools menu). It will set up it's paths for you. You can the CD to the flexlm directory.

Git

rcer 06-23-2013 15:20

Hi Dirkmill,

thanks for pointing me in the right direction, but when I change the makefile as per your suggestion, the compliler only builds the vendor daemon, and nothing else.

If I don't apply the change, I get the error message, and the compliler builds

lmcrypt.

regards

rcer

dirkmill 06-24-2013 02:53

hi rcer,
option "2" above only requires you to change two lines of your makefile, compilation of the whole kit works as before...
option "1" is even simpler, just create a zero-byte file called
Code:

$(VENDORNAME).rc
in your case this would be
Code:

scplmd.rc
cheers,
dirkmill :D

rcer 06-25-2013 18:21

Hi dirkmill,

Yes both options for building the kit are working fine.

Thanks & regards

rcer


All times are GMT +8. The time now is 23:13.

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2026, vBulletin Solutions, Inc.
Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX