Compilation with Visual Studio 2008 (Windows):
- Download and install customized sipXtapi prerequisites - cppunit-1.12.0 if you plan to run unit tests (optional), DirectX SDK Nobember 2008 (required by port audio).
- Download customized sipXtapi source code from http://code.google.com/p/sipxtapi/ . Snaphosts are available from http://code.google.com/p/sipxtapi/downloads/list download section. If you plan to modify the GUI, you need to install sipXtapi into c:\work. Then sipXcallib will be in c:\work\sipxtapi\sipXcallLib. WxCommunicator requires customized sipXtapi, it won't compile with original sipXtapi from SIP foundry. SVN trunk wxCommunicator compiles against sipXtapi trunk.
- Open sipX-msvc9.sln. Make sure that in configuration manager Debug or Release configurations are selected for all projects. Debug-IPP must not be used if you don't have Intel IPP. Compile debug and release versions of sipXtapi.
- Download wxWidgets 2.8.9 or later from http://www.wxwidgets.org/downloads/ and install it into c:\work\wxWidgets or other directory. Compile the unicode debug and unicode release versions.
- If you plan to compile the setup, download and install Inno setup 5 from http://www.jrsoftware.org/isdl.php. Install it into c:\Program Files\Inno Setup 5\. This is for building wxCommunicator setup. Then checkout the setup source from http://wxcommunicator.svn.sourceforge.net/svnroot/wxcommunicator/branches/windows-setup. Copy files into c:\Program Files\Inno Setup 5\wxCommunicator. wxCommunicator.iss will be located in c:\Program Files\Inno Setup 5\wxCommunicator\wxCommunicator.iss. Now you can use wxCommunicator.iss to compile setup.exe if you want. You can also put it in a different directory, but then you must change the paths in wxCommunicator.iss .
- Download wxCommunicator source code. If you plan to modify GUI, copy wxCommunicator directory into c:\work so that all sources are in c:\work\wxCommunicator. This is currently needed due to dialogblocks GUI designer, if its not done, it damages the GUI as there is 1 custom widget (toggle bitmap button). If wxCommunicator is put into another directory, dialogblocks can't load custom widget (using relative path in dialogblocks doesn't work properly).
- Download and install dialogblocks 4 from http://www.anthemion.co.uk/dialogblocks/. Install the unicode version. Important! Before you open wxCommunicator project, run DialogBlocks, and in Tools->Edit Tools->Custom controls load C:\work\wxCommunicator\CustomControls.cst. Then close Dialogblocks and open c:\work\wxCommunicator\wxCommunicatorDB.pjd to edit the GUI. Whole user interface is saved in wxWidgets XRC file and loaded at runtime. Cpp files only need pointers to widgets to initialize them with data. The advantage of using dialogblocks is that user interface can be edited, new handlers added or removed without damaging existing code in cpp or h files.
- If you want to add new translation, download poEdit from http://www.poedit.net/ and copy locale\sk\wxcommunicator.po and locale\sk\resources.po (this one has dialog strings) to another directory and translate them. Use poedit to edit them (or plain text editor if you prefer it).
- Compile wxCommunicator. The solution will be in c:\work\wxCommunicator\build\msw. Compiled exe will be in c:\work\wxCommunicator\bin\Debug. Debugging version can be run from visual studio directly, Release version not, as it requires all resouces in the Release directory (it ignores the working directory set in Visual studio).
Compilation in Linux:
No description available.