On 18-09-15 17:04, bodenseepingu wrote:
> Am 18.09.2015 um 16:41 schrieb Sebastiaan Couwenberg:
>> On 18-09-15 16:35, bodenseepingu wrote:
>>> after compiling an update of libroutino and qmapshack I get the error
>>> message "Die vorgegebene XML Profildatei konnte nicht geladen werden" /
>>> XML profile could not be loaded - from Routino.
>>>
>>> After that I am not able to set a routino directory with the GUI, so
>>> routino is not working.
>>>
>>> What might go wrong? Any hints?
>> Have you installed the XML files after compiling the routino update?
>>
>> You should have at least profiles.xml, translations.xml & tagging.xml
>> installed in /usr/share/routino or /{usr,opt}/local/share/routino, these
>> are required by FindROUTINO.cmake in QMapShack.
> 
> OK - I did just make a sudo make install after compiling - old version
> was working...
> 
> make install in subdir xml copied routiono-profiles.xml,
> routiono-translations.xml, routino-tagging.xml, tagging-drive.xml,
> tagging-ride.xml, tagging-walk.xml to /usr/local/share/routino
> 
> But /usr/share/routino did exist from earlier version with old files.
> 
> removing of that directory did not help.
> 
> After copying all the xml files from /usr/local/share/routino to
> /usr/share/routino it worked.
> 
> Thank you. Problem was obviously old xml files ?

It looks like your mixing different installs (not properly removing the
previous install at least). That seems to have confused Routino because
the paths were not what it expected (as defined in
web/www/routino/paths.pl).

Your manual installs should not use /usr/share/routino,
/usr/local/share/routino is the appropriate path for custom local builds.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

------------------------------------------------------------------------------
_______________________________________________
Qlandkartegt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users

Reply via email to