Visit our Popular Forums

conachair · 09-03-2013, 04:47

Quote:

Originally Posted by cagney

I downloaded the 1.2 source code.
After commenting out lines 5 - 7 in FastComboEditor.cpp, the plugin did compile, with a few warnings.
The final plugin is listed as version 1.190.
No problem when activating or selecting "Preferences".

Using Kubuntu 12.10 on an amd 64.

Thomas

Hmm, still no joy here, was it these lines you commented out?

/* #ifdef __WXGTK__
#include <gtk/gtk.h>
#endif
*/

On 386 - 32 running debian 6.0.7

Thanks

cagney · 10-03-2013, 03:43

Yes, those are the lines.
I just tested on 32 bits Xubuntu 12.04.
Same thing. It compiled OK after commenting out the same lines.

What kind of errors do you get when compiling? I have a few unused variables and comparisons between signed and unsigned int's.

Also try to run OpenCPN with the ddd debugger to find out what happens.

Thomas

conachair · 10-03-2013, 11:44

Quote:

Originally Posted by cagney

Yes, those are the lines.
I just tested on 32 bits Xubuntu 12.04.
Same thing. It compiled OK after commenting out the same lines.

What kind of errors do you get when compiling? I have a few unused variables and comparisons between signed and unsigned int's.

Also try to run OpenCPN with the ddd debugger to find out what happens.

Thomas

Just compiled again and it seemed to raise no error messages this time.

OK, output from DDD with no log plugin.

Quote:

GNU DDD 3.3.12 (i486-pc-linux-gnu), by Dorothea Lütkehaus and Andreas Zeller.
Copyright © 1995-1999 Technische Universität Braunschweig, Germany.
Copyright © 1999-2001 Universität Passau, Germany.
Copyright © 2001 Universität des Saarlandes, Germany.
Copyright © 2001-2004 Free Software Foundation, Inc.
Reading symbols from /usr/local/bin/opencpn...done.
(gdb) run
[Thread debugging using libthread_db enabled]
[New Thread 0xb68dfb70 (LWP 3204)]
[Thread 0xb68dfb70 (LWP 3204) exited]
[New Thread 0xb68dfb70 (LWP 3212)]
[New Thread 0xb5b83b70 (LWP 3213)]

Error opening coefficient file
[Thread 0xb68dfb70 (LWP 3212) exited]
[Thread 0xb5b83b70 (LWP 3213) exited]

Program exited normally.
(gdb)

In addition to above after compiling logbook and clicking the icon....

Quote:

Program received signal SIGSEGV, Segmentation fault.
0xb7f24361 in operator+(wxString const&, wxString const&) () from /usr/lib/libwx_baseu-2.8.so.0
(gdb)

Ta

sbfreddie · 10-03-2013, 17:24

Hello:
While trying to build Logbook Konni on the Mac (OS X 10.7.5) with wxWidgets 2.9.4 (x86_64) I get the follow errors on build:

[ 45%] Building CXX object plugins/dashboard_pi/CMakeFiles/dashboard_pi.dir/src/speedometer.cpp.o
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/logbook_pi.cpp: In member function ‘void logbookkonni_pi::loadLayouts(wxWindow*)’:
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/logbook_pi.cpp:1086: error: ‘wxOPEN’ was not declared in this scope
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/logbook_pi.cpp: In member function ‘void logbookkonni_pi::loadLanguages(wxWindow*)’:
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/logbook_pi.cpp:1185: error: ‘wxOPEN’ was not declared in this scope
make[2]: *** [plugins/LogbookKonni_pi/CMakeFiles/logbookkonni_pi.dir/src/logbook_pi.cpp.o] Error 1
make[1]: *** [plugins/LogbookKonni_pi/CMakeFiles/logbookkonni_pi.dir/all] Error 2

Any ideas on how to fix this issue?l

Thanks,
Freddie

nohal · 10-03-2013, 17:41

Freddie...
Try to change wxOPEN to wxFD_OPEN on the offending lines.

Pavel

sbfreddie · 10-03-2013, 18:07

Quote:

Originally Posted by nohal

Freddie...
Try to change wxOPEN to wxFD_OPEN on the offending lines.

Pavel

Pavel:
Thanks for your quick reply. That change fixed that particular problem.
However here is another one:

Code:

