Compiling OpenCPN - Error when trying to start

[X7JAY7X]

I compiled OpenCPN per the "Compiling for Windows" page on the Opencpn site. The compiled opencpn.exe will run fine on the computer I use to compile it. If I copy the exe to any other computer I get a error box (in win7) that says "The application has failed to start because its side-by-side configuration is incorrect". Am I compiling incorrectly?

[nohal]

Hi,
did you previously have OpenCPN installed and running on that other computer? If not, read http://www.cruisersforum.com/forums/...sta-62163.html - your problem looks like MSVC redistributable related.

Good luck

Pavel

[X7JAY7X]

I tried it on a win7 computer that previously had OpenCPN installed. I also tried it on a WinXP machine that did not have opencpn on it before. I am getting the same error in winxp but I belive it is just worded a bit different. It said there was a configuration error when I click on the opencpn.exe in winxp.

Thanks

[nohal]

Same stuff - MSVC redistributable related. Did you try to install vc_redist.exe manually?

Pavel

[X7JAY7X]

But why would it do this on a computer that previously had and official build of OpenCPN installed?

[nohal]

You are not specific about the version that was previously installed - if it was reasonably recent and worked and you are just replacing opencpn.exe you should definitely not see these errors - at least if you also compile against redistributable 2008sp1...
But as your info is not very exact, all I can suggest is the obvious, which we've learned during the time. Until now every time we've seen these errors, they were related to MSVC redistributable. Sometimes to insufficient user rights to install it properly, sometimes to antivirus software used. Always impossible to reproduce by any of the developers.

Pavel

[X7JAY7X]

I installed OpenCPN 2.4 beta v612. I compiled that same version. I first just replaced the OpenCPN.exe and I got this error. I then deleted the Official Build (as found in the v612 thread) and used my compiled installer and I still get this error.

[bdbcat]

X7.....

How about this: on a fresh compile of 612, in the VS2008 IDE, can you build and run the "opencpn" (Release or Debug) target from within the IDE? That is, do not build or run the "package" target....

This should use the dlls built-in to the VS2008 system.

Also, in "ControlPanel->Add/Remove Programs", what versions of VC runtime are installed? Before and after the opencpn installer.....

Thanks
Dave

[X7JAY7X]

How about this: on a fresh compile of 612, in the VS2008 IDE, can you build and run the "opencpn" (Release or Debug) target from within the IDE? That is, do not build or run the "package" target....

This should use the dlls built-in to the VS2008 system.

Yes i can run the debug and release targets.

Also, in "ControlPanel->Add/Remove Programs", what versions of VC runtime are installed? Before and after the opencpn installer.....

On my WinXp Machine I have VC Redist 2008 x86 9.0.30729.17. This was the first install of OpenCPN on this machine. There was no VC runtime on this machine before I used my compiled installer.

On my Win7 64bit machine I have VB Redist 2008 x86 9.0.30729.17, .4974, .6161, .5570. This machine had the official beta release of .612 on it before.

Thanks
Jason

[X7JAY7X]

I got it to run but now it is looking for "wxbase28_net_vc_custom.dll" instead of "wxbase28u_net_vc_custom.dll" that the installer installs. It errors on all the dll's because it is looking for dll's with the "u" in them.

[Netsurfer]

Originally Posted by X7JAY7X

It errors on all the dll's because it is looking for dll's with the "u" in them.

You have to use the Unicode version of the wxWidget library.

[X7JAY7X]

When I compile the package it packages the Unicode wxWidget library. I can see unicode dll's when I use this package to install on another computer. The opencpn.exe is still looking for the non-unicode wxwidgets and errors out because it cannot find them. How do I compile opencpn to use the unicode wxwidget dll's?

[nohal]

The easiest way is to remove the non-unicode wxwidgets dlls against which you compile. Another option is to run cmake-gui and modify the appropriate values (Check Advanced and scroll down to WX_* stuff, there's a lot of it). Of course make sure you actually have the unicode dlls - you should if you followed the build instructions. The dlls that are packaged to the installer are part of the git repository and are not used for compilation.

Pavel