You must setup JEDI API first before you can start with JWSCL! Otherwise if you set Delphi source path to include JwaWindows.pas you’ll get an error like:

Incompatible types: JwaWindows.XXX and JwaWinNT.XXX

JWSCL works with JwaWindows from the JEDI API. However this only works with some compiler directives defined in the packages in the package folder of JEDI API. Use these packages to compile and create a JwaWindows.dcu file.
ERROR: Adding the source path of JWA (folder Win32API) to your project options and then use JwaWindows and JWSCL does not work!

1. Adapt this source path to include some necessary files for JWSCL:

"path to JEDI API"\"version"\COM
e.g. C:\Projects\jwapi\2.3\COM

2. Make sure that you have added the path of JwaWindows.dcu to your project or general library path. After this step you can also add the source path to the JWSCL source folder (\source) to the project or general library path so all projects can easily use JWA and JWSCL.

3. Eventually you can start using JWA and JWSCL in the simplest way: Just add the units to your uses clause.

4. Consider to update your JEDI files using Subversion (with a Subversion client like TortoiseSVN). With TortoiseSVN you can just right click on the JEDI JWSCL folder and hit “SVN Update” (not Checkout or Import!). The code is then updated.

You are finished here or you can read on to get some more information:

Be aware that the order of including units may change Delphi’s behavior if an identifier with the same name is declared in several units.

1. JwaWindows instead of Borland’s Windows unit.
2. JwaVista for Vista enhancements. (This unit is no more available in newer versions than 2.2)

Some types in these JWA units are duplicate. JwaVista recreates and extends them to add Vista support. Example:
The new _TOKEN_INFORMATION_CLASS type from JwaVista.pas has several new additions:

However, if you add JwaVista and JwaWindows in this order into your uses clause you will only use the types from JwaVista. Some functions in JwaWindows or other libraries that use JWA won’t not know these types. To get the correct type you have to explicit adress the JwaWindows type.

JWSCL does not really need an order of its units.

Newer versions of JWSCL and JWA do no more support JwaVista.

Subversion

Sourceforge gives a short introduction how you can access the Subversion repository of the JEDI project.

The download packages (from Sourceforge) contain Subversion information so you can use your subversion tool to just update them. (Tortoisesvn: Right click the JWSCL folder and choose Subversion Update)

To get the latest release updates you can use this path with your Subversion client. Be aware that new versions (currently 0.9.3) can make this path obsolete (but still valid). The downloadable release packages are already provided with Subversion information so you can just update them to get the newest updates.
Click on the turtle to checkout the repository with TortoiseSVN.

https://jedi-apilib.svn.sourceforge.net/svnroot/jedi-apilib/jwscl/branches/0.9.3

There is also a development branch that contains new untested features. Use it with care:

https://jedi-apilib.svn.sourceforge.net/svnroot/jedi-apilib/jwscl/trunk

1. Single units use:
Single units are included into your project by adding the JEDI API source folder to your Delphi search path. Then you can use the units like

Be aware that some JEDI API examples use the single units approach. So if you want to compile them you have to add the folders to Delphi source path.
However, it is possible to use it in combination with the JwaWindows.dcu approach.

Add these folders to your Delphi source path (located in the JWA folder)

• \Common and
• \Win32API .
• \COM

Thats all.

We suggest to add these paths to your global source path of Delphi. To do so open the options dialog of Delphi (menu Tools -> Options) and navigate to the tab Library or Library Win32 (in newer Delphi).
There you add the three folders to the library path edit. Of course, you need to add absolute paths here like shown in example.

Example

So you saved the download “JEDI API 2.3 and JEDI WSCL 0.9.3.zip“  in this location

C:\Program Files\JEDI\

The zip file contains two projects located in folder jwa and jwscl. So you need to find the folders above by following the directory structure to :

C:\Program Files\JEDI\jwa\branches\2.3

In this folder you’ll find the folders Common, Win32API and COM that you need to add to your Delphi source path.
(You must not add qotation marks (“) since the space in Program Files is not a separator.)

2. JwaWindows.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.

Do not mix up the Jwa units like this:

It is possible to do so but in this way you will create duplicate and incompatible identifiers which will also collide with JWSCL.

We also suggest that you compile the file at first and then use the binary dcu file instead of the source directly. So you should add the location of JwaWindows.dcu to your Delphi source path to avoid rebuilding the file everytime you rebuild your project.

So again:
There are packages in the jwapi\Packages folder for the different Delphi versions. If not just use an older package version. That should suffice.

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 (recommended for using with JWSCL for debugging)
4. dynamic release = for dynamic linked functions and optimization (recommended for using with JWSCL in releases)

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

After a successful compilation, copy the folder or point the compiler path to the directory of your choice e.g. \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 (JwaVista is deprecated in future versions)) only. See here how to setup JWSCL. Furthermore it is recommended to use any of the dynamic linking packages for JWSCL.

Subversion

Sourceforge gives a short introduction how you can access the Subversion repository of the JEDI project.

The download packages (from Sourceforge) contain Subversion information so you can use your subversion tool to just update them. (Tortoisesvn: Right click the JWA folder and choose Subversion Update)

To get the latest release updates directly you can use this path with your Subversion client. Be aware that new versions (currently 2.2a) can make this path obsolete (but still valid). The downloadable release packages are already provided with Subversion information so you can just update them to get the newest updates.
Click on the turtle to checkout the repository with TortoiseSVN.

https://jedi-apilib.svn.sourceforge.net/svnroot/jedi-apilib/jwapi/branches/2.3

There is also a development branch that contains new untested features. Use it with care:

https://jedi-apilib.svn.sourceforge.net/svnroot/jedi-apilib/jwapi