How to create the manager

Find and share HowTos to various installations / configurations!
4 posts • Page 1 of 1
Pradeep Kumar
Posts:39
Joined: Fri Dec 09, 2016 2:54 pm

How to create the manager

Post by Pradeep Kumar »

As per the read me document provided , we ran %API_ROOT%\\newWCCILManager.cmd in Visual Studio command prompt.
The template got created , and we tried to compile the template we have following issues,

Some of the files cannot open and cannot be found Ex: DpIdentifier.hxx,DpIdentification.hxx etc and few files.

How to resolve?

And can we create the Manager, similar to creation of ewo from scratch?

Gertjan van Schijndel
Posts:634
Joined: Mon Aug 02, 2010 10:37 am

Re: How to create the manager

Post by Gertjan van Schijndel »

Make sure the 'API_ROOT' environment variable has been set, run '%API_ROOT%\\checkAPIenv.cmd' to set the other environment variables and start visual studio with these environment variables.

Also a manager can be created from scratch, but it has more dependencies. Make sure that the following settings are used:
  • Include: $(API_INCL)
  • Force include: $(API_ROOT)/include/winnt/win32.h
  • Options: $(VC8_DEFS) $(D_PVSS_VER)
  • Dependencies: $(API_LIB)

Pradeep Kumar
Posts:39
Joined: Fri Dec 09, 2016 2:54 pm

Re: How to create the manager

Post by Pradeep Kumar »

I have set the environment variable

API_ROOT = till the path of api folder.

And then ran %API_ROOT%\\checkAPIenv.cmd in Visual Studio command prompt.

then ran %API_ROOT%\\newWCCILManager.cmd , i got the template of the manager and, it is a visual studio project.

It is not compiling, it says not able to find the header files.


And what is the below statements and how do we set

Include: $(API_INCL)

Force include: $(API_ROOT)/include/winnt/win32.h

Options: $(VC8_DEFS) $(D_PVSS_VER)

Dependencies: $(API_LIB)

Gertjan van Schijndel
Posts:634
Joined: Mon Aug 02, 2010 10:37 am

Re: How to create the manager

Post by Gertjan van Schijndel »

Start visual studio from the same command prompt as 'checkAPIenv.cmd' with the command 'devenv'. Or use a batch file.

When you open the visual studio solution/project normally (without starting it from the mentioned command prompt), then the required environment variables are not set (unless you have created them in the user or system environment) and your compiler will not be able to find the header files.

4 posts • Page 1 of 1