igotu2gpx team mailing list archive
-
igotu2gpx team
-
Mailing list archive
-
Message #00045
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
Mmm, that worked BUT I think there's still an issue:
The make:
Silly-iMac:igotu2gpx-0.2 Will$ make
cd src/igotu/ && /usr/bin/qmake igotu.pro -spec /usr/local/Qt4.5/
mkspecs/macx-g++ -macx -o Makefile
cd src/igotu/ && make -f Makefile
echo !_TAG_FILE_FORMAT 2 dummy > /Users/Will/Code/igotu2gpx-0.2/tags;
echo !_TAG_FILE_SORTED 1 dummy >> /Users/Will/Code/igotu2gpx-0.2/tags;
sed -i 's/ /\t/g' /Users/Will/Code/igotu2gpx-0.2/tags; cd /Users/Will/
Code/igotu2gpx-0.2 && ctags -R --c++-kinds=+p-n --fields=+iaS --extra=
+fq --exclude=.build -f - src | sed 's/igotu:://g;s/\tnamespace:igotu//
g' | LC_ALL=C sort >> tags || cd .
sed: 1: "/Users/Will/Code/igotu2 ...": invalid command code W
ctags: illegal option -- R
usage: ctags [-BFadtuwvx] [-f tagsfile] file ...
compiling pch.h
compiling pch.h
compiling commands.cpp
compiling dataconnection.cpp
compiling igotucommand.cpp
compiling igotupoints.cpp
compiling optionutils.cpp
compiling verbose.cpp
compiling xmlutils.cpp
compiling libusbconnection.cpp
rm -f libigotu.1.0.0.dylib libigotu.dylib libigotu.1.dylib libigotu.
1.0.dylib
linking ../../bin/debug/libigotu.1.0.0.dylib
ln -s libigotu.1.0.0.dylib libigotu.dylib
ln -s libigotu.1.0.0.dylib libigotu.1.dylib
ln -s libigotu.1.0.0.dylib libigotu.1.0.dylib
rm -f ../../bin/debug/libigotu.1.0.0.dylib
rm -f ../../bin/debug/libigotu.dylib
rm -f ../../bin/debug/libigotu.1.dylib
rm -f ../../bin/debug/libigotu.1.0.dylib
mv -f libigotu.1.0.0.dylib libigotu.dylib libigotu.1.dylib libigotu.
1.0.dylib ../../bin/debug/
cd src/igotu2gpx/ && /usr/bin/qmake igotu2gpx.pro -spec /usr/local/
Qt4.5/mkspecs/macx-g++ -macx -o Makefile
cd src/igotu2gpx/ && make -f Makefile
compiling igotu2gpx.cpp
linking ../../bin/debug/igotu2gpx.app/Contents/MacOS/igotu2gpx
The sudo make install:
Silly-iMac:igotu2gpx-0.2 Will$ sudo make install
Password:
cd src/igotu/ && make -f Makefile install
echo !_TAG_FILE_FORMAT 2 dummy > /Users/Will/Code/igotu2gpx-0.2/tags;
echo !_TAG_FILE_SORTED 1 dummy >> /Users/Will/Code/igotu2gpx-0.2/tags;
sed -i 's/ /\t/g' /Users/Will/Code/igotu2gpx-0.2/tags; cd /Users/Will/
Code/igotu2gpx-0.2 && ctags -R --c++-kinds=+p-n --fields=+iaS --extra=
+fq --exclude=.build -f - src | sed 's/igotu:://g;s/\tnamespace:igotu//
g' | LC_ALL=C sort >> tags || cd .
sed: 1: "/Users/Will/Code/igotu2 ...": invalid command code W
ctags: illegal option -- R
usage: ctags [-BFadtuwvx] [-f tagsfile] file ...
cp -f "../../bin/debug/libigotu.1.0.0.dylib" "/usr/local/lib/libigotu.
1.0.0.dylib"
ln -sf "libigotu.1.0.0.dylib" "/usr/local/lib/libigotu.dylib"
ln -sf "libigotu.1.0.0.dylib" "/usr/local/lib/libigotu.1.dylib"
ln -sf "libigotu.1.0.0.dylib" "/usr/local/lib/libigotu.1.0.dylib"
cd src/igotu2gpx/ && make -f Makefile install
rm -f -r "/usr/local/bin/igotu2gpx.app"
cp -f -R "../../bin/debug/igotu2gpx.app" "/usr/local/bin/igotu2gpx.app"
cp -f /Users/Will/Code/igotu2gpx-0.2/src/igotu2gpx/igotu2gpx.1 /usr/
local/share/man/man1/
cp -f /Users/Will/Code/igotu2gpx-0.2/LICENSE /usr/local/share/doc/
igotu2gpx/
cp -f /Users/Will/Code/igotu2gpx-0.2/HACKING /usr/local/share/doc/
igotu2gpx/
This gives me a igotu2gpx.app folder/application in the /usr/local/bin
directory which I can't run. That path is valid becuase I can run
other executables in the same dir. If I go into the directory
structure (/usr/local/bin/igotu2gpx.app/Contents/MacOS) then I can run
it:
Silly-iMac:MacOS Will$ ./igotu2gpx info
Unable to create gps tracker connection: Unable to find device 0df7:0900
Silly-iMac:MacOS Will$ ./igotu2gpx --help
Usage:
igotu2gpx dump|info|diff [OPTIONS...]
Options:
--help this help message
-i [ --image ] arg instead of connecting to the gps
tracker, use the
specified image file (saved by "dump --
raw")
-s [ --serial-device ] arg connect via RS232 to the serial port
with the
specfied number (this is the default on
Windows)
--gpx output in gpx format (this is the default)
--details output a detailed representation of the
track
--raw arg output the raw flash contents of the gps
tracker
--count arg limits the number of sectors read (4096
bytes
each)
-v [ --verbose ] increase the amount of informative
messages
--action arg dump: dump the trackpoints
info: show general info
diff: show change relative to image file
So assuming this works (current lack of a working igotu device makes
this tricky....) there's just some Mac specifics to work out. I moved
the igotu2gpx executable to /usr/local/bin/ then rm -r the
igotu2gpx.app directory and can then run it fine.
very close now...
On 16 Apr 2009, at 16:20, Michael Hofmann wrote:
>> libboost_program_options-xgcc40-mt.dylib
> I changed the build system to be more flexible on Mac OS X, so you
> can define
>
> macx:BOOSTROOT = /usr/local
> macx:BOOSTINCLUDEDIR = $${BOOSTROOT}/include/boost-1_38
> macx:BOOSTLIBDIR = $${BOOSTROOT}/lib
> macx:BOOSTPOLIB = boost_program_options-xgcc40-mt
>
> and it will hopefully use these. Next try :-).
>
> --
> Errors while compiling on Mac OS X
> https://bugs.launchpad.net/bugs/361820
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in MobileAction i-gotU USB GPS travel logger Mac/Linux
> support: Incomplete
>
> Bug description:
> Compiling on Mac OS X does not work, but it should theoretically.
>
> After a long break at programming, I'm trying to work out how to
> make use of the work done for the i-gotU. If someone could fill in
> any gaps I'd appreciate it.... I've not done dev on the Mac before
> but am familiar with Solaris/UNIX/C.
>
> Mac 10.5.6, Intel iMac, Xcode 3.1.2 tools installed, boost 1.38.0
> installed (std ./configure used - resulted in /usr/local install),
> Qt4.5.0 installed
>
> The install file states:
>
> To compile igotu2gpx, you need:
> - qt4
> - boost
> - boost-program-options
> - libusb
> - chrpath (optional, makes it possible to run the program without
> installation)
>
> So I have a compiler, I have qt4 and boost (which seems to include
> program-options).
>
> - libusb most recent version does not work on Mac so I instead used
> 0.1.12which installed in /usr/local/lib
> - chrpath could not find this but as it's optional this should be
> okay??
>
> So now what.. I tried qmake in igotu directory (prompt returns with
> no message) followed by make which returns with make: *** No targets
> specified and no makefile found. Stop.
>
> I' not sure if Qt Creator can/should be used or if the command line
> approach should work. I've not made any changes to include/path and
> wonder this would help and if so how should it be done?
>
> Plenty of questions and I appreciate any feedback/pointers to
> tutorials.
>
--
Errors while compiling on Mac OS X
https://bugs.launchpad.net/bugs/361820
You received this bug notification because you are a member of
MobileAction i-gotU USB GPS travel logger Mac/Linux support developers,
which is the registrant for igotu2gpx.
Status in MobileAction i-gotU USB GPS travel logger Mac/Linux support: Incomplete
Bug description:
Compiling on Mac OS X does not work, but it should theoretically.
After a long break at programming, I'm trying to work out how to make use of the work done for the i-gotU. If someone could fill in any gaps I'd appreciate it.... I've not done dev on the Mac before but am familiar with Solaris/UNIX/C.
Mac 10.5.6, Intel iMac, Xcode 3.1.2 tools installed, boost 1.38.0 installed (std ./configure used - resulted in /usr/local install), Qt4.5.0 installed
The install file states:
To compile igotu2gpx, you need:
- qt4
- boost
- boost-program-options
- libusb
- chrpath (optional, makes it possible to run the program without installation)
So I have a compiler, I have qt4 and boost (which seems to include program-options).
- libusb most recent version does not work on Mac so I instead used 0.1.12which installed in /usr/local/lib
- chrpath could not find this but as it's optional this should be okay??
So now what.. I tried qmake in igotu directory (prompt returns with no message) followed by make which returns with make: *** No targets specified and no makefile found. Stop.
I' not sure if Qt Creator can/should be used or if the command line approach should work. I've not made any changes to include/path and wonder this would help and if so how should it be done?
Plenty of questions and I appreciate any feedback/pointers to tutorials.
Follow ups
References
-
[Bug 361820] Re: Errors while compiling on Mac OS X
From: Michael Hofmann, 2009-04-15
-
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
From: billy920, 2009-04-15
-
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
From: Michael Hofmann, 2009-04-15
-
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
From: billy920, 2009-04-16
-
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
From: Michael Hofmann, 2009-04-16
-
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
From: billy920, 2009-04-16
-
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
From: Michael Hofmann, 2009-04-16
-
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
From: billy920, 2009-04-16
-
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
From: Michael Hofmann, 2009-04-16
-
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
From: billy920, 2009-04-16
-
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
From: Michael Hofmann, 2009-04-16
-
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
From: billy920, 2009-04-16
-
Re: [Bug 361820] Re: Errors while compiling on Mac OS X
From: Michael Hofmann, 2009-04-16