[vidalia-users] vidalia-users Digest, Vol 17, Issue 4

[Matt Edman]

On Wed, Feb 25, 2009 at 07:51:45PM -0000, Matthew P. Saunier wrote:
> OK, I don't know why I didn't check this before, but the problem with
> float not working is that cmath is not present when compiling with
> MIPSPro. I've attached a patch that adds an ifdef and fixes the problem.

Thanks for the patch. Rather than doing some MIPSPro-specific #ifdefs, I
figured it might be better to add some CMake fu for checking whether cmath
is available when running cmake. If it isn't, we'll fall back to including
math.h instead.

I just committed this change to trunk in r3595. If you're building from
trunk, you should 'svn up' and then see if that fixed things for you as
well. Please let me know one way or the other.

> I still don't know why the main window never shows up, though. I know
> that it's not my Qt implementation (4.3.0) being broken - other Qt apps
> work fine. I've forced the tray-detection to always return true, but
> that doesn't work either. I'll need to get Visual Studio going on a
> Windows box to investigate further, though, since it's hard to do
> serious debugging with no tools other than nano. and I'm not really
> familiar with Qt. Hopefully I will be able to reproduce the bug and fix
> it quickly with a real IDE.

Do you have 'ShowMainWindowAtStart=false' in your ~/.vidalia/vidalia.conf.
That might be suppressing the main Vidalia window when it starts.

> Does anyone know if there is a prebaked Vidalia VS project that I could
> grab, instead of having to compile Qt, etc, etc? I can take care of the
> DLL dependencies with the binary Win32 package, I would think.

One of the advantages of CMake is that it can generate a project file for
a wide variety of IDEs, including several flavors of Visual Studio. The
CMake documentation lists the currently available generators:

  http://cmake.org/cmake/help/cmake2.6docs.html#section_Generators

I've been able to build Vidalia before using the "Visual Studio 9 2008"
generator, though usually I stick with "MinGW Makefiles" for simplicity.

--Matt