Re: [Openpilot-developers] Vista and microsoft.

[Tim B. <ti...@en...>]

On Sunday 28 March 2010 22:25:05 you wrote:
> Message body follows:
> 
> Hi.
> 
> I just downloaded openPilot release, but had problems
> compiling it with windows (microsoft visual studio 2008, Qt
> 4.6.2).
> 
> So I downloaded your snapshot, which contains a lot more,
> but also seems to have severe problems with windows. Can you
> please tell me if I am doing someting wrong, or is the code
> not really ported to windows ?
> 
> Which linux platform are you using for development ?
> 
> In case it is not ported to windows, I would like to
> volounteer for the job, since I would like to use it for
> route planning on my notebook.
> 
> looking forward to hear from you.
> rgds
> Jan Iversen
> 
> --
> This message has been sent to you, a registered SourceForge.net user,
> by another site user, through the SourceForge.net site.  This message
> has been delivered to your SourceForge.net mail alias.  You may reply
> to this message using the "Reply" feature of your email client, or
> using the messaging facility of SourceForge.net at:
> https://sourceforge.net/sendmessage.php?touser=2859889
> 

Jan,

OpenPilot hasn't recently been compiled on Windows. In the last few months, 
the map widget has been re-written extensively, so I make no guarantees! I did 
manage to compile the map widget under Windows using MinGW way back in 2009 
(2nd Quarter? who knows!). Most of the other code should be possible to port 
reasonably easily, if it doesn't just compile straight away (one of the 
advantages of using QT).

At present the map widget doesn't contain much for route planning (I just 
haven't got there yet!) and it is still in a bit of a state of flux as I finish 
the layout of the chart plotting system. This is moving towards renderers, 
datastores and data loaders, which is how the CM93/2 and point of interest 
handling is written. Hopefully this will make the dependencies more modular 
(eg. enable the user to remove the GDAL dependency without crippling all chart 
support as at present).

My thoughts so far on route planning were to use the map widget to provide 
locations (perhaps by mouse-click, or nearest object) to a separate widget 
which could then supply data to an autopilot or similar. This hopefully 
prevents the map widget from becoming too large (it's already pretty big), and 
hopefully allows us to re-use the lighter route planning/route control widget 
on lower-spec hardware than required for the full map widget.

At present I'm developing on Debian Squeeze under KDE4.2 with standard tools. 
If you'd like the job of porting the code then it's yours! I would suggest 
that you start porting the simpler widgets first, then work up to the widgets 
which have dependencies (notably AISDecoder--sqlite3 and the map widget - 
GDAL). I would not be surprised if you have trouble with GDAL, but you can use 
older versions if you don't want/need GRIB support.

Thanks for your interest,

Tim B.

-- 
OpenPilot - Open-source Marine Chart Plotter
Lead Developer
http://openpilot.engineering.selfip.org