Attendees: clsk, j_k9

As sent to the Mira Development Mailing List on 19/05/2010 with the subject: “Summary of 18/05/2010 bug fixing session”:

Hi all,

Last night, I invited Alan to connect to my Windows Vista Ultimate (32-bit) machine via Remote Desktop in order to diagnose the Side-by-Side configuration error I was experiencing when trying to run the Mira Client binary he provided. We spent a few hours working at it, but in the end he managed to fix the problem.

Alan discovered that the reason behind the error is that, although I have the Visual C++ 2008 Redistributable package installed, I did not have the VC++ debug run-time libraries (because I do not have the full VC++ 2008 application installed). Alan had not compiled the application in “Release mode”, and so it was attempting to call the debug libraries which I didn't have, hence the Side-by-Side configuration error. When he compiled it in Release mode, it worked without a problem, out-of-the box! (The pre-built binaries of the required libraries were included with the Mira Client binary.)

I then started testing it, for fun (I haven't run a Mira Client on Windows since the days when the UI was vegetative!). In doing so, I noticed that a Command Prompt is opened in the background when Mira Client is started. Alan says this is because the application is compiled as a Console application. He will try to figure out how to prevent the Command Prompt from opening, but it's not a huge priority.

Alan also suggested that we create a separate branch for the installer. I think this makes sense, as the installer seems to be a sub-project in itself; a wrapper around the main project. That would also allow us to redesign the installers, until we are happy with them, without affecting trunk. It also means that there wouldn't be any binary files (such as the executable installers) in trunk - these would be housed in the new installers branch. Does anyone have any objections to this?

Regards,

Max Bossino
Project Manager
http://miragroupware.org