Hi Jan!

On 20.06.2008 17:20, Jan Kaláb wrote:
>
> Darshaka: I'll try to compile it with visual C++ after I finish
> with mingw.  But, this thread started a few months ago. Aren't
> your patches part of the official repository now?

You're completely right. Some (or even all) patches found their way
into the main repository. As far as I can remember it's not
necessary to patch the sources anymore to get a clean build.

So the most interesting part of my mini-howto are the notes on the
build environment which are nearly but not completely up-to-date.

So here's my addendum:

- Platform SDK. I've installed Platform SDK for Windows Server 2003
R2 (3790.2075). There are some problems with newer versions of
the SDK. If you really want to go through the troubles let us know
how you fixed them... ;)

- Visual Sudio C++ 2005 Express Edition. There is a SP1 available.
Don't install it.. if you still like to do so see my notes above.
;)

- Mercurial[1]. I've installed TortoiseHG v0.3 but any newer
version or even the commandline only version should be fine.

[1] http://tinyurl.com/2w9h75

- Qt. I've install v4.3.3 but found out that qutecom relies on
v4.2.x [2]. So if you intend to change some of the GUI elements
with the help of the QT-Designer use the old version of that. (You
can safely build against the new version.)

[2] http://article.gmane.org/gmane.comp.voip.qutecom.devel/94

- NSIS[4]. In order the run "nmake install" which builds the
installer you'll need NSIS. I've install v2.35 any newer version
should do fine but i'm not sure which version MDBSys is using...

[4] http://nsis.sourceforge.net/Main_Page

- VirtualBox. I still use v1.5.4. v1.6.0 had a ugly network problem
if you installed Windows as a guest-system but that should be
fixed in v1.6.1 or 1.6.2. When building qutecom you should give
your maschine at least 1GB of RAM to get a reasonable compile
speed.

- "This application has failed to start because the application
configuration is incorrect. Reinstalling the application may fix
the problem".

This error message occurs on some machines where qutecom is
deployed with the installer. I've found some notes in [3] but was
not able to solve it. I should start a new thread about this one but
thought it would be good to mention it here.

[3] http://www.codeproject.com/KB/cpp/vcredists_x86.aspx#IDE_Builds

I'll try to write a clean Howto into the new development wiki but
that will take some time...

Greetings,
 - Darsha



_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to