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
- :
- Re: Common Vendor Daemon tecnology
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
‎Apr 18, 2008
12:35 PM
Common Vendor Daemon tecnology
Hi All
I´m need to configure common vendor daemon toolkit, but i didn´t understand still. cvdconfig show me that message::confused:
Error in file:cvdconfig.c at line:1634
Error in file:cvdconfig.c at line:1610
Error in file:cvdconfig.c at line:1515
Error in file:cvdconfig.c at line:137
Any help will be wellcome !
I´m need to configure common vendor daemon toolkit, but i didn´t understand still. cvdconfig show me that message::confused:
Error in file:cvdconfig.c at line:1634
Error in file:cvdconfig.c at line:1610
Error in file:cvdconfig.c at line:1515
Error in file:cvdconfig.c at line:137
Any help will be wellcome !
(13) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 18, 2008
05:16 PM
Could you post the cvdconfig configuration steps you've performed so far?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 21, 2008
11:50 AM
Well, I filled a file and named it as make.txt inside machind directory of FLEXnet SDK.
my file has these lines:
VENDOR=vendor_daemon
{
ALIAS=alias_name
CODEFILE=path_to_lm_code.h
LMSEEDS=path_to_lmseeds.h
LSVENDOR=path_to_LSVENDOR.c
}
my file has these lines:
VENDOR=vendor_daemon
{
ALIAS=alias_name
CODEFILE=path_to_lm_code.h
LMSEEDS=path_to_lmseeds.h
LSVENDOR=path_to_LSVENDOR.c
}
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 21, 2008
03:46 PM
And the CODEFILE, LMSEEDS, and LSVENDOR values are valid paths to the toolkit files? As in:
Followed by running cvdconfig /f config.txt?
VENDOR=child1
{
ALIAS=child1alias
CODEFILE="C:\ChildToolkit1\machind\lm_code.h"
LMSEEDS="C:\ChildToolkit1\i86_n3\lmseeds.h"
LSVENDOR="C:\ChildToolkit1\machind\lsvendor.c"
}
Followed by running cvdconfig /f config.txt?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 25, 2008
06:59 AM
Hi mate.
I didn´t had success, i am getting that four errors message.
Where i put the name of the comun vendor daemon ?
See my config.txt.
VENDOR=vendor
{
ALIAS=vendor1
CODEFILE="C:\ChildToolkit1\machind\lm_code.h"
LMSEEDS="C:\ChildToolkit1\i86_n3\lmseeds.h"
LSVENDOR="C:\ChildToolkit1\machind\lsvendor.c"
}
VENDOR=vendor
{
ALIAS=vendor2
CODEFILE="C:\ChildToolkit2\machind\lm_code.h"
LMSEEDS="C:\ChildToolkit2\i86_n3\lmseeds.h"
LSVENDOR="C:\ChildToolkit2\machind\lsvendor.c"
}
I didn´t had success, i am getting that four errors message.
Where i put the name of the comun vendor daemon ?
See my config.txt.
VENDOR=vendor
{
ALIAS=vendor1
CODEFILE="C:\ChildToolkit1\machind\lm_code.h"
LMSEEDS="C:\ChildToolkit1\i86_n3\lmseeds.h"
LSVENDOR="C:\ChildToolkit1\machind\lsvendor.c"
}
VENDOR=vendor
{
ALIAS=vendor2
CODEFILE="C:\ChildToolkit2\machind\lm_code.h"
LMSEEDS="C:\ChildToolkit2\i86_n3\lmseeds.h"
LSVENDOR="C:\ChildToolkit2\machind\lsvendor.c"
}
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 30, 2008
09:48 AM
Anyone can help me to config toolkit to common vendor daemon ?:o
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 30, 2008
10:58 AM
To begin, do you have two different vendor names that you want to combine into one? As described in the Programming and Reference Guide, you must choose one of the vendors to be the "primary" vendor, and the others are "secondary" vendors. I believe the configuration file should list only the secondary vendors.
Afterward, the output of cvdconfig should be modified headers files and a make file for building the combined toolkit.
In some versions, it might be necessary to fix up quotation marks around paths in the modified make file. In some cases the release notes also have version-specific information.
The help topic "Planning Your Common Vendor Daemon Configuration" has more details about these initial steps...
Afterward, the output of cvdconfig should be modified headers files and a make file for building the combined toolkit.
In some versions, it might be necessary to fix up quotation marks around paths in the modified make file. In some cases the release notes also have version-specific information.
The help topic "Planning Your Common Vendor Daemon Configuration" has more details about these initial steps...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 30, 2008
11:51 AM
Thanks for reply, Robert
Let me explain my situation, better.
I have two vendor names:
I have one vendor name ( vendor1 ) that is inside Flexnet v10.8 and other vendor name ( vendor2 ) that is inside FLEXlm v9.2. Now I need building one common vendor daemon with vendor1 and vendor2, i think that will be vendor3, for example.
I was wrong in my reasoning :confused:
Let me explain my situation, better.
I have two vendor names:
I have one vendor name ( vendor1 ) that is inside Flexnet v10.8 and other vendor name ( vendor2 ) that is inside FLEXlm v9.2. Now I need building one common vendor daemon with vendor1 and vendor2, i think that will be vendor3, for example.
I was wrong in my reasoning :confused:
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 30, 2008
12:17 PM
I believe you'll need to select one of your existing vendor toolkits to be the "primary" toolkit.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 30, 2008
04:15 PM
How I do select primary vendor to be the "primary" toolkit ?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 30, 2008
04:20 PM
The configuration file should contain only secondary vendor information. By running cvdconfig from the primary vendor's toolkit directory and then building the resulting make file, you have defined the primary vendor.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 02, 2008
08:10 AM
Ok.
I running config.exe and it genenerated lmcode.h, lmcrypt.c and makefile with .saved extension.
Now, to building common vendor daemon i need put the the name it inside lmcode.h or makefile ?
I running config.exe and it genenerated lmcode.h, lmcrypt.c and makefile with .saved extension.
Now, to building common vendor daemon i need put the the name it inside lmcode.h or makefile ?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 02, 2008
05:30 PM
Did you have the primary vendor name in the original makefile? What happens if you build using the new, generated make file?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 25, 2008
02:02 PM
RobertDickau wrote:
Did you have the primary vendor name in the original makefile? What happens if you build using the new, generated make file?
Yes, i have the primary vendor in the original makefile. But still i am getting error message !
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)