The Jedi API Lib units can be used solely or just by including jwaWindows.pas.

1. Single units use:

If you want to use it solely you just have to set the compiler unit path to

  • \commond and
  • \win32API .

Thats all.

2. JwaWindows.pas and JwaVista.pas (also for the use with JWSCL)

There is also the possibility to use only one file that includes all other Jedi API headers.
It is called JwaWindows.pas and should not be included along the other unit files.

  1. uses SysUtils, JwaWindows, JwaVista;

Do not mix up the Jwa units like this:

  1. uses SysUtils, JwaWindows, JwaWinNT, JwaVista;

We also suggest that you compile the file at first and then use the binary dcu file instead of the source.
Because the source file will need a lot of time when recompiling.

Howto:
For this purpose there are packages in the jwapi\Packages folder for the different Delphi versions. If not just
use an older package version.

You can load the project group for your Delphi version and compile the different package types :

  1. static debug = for static linked functions and debugger information and no optimization
  2. static release = for static linked functions and optimization
  3. dynamic debug = for dynamic linked functions and debugger information and no optimization
  4. dynamic release = for dynamic linked functions and optimization

The project group contains all four package types and are predefined to save the output in different folders.

After successfull compilation copy the folder or point the compiler path to the directory of your choice e.g. <your absolute path>\jwapi\trunk\Packages\d7\bin\debug\dynamic . Now your Delphi will use the dcu files instead of the source files.
The packages contains JwaWindows AND jwaVista. Both units must be included in a uses clause. JwaWindows does not contain jwaVista!

The JEDI Windows Security Code Library uses the second choice (JwaWindows.pas and JwaVista.pas) only. See here how to setup JWSCL.

Send post as PDF to www.pdf24.org
convert this post to pdf.