[ 61%] Building CXX object plugins/dashboard_pi/CMakeFiles/dashboard_pi.dir/src/depth.cpp.o
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/Logbook.cpp: In member function ‘void Logbook::SetSentence(wxString&)’:
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/Logbook.cpp:180: error: call of overloaded ‘ParseTime(wxAnyStrPtr)’ is ambiguous
/usr/local/Cellar/wxmac/2.9.4.0/include/wx-2.9/wx/datetime.h:1250: note: candidates are: const char* wxDateTime::ParseTime(const char*)
/usr/local/Cellar/wxmac/2.9.4.0/include/wx-2.9/wx/datetime.h:1251: note:                 const wchar_t* wxDateTime::ParseTime(const wchar_t*)
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/Logbook.cpp:244: error: call of overloaded ‘ParseTime(wxAnyStrPtr)’ is ambiguous
/usr/local/Cellar/wxmac/2.9.4.0/include/wx-2.9/wx/datetime.h:1250: note: candidates are: const char* wxDateTime::ParseTime(const char*)
/usr/local/Cellar/wxmac/2.9.4.0/include/wx-2.9/wx/datetime.h:1251: note:                 const wchar_t* wxDateTime::ParseTime(const wchar_t*)
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/Logbook.cpp: In member function ‘void Logbook::getModifiedCellValue(int, int, int, int)’:
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/Logbook.cpp:1467: error: ambiguous overload for ‘operator+’ in ‘+wxString::c_str() const()’
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/Logbook.cpp:1467: note: candidates are: operator+(const wchar_t*) <built-in>
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/Logbook.cpp:1467: note:                 operator+(const char*) <built-in>
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/Logbook.cpp:1467: note:                 operator+(const unsigned char*) <built-in>
/Users/freddie/Desktop/OpenCPN3.1.1405EDS/plugins/LogbookKonni_pi/src/Logbook.cpp:1467: note:                 operator+(const void*) <built-in>
make[2]: *** [plugins/LogbookKonni_pi/CMakeFiles/logbookkonni_pi.dir/src/Logbook.cpp.o] Error 1
make[1]: *** [plugins/LogbookKonni_pi/CMakeFiles/logbookkonni_pi.dir/all] Error 2

Any Ideas?

Thanks,
Freddie

nohal · 11-03-2013, 20:57

Freddie...
I've terrorized one of my Linux machines to use wx2.9 and made OpenCPN 3.2 build and run there (easy). I also made the logbook to build (less easy). So far the good news. The bad news are that it crashes doing almost anything and I will have to look deeper into the plugin code and changes in wx2.9 to fix it, which will take some time... Let's have a look at the other plugins first - they very likely will be way less problematic, so we can get some usable results faster.

Pavel

sbfreddie · 12-03-2013, 11:11

Quote:

Originally Posted by nohal

Freddie...
I've terrorized one of my Linux machines to use wx2.9 and made OpenCPN 3.2 build and run there (easy). I also made the logbook to build (less easy). So far the good news. The bad news are that it crashes doing almost anything and I will have to look deeper into the plugin code and changes in wx2.9 to fix it, which will take some time... Let's have a look at the other plugins first - they very likely will be way less problematic, so we can get some usable results faster.

Pavel

Pavel:
Which plugin would you prefer to work on first?

Thanks,
Freddie

nohal · 12-03-2013, 11:42

Freddie...
I would go with https://github.com/SethDart/vdr_pi - it's the most useful one for further testing and development and should be easy. Then probably https://github.com/SaltyPaws/SAR_pi

Pavel

cagney · 13-03-2013, 10:16

Quote:

Originally Posted by conachair

Just compiled again and it seemed to raise no error messages this time.

OK, output from DDD with no log plugin.

In addition to above after compiling logbook and clicking the icon....

Ta

You need to do one more thing in ddd once you have seen the crash (segfault). Click "Status", in the menu bar at the top of the window, and then "Backtrace". A new dialog, backtracing the code that lead to the crash, pops up. Enlarge as necessary and take a screen shot, and post it here. Make sure the backtrace goes so far back so some OpenCPN code is referred to, not just external code.

No guarantee that I can help you further than this, but at least it will actually give a programmer a hint about what's up.

Thomas

HEME · 20-03-2013, 10:01

Hi there
Thank you for the logbook. It is a very nice instrument. I am just wondering: When I press ctrl & space, I am making a MOB mark and this can be seen in the map, but a restart af CPN removes the mark and therefore I looked in the Log to find the coordinates there, but there was no incident here. Is it a miss, or am I doing something wrong?

brg
Henning

cagney · 20-03-2013, 10:38

Quote:

Originally Posted by HEME

Hi there
Thank you for the logbook. It is a very nice instrument. I am just wondering: When I press ctrl & space, I am making a MOB mark and this can be seen in the map, but a restart af CPN removes the mark and therefore I looked in the Log to find the coordinates there, but there was no incident here. Is it a miss, or am I doing something wrong?

brg
Henning

An active MOB mark must be persistent on exit. It should be treated as other navobjects, so it's available on restart. This is a bug in OpenCPN, and I have entered it in the bugtracker. Thanks for pointing out the problem.
It should be entered in the log as well.....

Thomas

Icnoships · 20-03-2013, 17:59

Hi Pavel.... Apple for your table ...couple of screen shots of WMM plugin running on OS 10.7.5 with wxwidgets 2.9.4_dev, macports, an compiled in 64 bit mode targeting 10.7 SDK.
It build cleanly enough but cant test beyond that as i am still grappling with why the plugin folder is not being pulled into the final bundle ( i pasted um in )

but hey it did build, its a start
A shot of the screen & a shot of O's log that may be of use

regards mo

nohal · 20-03-2013, 18:35

mo...
Perfect. I can't see any functional problem in the screen shot - the message in the log is OK until December 31, 2014 - NOAA should, hopefully, release new coefs by that time

Pavel