1 -------------------------------
\r
3 -------------------------------
\r
5 This folder contains all the windows specific sources.
\r
6 You will also find two sets of files :
\r
7 - VisualC++6 workspace and project files, in order to compile JACK with MSVC
\r
8 - Code::Blocks (8.02) workspace and project files, in order to compile JACK with MingW
\r
10 The built binaries will be located in '/Release/bin' (or '/Debug/bin' if you build the Debug target). Once compiled, you'll find there everything you need :
\r
11 - the two 'libjackmp.dll' and 'libjackservermp.dll', client and server jack libraries
\r
12 - the 'jackdmp.exe', main application : the JACK server
\r
13 - the 'jack_xxx.exe' utilities and examples
\r
14 - in the jackmp directory, you'll find the driver's DLL's ('jack_portaudio.dll' and 'jack_netdriver.dll') and some tools ('netmanager.dll', 'audioadapter.dll', 'netadapter.dll' for example)
\r
16 In Code::Blocks all the projects are automatically built in a correct order (dll's then apps) by doing 'build->build workspace'.
\r
17 In VC6, you'll have to build the projects one by one.
\r
19 The needed regexp library TRE can be found here http://laurikari.net/tre/. Unzip and place the "tre-0.8.0" folder into the "windows" folder.
\r
20 Then edit and comment "#define snprintf sprintf_s" at the end off the "tre-0.8.0/win32/config.h" file before building the JACK project.
\r
22 -------------------------------
\r
23 Notes about VC and GCC versions
\r
24 -------------------------------
\r
26 The Visual Studio workspace is limited to VC6. JACK will not compile on most recent MSVC's. The fact is recent compilers (MSVC7, 8 or 9) don't agree with some of the JACK sources.
\r
27 But now you can compile JACK using GCC, with MingW.
\r
28 The project is actually organized in a Code::Blocks workspace. This is a simple and efficient way to compile the whole project.
\r
30 But for some reasons, you need to compile JACK using a SJLJ version of G++ (available on MingW website).
\r
31 Current GCC/G++ version (3.4.5) doesn't includes SJLJ so you'll have to use another one.
\r
32 JACK needs the use of SJLJ exceptions instead of DW2 because exceptions are exchanged between DLL's, and DW2 does not allow to throw an exception out of a DLL, so it wouldn't be cought.
\r
34 The ressources files has been created with ResEdit (ANSI build). VisualStudio uses 'ressource.rc' and 'ressource_vc.h'. The other files are used by MingW.
\r
36 You can make a small installer ('setup.exe') with CreateInstallFree, a little freeware. For this you have the little script 'jack.ci'.The installer contains everything jack needs to be intagreted in windows (including register entries and shortcuts).
\r
37 A binary version of qjackctl is also included.
\r
39 -------------------------------
\r
40 Running JACK on Windows
\r
41 -------------------------------
\r
43 You can use two drivers : PortAudio and NetDriver.
\r
44 The PortAudio backend allow the use of many soundcards, using ASIO, DirectSound or WMME drivers (any ASIO driver can be seen by PortAudio).
\r
45 The NetDriver allow you to use NetJack2 on windows. Thus you can easily exchange midi and audio streams bitween computers (Linux, MacOSX or Windows).
\r
46 In both cases, you have to use the minimalist :
\r
47 'jackd -R -d ...' command. With PortAudio, you can have a list of supported drivers with :
\r
48 'jackd -R -S -d portaudio -l'
\r
50 Other options still stay the same.
\r
51 You can also pick a binary of Qjackctl, but this is still in development.
\r
53 -------------------------------
\r
54 Running Jack on windows
\r
55 -------------------------------
\r
57 More information at : 'http://www.grame.fr/~letz/jackdmp.html'.
\r
59 For any question or suggestion, you can refer to the mailing list 'jack-devel@jackaudio.org'
\r
60 Enjoy JACK on windows... ;-)
\r