Reply to topic

no console output and no osm-data

berndp
Registered Member
Posts
3
Karma
0

no console output and no osm-data

Wed Jan 04, 2017 2:23 pm
Hello,
I build and installed marble on Windows, and it seems to works, except two points:
- when I start marble via command line, there is no output on console, even if I use command line options like -h or --debug-info
- osm data is not loaded from internet

I have a second marble installed on a Debian-Linux on a VM.
The marble on Linux works in both points correct.
There are a lot of console outputs with --debug-info and osm-data is correct loaded (with the same proxy settings like on windows).

Thanks for help
Bernd
prese
Registered Member
Posts
1
Karma
0
Tell me, what type of proxy are you using? I just remember that I had a similar problem. And my proxy settings were set incorrectly. But I could be wrong.
berndp
Registered Member
Posts
3
Karma
0
It is a HTTP proxy.
I've already read the issue with the http prefix, but I use the name of the proxy server without the starting http:\\
The strange thing is, that the setting inside the VM works (debian) but the same setting doesn't work on the host.
I guess the reason is, on debian it was installed by apt and on windows I build it by sources.
May be there are build options, which cause proxy problems and also prevent the console output.
mirkos
Registered Member
Posts
1
Karma
0
I had the same problem.

It turned out that the default windows Qt 5 build lacks openSSL for legal (export) reasons. Thus SSL connections are not possible by default FOR ALL QT5 APPLICATIONS! :'(

However I was able to get OSM working within marble by manually replacing https with http in the marble/data/earth/openstreetmap/openstreetmap.dgml file. This solved the issue for me - at least as long as the data is provided via http too.

HTH,

Mirko
berndp
Registered Member
Posts
3
Karma
0
OK,
now I understand the missing console output in windows.

Marbles mDebug() depends on qDebug(). And qDebug() works only with the following line inside the .pro file:
CONFIG += console
see: http://stackoverflow.com/questions/3360 ... qt-gui-app
But this is more an QT in Windows topic.

To use mDebug() inside marble it is further important to enable the marble debug flag with:
MarbleDebug::setEnabled( true );

 
Reply to topic

Bookmarks



Who is online

Registered users: a17r, Baidu [Spider], Bing [Bot], claydoh, Google [Bot], johngb, joy, Mamarok, raphaelra, wizonesolutions