1 |
Compilation for Windows |
2 |
======================= |
3 |
|
4 |
This quick guide only covers compilation with Dev-C++ for now, which is a |
5 |
free (GPL) C++ integrated development environment for Windows. |
6 |
|
7 |
You can download Dev-C++ here: |
8 |
|
9 |
http://www.bloodshed.net/devcpp.html |
10 |
|
11 |
Make sure you install a version with Mingw integrated. |
12 |
|
13 |
First you need to install gtk and gtkmm. You can download them from the |
14 |
following URL: |
15 |
|
16 |
http://gladewin32.sourceforge.net |
17 |
http://ftp.gnome.org/pub/gnome/binaries/win32/gtkmm/2.10/ |
18 |
|
19 |
I recommend you to install them to the default destination (which is |
20 |
"C:\GTK"), that way you can probably avoid having to reconfigure the |
21 |
Dev-C++ project files later on. |
22 |
|
23 |
Download libsndfile DLL and header files: |
24 |
|
25 |
http://www.mega-nerd.com/libsndfile/ |
26 |
|
27 |
Extract the .zip file i.e. to "C:\". The libsndfile .dll file should then |
28 |
be i.e. under "C:\libsndfile-1_0_17". Beside the .dll file, make sure |
29 |
libsndfile's .lib file exists in that directory as well. If the .lib file |
30 |
does not exist yet, you have to create it with: |
31 |
|
32 |
dlltool --input-def libsndfile-1.def --output-lib libsndfile-1.lib |
33 |
|
34 |
Download and do the same steps for the libgig DLL and header files: |
35 |
|
36 |
http://download.linuxsampler.org/packages/win32/ |
37 |
|
38 |
a) Compile libgigedit.dll |
39 |
|
40 |
Open the project file "win32/libgigedit.dev" either directly in Dev-C++ or |
41 |
by double clicking on the project file in the Windows explorer. Then you |
42 |
have to ensure the settings of libgigedit's Dev-C++ project file are |
43 |
pointing to the correct location of your local copy of libsndfile, libgig, |
44 |
gtk and gtkmm (remember the recommendation from the beginng?). For that |
45 |
click in the Dev-C++ menu on "Project" -> "Project Options". Then click on |
46 |
the tab "Parameter" and make sure the paths of the .lib files of libsndfile |
47 |
and gigedit in the "Linker" list view are correct. Then click on the tab |
48 |
"Directories" and then on the tab "Library Directories" and check that the |
49 |
path to GTK's lib directory is corre. Then click on the tab |
50 |
"Include Directories" and make sure the paths to the header files of libgig, |
51 |
libsndfile, gtk and gtkmm point to the correct locations there as well. |
52 |
|
53 |
After that click on the "OK button and you should finally be able to compile |
54 |
"libgigedit" by clicking on "Compile" in the Dev-C++ menu. After compilation |
55 |
succeeded, you can find the "libgigedit.dll" file in the "win32" directory. |
56 |
|
57 |
b) Compile gigedit.exe |
58 |
|
59 |
To be able to succesfully compile this executable, you really have to |
60 |
compile the libgigedit.dll (that is the steps described in a) previously). |
61 |
Now open the project file "win32/gigedit.dev". Open the project options and |
62 |
check the library paths here as well, similar as described in a). After that |
63 |
you should be able to compile the executable by clicking on "Compile" in the |
64 |
Dev-C++ menu. After compilation succeeded, you can find the "gigedit.exe" |
65 |
file in the "win32" directory. |
66 |
|
67 |
Note: for being able to launch gigedit, you need to adjust your PATH |
68 |
environment variable, so it includes the library directories (the ones with |
69 |
the .dll files) of libgig, libsndfile, gtk and gtkmm. The previously |
70 |
compiled "libgigedit.dll" (don't confuse with "libgig.dll") should be in the |
71 |
same directory as "gigedit.exe", which of course is the default when you |
72 |
just run them from the "win32" directory. ;) |