maemo.org - Talk - [ANNOUNCE] Columbus Navigation Toolkit

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - [ANNOUNCE] Columbus Navigation Toolkit (https://talk.maemo.org/showthread.php?t=67276)

Re: [ANNOUNCE] Columbus Navigation Toolkit

why don't you just link the .desktop file to a shell script that appends /opt/usr/lib or whatever to LD_LIBRARY_PATH? Like Marble does. then call main app from the script.

Re: [ANNOUNCE] Columbus Navigation Toolkit

Quote:

Originally Posted by Android_808 (Post 907740)

why don't you just link the .desktop file to a shell script that appends /opt/usr/lib or whatever to LD_LIBRARY_PATH? Like Marble does. then call main app from the script.

Good idea,

Re: [ANNOUNCE] Columbus Navigation Toolkit

haven't got columbus installed. should be pretty easy though. i use it to run a desktop project with loads of shared libraries. bit more complex as its based off the quake 3 launcher script.

Re: [ANNOUNCE] Columbus Navigation Toolkit

Personally as "/opt/usr" is the default install prefix in Qt Creator for maemo projects, I think that /opt/usr/bin should be in $PATH and /opt/usr/lib should be in /etc/ld.so.conf, but who should set that up :)

Re: [ANNOUNCE] Columbus Navigation Toolkit

As ld.so.conf is a major file, would you want your app to be the reason someones device gets messed up if something goes wrong. at least the scripted way the change is only temporary, only being made when the app is run and then undone on reboot

Re: [ANNOUNCE] Columbus Navigation Toolkit

Quote:

Originally Posted by Android_808 (Post 907816)

Actually unless you export your LD_LIBRARY_PATH variable, it's only in effect for the duration of your shell script/app is running.

"/etc/ld.so.conf" is a system configuration file that I am only using for its' intended purpose. I'm using it for exactly the reason it's there ..

But It shouldn't necessarily be up to my app to add the "/opt/usr" prefix into the system. There should be some Qt Application package that does it, that I and other developers would then depend on so we didn't have to worry about setting the system up correctly ourselves ..

Re: [ANNOUNCE] Columbus Navigation Toolkit

will this app EASILY give me the exact geographic coordinates of where i am at any moment? if so how? i see from the screenshots that there are some coordinates. if this app does then i will love you forever!

Re: [ANNOUNCE] Columbus Navigation Toolkit

Quote:

Originally Posted by ddiscodave (Post 907862)

The application displays latitude and longitude in various formats, it's not exactly the first that does it though :P

Re: [ANNOUNCE] Columbus Navigation Toolkit

Quote:

Originally Posted by ajack (Post 907705)

@tswindell:

I have this problem where I run Columbus, and it runs fine... but about a minute later the program quits.

Also, I had installation problems earlier and had to append in file /etc/ld.so.conf the string "/opt/usr/lib/" before I got it working.

Is there anything you need from me to help you debug this?

Hi tswindell,

I didn't hear from you since my last post and decided to give you whatever info I could get from the error. When I run columbus from a terminal shell, I got the following:

Quote:

/opt/usr/bin $ ./columbus
ApplicationController: Creating telemetry source objects.
ApplicationController: Initializing configuration manager.
ApplicationController: Initializing logging manager.
ApplicationController: Initializing plugin management system.
PluginManager: ctor()
PluginManager: Loading plugins from: "/opt/usr/lib/columbus/plugins"
PluginManager: Found plugin candidate: "libbluetooth-plugin.so"
PluginManager: Loading plugin candidate: "libbluetooth-plugin.so"
BluetoothServerPlugin: ctor()
BluetoothServerPlugin: Initializing plugin.
BluetoothOptionsDialog: Restoring configuration.
BluetoothOptionsDialog: Performing UI update.
BluetoothOptionsDialog: Performing UI update.
PluginManager: Registered plugin: "bluetooth-server"
PluginManager: Found plugin candidate: "libnetwork-plugin.so"
PluginManager: Loading plugin candidate: "libnetwork-plugin.so"
NetworkServerPlugin: ctor()
NetworkServerPlugin: Initializing plugin.
NetworkServerPlugin: Loading configuration settings.
NetworkOptionsDialog: Restoring configuration.
NetworkOptionsDialog: Performing UI update.
NetworkOptionsDialog: Performing UI update.
NetworkOptionsDialog: Performing UI update.
NetworkOptionsDialog: Performing UI update.
PluginManager: Registered plugin: "network-server-plugin"
PluginManager: Found plugin candidate: "libusb-serial-plugin.so"
PluginManager: Loading plugin candidate: "libusb-serial-plugin.so"
USBSerialPlugin: ctor()
USBSerialPlugin: Initializing plugin.
USBSerialOptionsDialog: Loading settings.
USBSerialOptionsDialog: Performing UI update.
PluginManager: Registered plugin: "usb-serial"
ApplicationController: Loading application configuration.
ApplicationController: Attempting to start up location services.
ApplicationController: Location services started.
ApplicationController: Connecting telemetry source signals.
ColumbusDialogLogging: Loading settings.
ColumbusDialogLogging: Performing UI update.
MainWindow: Enabling screen saver inhibit.
MainWindow: Window activate event.
MainWindow: Resuming UI updates.
MainWindow: Window deactivate event.
MainWindow: Disabling screen saver inhibit.
MainWindow: Suspending UI updates.
MainWindow: Window activate event.
MainWindow: Resuming UI updates.
MainWindow: Enabling screen saver inhibit.
Segmentation fault

Hope this helps as I really like this program...

Re: [ANNOUNCE] Columbus Navigation Toolkit

Quote:

Originally Posted by tswindell (Post 907585)

You need to pair your N900 with the N95 and set the N900 to accept connections automatically from the N95, then, make sure Bluetooth is on from the system tray then enable bluetooth streaming in Columbus

here is columbus output message:

ServicePerformerFactory: destroyInstance() - Unregistering with logging manager.
BluetoothAcceptor: Destroying transport.
BluetoothAcceptor: Notifying upper layer.
BluetoothAcceptor: Remote endpoint "00:1A:DC:D4:8D:5C" connected, creating transport handle.
BluetoothAcceptor: Creating service performer.
ServicePerformerFactory - Creating instance.
ServicePerformerFactory - Registering instance with logging manager.
BluetoothAcceptor: Notifying upper layer.
BluetoothAcceptor: Shutting down transport device.
BluetoothAcceptor: Remote endpoint disconnected, destroying performer.

"00:1A:DC:D4:8D:5C" is my n95.

is the n95 not support NMEA format?