| | 15 | == Building using the autotools == |
| | 16 | |
| | 17 | Using the autotools solution is the preferred way to build libpipi. It is complicated but you can trust us to maintain it properly. Building libpipi is then a 3-step operation: bootstrapping, configuring and building. |
| | 18 | |
| | 19 | {{{ |
| | 20 | ./bootstrap |
| | 21 | ./configure |
| | 22 | make |
| | 23 | }}} |
| | 24 | |
| | 25 | This will build [wiki:libpipi], [wiki:thepimp The Pimp] and a few example programs. |
| | 26 | |
| | 27 | == Developing using !MonoDevelop == |
| | 28 | |
| | 29 | [http://www.monodevelop.com/ MonoDevelop] is an IDE primarily targetting .NET. libpipi includes a !MonoDevelop solution because The Pimp makes use of its convenient interface builder, Stetic. |
| | 30 | |
| | 31 | The `libpipi.mds` solution contains the following projects: |
| | 32 | * `libpipi.mdp`, which builds libpipi using the autotools solution under the hood |
| | 33 | * `pipi-sharp.mdp`, the libpipi .NET bindings |
| | 34 | * `ThePimp.mdp` |
| | 35 | |
| | 36 | To build the libpipi examples or other programs, use the autotools solution. |
| | 37 | |
| | 38 | '''Note''': if you add new files or widgets to the !MonoDevelop solution, try not to forget to edit `ThePimp/Makefile.am` accordingly. |
| | 39 | |
| | 40 | == Developing using Visual Studio == |
| | 41 | |
| | 42 | A `libpipi.sln` Visual Studio solution is also provided, but not actively maintained. Its primary purpose is to debug libpipi and The Pimp on the Windows platform. |
| | 43 | |
| | 44 | == Developing using Cygwin == |
| | 45 | |
| | 46 | The [http://www.cygwin.com/ Cygwin] environment is not supported. Let us know about your experience. |
