Re: [Viking-devel] Export via GPSbabel
Robert Norris writes: > I note it says "IMPORTANT: Do not port to the new system if the > application still needs to run under GNOME 2. Yelp 2 does not > recognize the new help system." > > Is this important for us? I guess it means help wouldn't work on a > MATE desktop. My opinion is that while using gnomish things is the preferred path, to the extent viking works with gtk2+ without needing all of gnome, that's a big positive. On my system the viking binary has a vast number of libs but not gnome. Perhaps I'm help-deficient. pgpB_g4pXNfiU.pgp Description: PGP signature -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Export via GPSbabel
> > As other solution, I propose: > - use autoreconf (directly related to other autotools) > - directly call gtkdocize from our autogen.sh (single line) > - concert help from DocBook to Mallard: Mallard is simple and > non-linear, modern approach to user documentation. > I'm thinking about the last item of my list since long time now. This > can be the good occasion. The most notable lost of feature is that I do > not know how to generate a single PDF from a collection of mallard > files. The only reason for PDF generation in my opinion as it's the only current help delivered on Windows builds. > http://projectmallard.org/ Using Mallard for the XML will not of course magically make the documentation any better. Some one still has to write it. Considering no-one else is volunteering to update any Wiki material, I doubt whether changing to Mallard will make much difference. Presumably Yelp can cope with documentation in both DocBook and Mallard at the same time? > Furthermore, I feel that gnome-autogen.sh is going to be deprecated, > like DocBook is. > https://wiki.gnome.org/GnomeDocUtilsMigrationHowTo > https://wiki.gnome.org/GnomeGoals/NewDocumentationInfrastructure I note it says "IMPORTANT: Do not port to the new system if the application still needs to run under GNOME 2. Yelp 2 does not recognize the new help system." Is this important for us? I guess it means help wouldn't work on a MATE desktop. > What should we do? If you want to lead the change then do it. I can not find a pre built version of Yelp to use under Windows. However I can fairly easily switch the Windows build to use Compiled HTML (using HTML Help Workshop). MacOS - not worried about the help system - would like the latest main program to be consistently available first! (MacPorts has version 1.4). NB MacPorts only has Yelp2. -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Export via GPSbabel
>>There is many things to do now. For example, allowing such "export" feature >>at the File->Export level. I also realized that this is one more "export" >> sub-menu entry. From the simple user point of view, a single "Export" >> dialog would certainly be better, allowing export to GPX, KML and any other >> file format known by gpsbabel or viking. >My opinion is that GPX is the one true format, and the others are useful >but can also be distracting. So I think export to GPX should be able to >happen with no adtitional barriers. Perhaps if gpx is preselected so >you can just hit return once the file is specified that's ok. > Basically I'm saying that logically I see options as >export as gpx >export to some other format, with a dialog to choose it I'd just to say that I agree with Greg here. I think it is really useful to have GPX as the primary export option since it is the de facto standard. It may not be conceptually clean but I think it's more user friendly for the presumed majority that use GPX - because it's the mostly widely supported type. I only added a KML option here because it's probably quite popular than the rest of the formats, but I'd happily relegate it into a GPSBabel option. The main sticking points are GPSMapper and GPSPoints - stuff that I expect hardly any one uses - but the capability is built into Viking. Putting it into a single export UI is probably very hard. I'd be tempted with: Export->GPX Export->Other->GPSMapper Export->Other->GPSPoint Export->With GPSBabel... Trouble is what happens if include an option for GeoJSON, depending on how it's implemented. I've being thinking of adding in GeoJSON support some how but haven't found a simple/clean way to do. I thought about supporting GeoJSON natively in Viking but that's a lot of coding effort, but could be plus point for Viking. Alternatively putting in GeoJSON support into GPSBabel would help lots of other people. Unfortunately it seems GPSBabel is going through the transition to Qt framework. This work may be complete but I couldn't see how to write a new format for GPSBabel very easily (even if the current google_maps thing does a certain amount it's geojson->gpx not an export option for us). Trying to use ogr2ogr produces ugly output, has annoying command line behaviour (IIRC needing '-overwrite' to overwrite an existing file but the command fails when -overwrite is used but it's a new file. or something like the command failing if you specify both waypoints and tracks at the same time but the layer has no waypoints - i.e. need to tailor the options exactly depending on what input you give it) I haven't investigated MapBox's togeojson (a node.js thing) yet, because I've yet to install it on my system... -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Export via GPSbabel
Guilhem Bonnefille wrote: > In order to unlock some users, here is a patch. patch applied to latest git.. *OK* on ubuntu13.10 thx! have a nice day Wolfgang > > > 2013/11/6 Guilhem Bonnefille > > > > > > > > > 2013/11/5 Robert Norris > > > >> Yes I was incorrectly reading the SHA for the commits in the > >> output from gitg (since it shows parent SHA too) > >> > >> So gnome-autogen.sh was doing something useful after all, copying > >> or linking: > >> gnome-doc-utils.make > >> gtk-doc.make > >> omf.make > >> xmldocs.make > >> > >> It seems the latest gnome-common (3.10) in Debian has fixed the > >> previous dodgy automake version checking. > >> > >> I suggest reverting back to the old autogen.sh script which uses > >> gnome-autogen.sh script. > >> > > > > It could be a solution. > > > > As other solution, I propose: > > - use autoreconf (directly related to other autotools) > > - directly call gtkdocize from our autogen.sh (single line) > > - concert help from DocBook to Mallard: Mallard is simple and > > non-linear, modern approach to user documentation. > > I'm thinking about the last item of my list since long time now. > > This can be the good occasion. The most notable lost of feature is > > that I do not know how to generate a single PDF from a collection > > of mallard files. > > > > http://projectmallard.org/ > > > > Furthermore, I feel that gnome-autogen.sh is going to be > > deprecated, like DocBook is. > > https://wiki.gnome.org/GnomeDocUtilsMigrationHowTo > > https://wiki.gnome.org/GnomeGoals/NewDocumentationInfrastructure > > > > What should we do? > > -- > > Guilhem BONNEFILLE > > -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com > > -=- mailto:guilhem.bonnefi...@gmail.com > > -=- http://nathguil.free.fr/ > > > > > signature.asc Description: PGP signature -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Export via GPSbabel
In order to unlock some users, here is a patch. 2013/11/6 Guilhem Bonnefille > > > > 2013/11/5 Robert Norris > >> Yes I was incorrectly reading the SHA for the commits in the output from >> gitg (since it shows parent SHA too) >> >> So gnome-autogen.sh was doing something useful after all, copying or >> linking: >> gnome-doc-utils.make >> gtk-doc.make >> omf.make >> xmldocs.make >> >> It seems the latest gnome-common (3.10) in Debian has fixed the previous >> dodgy automake version checking. >> >> I suggest reverting back to the old autogen.sh script which uses >> gnome-autogen.sh script. >> > > It could be a solution. > > As other solution, I propose: > - use autoreconf (directly related to other autotools) > - directly call gtkdocize from our autogen.sh (single line) > - concert help from DocBook to Mallard: Mallard is simple and non-linear, > modern approach to user documentation. > I'm thinking about the last item of my list since long time now. This can > be the good occasion. The most notable lost of feature is that I do not > know how to generate a single PDF from a collection of mallard files. > > http://projectmallard.org/ > > Furthermore, I feel that gnome-autogen.sh is going to be deprecated, like > DocBook is. > https://wiki.gnome.org/GnomeDocUtilsMigrationHowTo > https://wiki.gnome.org/GnomeGoals/NewDocumentationInfrastructure > > What should we do? > -- > Guilhem BONNEFILLE > -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com > -=- mailto:guilhem.bonnefi...@gmail.com > -=- http://nathguil.free.fr/ > -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ commit 3879238727483edf22dde4b5a2fe44bd91f1a8e1 Author: Guilhem Bonnefille Date: Wed Nov 6 23:15:52 2013 +0100 Fix autogen.sh in order to install needed files diff --git a/autogen.sh b/autogen.sh index 0ef7c28..46f4a3d 100755 --- a/autogen.sh +++ b/autogen.sh @@ -13,6 +13,18 @@ if test -z $INTLTOOLIZE; then exit 1 fi +GTK_DOC=`which gtkdocize` +if test -z $GTK_DOC; then +echo "*** No gtkdocize found, please install the gtk-doc-tools package ***" +exit 1 +fi + +GNOME_DOC=`which gnome-doc-prepare` +if test -z $GNOME_DOC; then +echo "*** No gnome-doc-prepare found, please install the gnome-doc-utils package ***" +exit 1 +fi + AUTORECONF=`which autoreconf` if test -z $AUTORECONF; then echo "*** No autoreconf found, please install it ***" @@ -24,7 +36,9 @@ if test -z `which autopoint`; then exit 1 fi -autopoint --force +gnome-doc-prepare --automake --copy --force || exit $? +gtkdocize --copy || exit $? +autopoint --force || exit $? AUTOPOINT='intltoolize --automake --copy' autoreconf --force --install --verbose || exit $? cd "$olddir" -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Export via GPSbabel
2013/11/5 Robert Norris > Yes I was incorrectly reading the SHA for the commits in the output from > gitg (since it shows parent SHA too) > > So gnome-autogen.sh was doing something useful after all, copying or > linking: > gnome-doc-utils.make > gtk-doc.make > omf.make > xmldocs.make > > It seems the latest gnome-common (3.10) in Debian has fixed the previous > dodgy automake version checking. > > I suggest reverting back to the old autogen.sh script which uses > gnome-autogen.sh script. > It could be a solution. As other solution, I propose: - use autoreconf (directly related to other autotools) - directly call gtkdocize from our autogen.sh (single line) - concert help from DocBook to Mallard: Mallard is simple and non-linear, modern approach to user documentation. I'm thinking about the last item of my list since long time now. This can be the good occasion. The most notable lost of feature is that I do not know how to generate a single PDF from a collection of mallard files. http://projectmallard.org/ Furthermore, I feel that gnome-autogen.sh is going to be deprecated, like DocBook is. https://wiki.gnome.org/GnomeDocUtilsMigrationHowTo https://wiki.gnome.org/GnomeGoals/NewDocumentationInfrastructure What should we do? -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Export via GPSbabel
There is many things to do now. For example, allowing such "export" feature at the File->Export level. I also realized that this is one more "export" sub-menu entry. From the simple user point of view, a single "Export" dialog would certainly be better, allowing export to GPX, KML and any other file format known by gpsbabel or viking. My opinion is that GPX is the one true format, and the others are useful but can also be distracting. So I think export to GPX should be able to happen with no adtitional barriers. Perhaps if gpx is preselected so you can just hit return once the file is specified that's ok. Basically I'm saying that logically I see options as export as gpx export to some other format, with a dialog to choose it pgppDDbw30Dlh.pgp Description: PGP signature -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Export via GPSbabel
Yes I was incorrectly reading the SHA for the commits in the output from gitg (since it shows parent SHA too) So gnome-autogen.sh was doing something useful after all, copying or linking: gnome-doc-utils.make gtk-doc.make omf.make xmldocs.make It seems the latest gnome-common (3.10) in Debian has fixed the previous dodgy automake version checking. I suggest reverting back to the old autogen.sh script which uses gnome-autogen.sh script. > To: rw_nor...@hotmail.com > CC: wolfgang.zt...@web.de; viking-devel@lists.sourceforge.net > > I do not already find "THE" solution but the matter is the related to > the missing gtk-doc.make and gnome-doc-utils.make files. > > The simplest solution for users, at the moment, is to hack > configure.ac<http://configure.ac> to remove reference to help/Makefile > and doc/reference/Makefile. > > > 2013/11/5 Guilhem Bonnefille > mailto:guilhem.bonnefi...@gmail.com>> > Between 04b23911c20c990968128920ad2252f529fb8f3d > and 2598086bbc61585ad4cb61ebd23b67fa09f00207 there is my change on > autogen. > > > 2013/11/5 Robert Norris mailto:rw_nor...@hotmail.com>> > I can reproduce this on my Debian unstable system. > > I seems it's my commit 04b23911c20c990968128920ad2252f529fb8f3d, that > breaks it, but only on a totally clean clone. > > How changing the .gitignore file and some text in the INSTALL file > effects the build system is beyond me. > > I'm not quite sure why the INSTALL file is under our change control > when one of the autotools things generates it. > > I will investigate further later on tonight. > > Be Seeing You - Rob. > If at first you don't succeed, > then skydiving isn't for you. > > > > Date: Tue, 5 Nov 2013 17:26:13 +0100 > From: wolfgang.zt...@web.de<mailto:wolfgang.zt...@web.de> > To: guilhem.bonnefi...@gmail.com<mailto:guilhem.bonnefi...@gmail.com> > CC: > viking-devel@lists.sourceforge.net<mailto:viking-devel@lists.sourceforge.net> > Subject: Re: [Viking-devel] Export via GPSbabel > > > Guilhem Bonnefille wrote: > > > Hi all, > > Hi Guilhem, > > which system are you working with? > at least on fedora19 and ubuntu13.10 it doesn't work. > > > *fresh* git clone: (ubuntu1310) > git clone http://git.code.sf.net/p/viking/code viking_sf > cd viking_sf > ./autogen.sh > ... > config.status: error: cannot find input file: `src/Makefile.in' > > > > > this is my last good compile: > git clean -x -f > git checkout 2598086bbc61585ad4cb61ebd23b67fa09f00207 > autogen.sh > make > sudo make install > OK! > > > -rwxr-xr-x 1 root root 4418832 Nov 5 17:23 /usr/local/bin/viking > viking --version > viking 1.5 > Copyright (c) 2003-2008 Evan Battaglia > Copyright (c) 2008-2012 Viking's contributors > > > kind regards > Wolfgang > > > > > > Since few years, I always missed something in viking: the ability to > > directly export data into the file format expected by my device. > > > > After few days of work and few more days to hesitate, I finally > > pushed my changes into master. > > > > There is many things to do now. For example, allowing such "export" > > feature at the File->Export level. I also realized that this is one > > more "export" sub-menu entry. From the simple user point of view, a > > single "Export" dialog would certainly be better, allowing export to > > GPX, KML and any other file format known by gpsbabel or viking. > > > > A new refactoring needed for future. > > > > -- > > November Webinars for C, C++, Fortran Developers > Accelerate application performance with scalable programming models. Explore > techniques for threading, error checking, porting, and tuning. Get the most > from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk > ___ > Viking-devel mailing list > Viking-devel@lists.sourceforge.net<mailto:Viking-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/viking-devel > Viking home page: http://viking.sf.net/ > > > > -- > Guilhem BONNEFILLE > -=- JID: gu...@im.apinc.org<mailto:gu...@im.apinc.org> MSN: > guilhem_bonnefi...@hotmail.com<mailto:guilhem_bonnefi...@hot
Re: [Viking-devel] Export via GPSbabel
I do not already find "THE" solution but the matter is the related to the missing gtk-doc.make and gnome-doc-utils.make files. The simplest solution for users, at the moment, is to hack configure.ac to remove reference to help/Makefile and doc/reference/Makefile. 2013/11/5 Guilhem Bonnefille > Between 04b23911c20c990968128920ad2252f529fb8f3d > and 2598086bbc61585ad4cb61ebd23b67fa09f00207 there is my change on autogen. > > > 2013/11/5 Robert Norris > >> I can reproduce this on my Debian unstable system. >> >> I seems it's my commit 04b23911c20c990968128920ad2252f529fb8f3d, that >> breaks it, but only on a totally clean clone. >> >> How changing the .gitignore file and some text in the INSTALL file >> effects the build system is beyond me. >> >> I'm not quite sure why the INSTALL file is under our change control when >> one of the autotools things generates it. >> >> I will investigate further later on tonight. >> >> Be Seeing You - Rob. >> If at first you don't succeed, >> then skydiving isn't for you. >> >> >> >> Date: Tue, 5 Nov 2013 17:26:13 +0100 >> From: wolfgang.zt...@web.de >> To: guilhem.bonnefi...@gmail.com >> CC: viking-devel@lists.sourceforge.net >> Subject: Re: [Viking-devel] Export via GPSbabel >> >> >> Guilhem Bonnefille wrote: >> >> > Hi all, >> >> Hi Guilhem, >> >> which system are you working with? >> at least on fedora19 and ubuntu13.10 it doesn't work. >> >> >> *fresh* git clone: (ubuntu1310) >> git clone http://git.code.sf.net/p/viking/code viking_sf >> cd viking_sf >> ./autogen.sh >> ... >> config.status: error: cannot find input file: `src/Makefile.in' >> >> >> >> >> this is my last good compile: >> git clean -x -f >> git checkout 2598086bbc61585ad4cb61ebd23b67fa09f00207 >> autogen.sh >> make >> sudo make install >> OK! >> >> >> -rwxr-xr-x 1 root root 4418832 Nov 5 17:23 /usr/local/bin/viking >> viking --version >> viking 1.5 >> Copyright (c) 2003-2008 Evan Battaglia >> Copyright (c) 2008-2012 Viking's contributors >> >> >> kind regards >> Wolfgang >> >> >> >> >> > Since few years, I always missed something in viking: the ability to >> > directly export data into the file format expected by my device. >> > >> > After few days of work and few more days to hesitate, I finally >> > pushed my changes into master. >> > >> > There is many things to do now. For example, allowing such "export" >> > feature at the File->Export level. I also realized that this is one >> > more "export" sub-menu entry. From the simple user point of view, a >> > single "Export" dialog would certainly be better, allowing export to >> > GPX, KML and any other file format known by gpsbabel or viking. >> > >> > A new refactoring needed for future. >> >> >> >> >> -- >> November Webinars for C, C++, Fortran Developers >> Accelerate application performance with scalable programming models. >> Explore >> techniques for threading, error checking, porting, and tuning. Get the >> most >> from the latest Intel processors and coprocessors. See abstracts and >> register >> >> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk >> ___ >> Viking-devel mailing list >> Viking-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/viking-devel >> Viking home page: http://viking.sf.net/ >> > > > > > -- > Guilhem BONNEFILLE > -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com > -=- mailto:guilhem.bonnefi...@gmail.com > -=- http://nathguil.free.fr/ > -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Export via GPSbabel
Between 04b23911c20c990968128920ad2252f529fb8f3d and 2598086bbc61585ad4cb61ebd23b67fa09f00207 there is my change on autogen. 2013/11/5 Robert Norris > I can reproduce this on my Debian unstable system. > > I seems it's my commit 04b23911c20c990968128920ad2252f529fb8f3d, that > breaks it, but only on a totally clean clone. > > How changing the .gitignore file and some text in the INSTALL file effects > the build system is beyond me. > > I'm not quite sure why the INSTALL file is under our change control when > one of the autotools things generates it. > > I will investigate further later on tonight. > > Be Seeing You - Rob. > If at first you don't succeed, > then skydiving isn't for you. > > > > Date: Tue, 5 Nov 2013 17:26:13 +0100 > From: wolfgang.zt...@web.de > To: guilhem.bonnefi...@gmail.com > CC: viking-devel@lists.sourceforge.net > Subject: Re: [Viking-devel] Export via GPSbabel > > > Guilhem Bonnefille wrote: > > > Hi all, > > Hi Guilhem, > > which system are you working with? > at least on fedora19 and ubuntu13.10 it doesn't work. > > > *fresh* git clone: (ubuntu1310) > git clone http://git.code.sf.net/p/viking/code viking_sf > cd viking_sf > ./autogen.sh > ... > config.status: error: cannot find input file: `src/Makefile.in' > > > > > this is my last good compile: > git clean -x -f > git checkout 2598086bbc61585ad4cb61ebd23b67fa09f00207 > autogen.sh > make > sudo make install > OK! > > > -rwxr-xr-x 1 root root 4418832 Nov 5 17:23 /usr/local/bin/viking > viking --version > viking 1.5 > Copyright (c) 2003-2008 Evan Battaglia > Copyright (c) 2008-2012 Viking's contributors > > > kind regards > Wolfgang > > > > > > Since few years, I always missed something in viking: the ability to > > directly export data into the file format expected by my device. > > > > After few days of work and few more days to hesitate, I finally > > pushed my changes into master. > > > > There is many things to do now. For example, allowing such "export" > > feature at the File->Export level. I also realized that this is one > > more "export" sub-menu entry. From the simple user point of view, a > > single "Export" dialog would certainly be better, allowing export to > > GPX, KML and any other file format known by gpsbabel or viking. > > > > A new refactoring needed for future. > > > > > -- > November Webinars for C, C++, Fortran Developers > Accelerate application performance with scalable programming models. > Explore > techniques for threading, error checking, porting, and tuning. Get the most > from the latest Intel processors and coprocessors. See abstracts and > register > http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk > ___ > Viking-devel mailing list > Viking-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/viking-devel > Viking home page: http://viking.sf.net/ > -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Export via GPSbabel
I can reproduce this on my Debian unstable system. I seems it's my commit 04b23911c20c990968128920ad2252f529fb8f3d, that breaks it, but only on a totally clean clone. How changing the .gitignore file and some text in the INSTALL file effects the build system is beyond me. I'm not quite sure why the INSTALL file is under our change control when one of the autotools things generates it. I will investigate further later on tonight. Be Seeing You - Rob. If at first you don't succeed, then skydiving isn't for you. Date: Tue, 5 Nov 2013 17:26:13 +0100 From: wolfgang.zt...@web.de To: guilhem.bonnefi...@gmail.com CC: viking-devel@lists.sourceforge.net Subject: Re: [Viking-devel] Export via GPSbabel Guilhem Bonnefille wrote: > Hi all, Hi Guilhem, which system are you working with? at least on fedora19 and ubuntu13.10 it doesn't work. *fresh* git clone: (ubuntu1310) git clone http://git.code.sf.net/p/viking/code viking_sf cd viking_sf ./autogen.sh ... config.status: error: cannot find input file: `src/Makefile.in' this is my last good compile: git clean -x -f git checkout 2598086bbc61585ad4cb61ebd23b67fa09f00207 autogen.sh make sudo make install OK! -rwxr-xr-x 1 root root 4418832 Nov 5 17:23 /usr/local/bin/viking viking --version viking 1.5 Copyright (c) 2003-2008 Evan Battaglia Copyright (c) 2008-2012 Viking's contributors kind regards Wolfgang > Since few years, I always missed something in viking: the ability to > directly export data into the file format expected by my device. > > After few days of work and few more days to hesitate, I finally > pushed my changes into master. > > There is many things to do now. For example, allowing such "export" > feature at the File->Export level. I also realized that this is one > more "export" sub-menu entry. From the simple user point of view, a > single "Export" dialog would certainly be better, allowing export to > GPX, KML and any other file format known by gpsbabel or viking. > > A new refactoring needed for future. -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/ -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Export via GPSbabel
Guilhem Bonnefille wrote: > Hi all, Hi Guilhem, which system are you working with? at least on fedora19 and ubuntu13.10 it doesn't work. *fresh* git clone: (ubuntu1310) git clone http://git.code.sf.net/p/viking/code viking_sf cd viking_sf ./autogen.sh ... config.status: error: cannot find input file: `src/Makefile.in' this is my last good compile: git clean -x -f git checkout 2598086bbc61585ad4cb61ebd23b67fa09f00207 autogen.sh make sudo make install OK! -rwxr-xr-x 1 root root 4418832 Nov 5 17:23 /usr/local/bin/viking viking --version viking 1.5 Copyright (c) 2003-2008 Evan Battaglia Copyright (c) 2008-2012 Viking's contributors kind regards Wolfgang > Since few years, I always missed something in viking: the ability to > directly export data into the file format expected by my device. > > After few days of work and few more days to hesitate, I finally > pushed my changes into master. > > There is many things to do now. For example, allowing such "export" > feature at the File->Export level. I also realized that this is one > more "export" sub-menu entry. From the simple user point of view, a > single "Export" dialog would certainly be better, allowing export to > GPX, KML and any other file format known by gpsbabel or viking. > > A new refactoring needed for future. signature.asc Description: PGP signature -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
[Viking-devel] Export via GPSbabel
Hi all, Since few years, I always missed something in viking: the ability to directly export data into the file format expected by my device. After few days of work and few more days to hesitate, I finally pushed my changes into master. There is many things to do now. For example, allowing such "export" feature at the File->Export level. I also realized that this is one more "export" sub-menu entry. From the simple user point of view, a single "Export" dialog would certainly be better, allowing export to GPX, KML and any other file format known by gpsbabel or viking. A new refactoring needed for future. -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
