← Back to team overview

igotu2gpx team mailing list archive

Re: [Bug 361820] Re: Errors while compiling on Mac OS X

 

What do you mean, kind of..... ;-)

Some error output at the end of the make relating to program options.  
Remember I have boost 1.38.0 installed and have previously assumed  
that program options was included. There are certainly files relating  
to this in //usr/local/include/boost-1_38/boost/program_options so not  
sure why the error is there.

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
ld: library not found for -lboost_program_options-mt
collect2: ld returned 1 exit status
make[1]: *** [../../bin/debug/igotu2gpx.app/Contents/MacOS/igotu2gpx]  
Error 1
make: *** [sub-src-igotu2gpx-make_default] Error 2

Will

On 16 Apr 2009, at 14:14, Michael Hofmann wrote:

> I played around in the build system, seems like qmake thinks that  
> Mac OS
> X is a unix system (which is kind of true :-).
>
>> ld: unknown option: -rpath-link=/Users/Will/Code/igotu2gpx-0.2/bin/ 
>> debug
> So this should be solved, but maybe I did mess up sth. else. Give it a
> try.
>
> Michael
>
> -- 
> 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