igotu2gpx team mailing list archive

[billy920 <cwscott@xxxxxxx>]

This one then:

-rw-r--r--  1 root  wheel   2472932 14 Apr 18:47  
libboost_program_options-xgcc40-mt-1_38.a
-rwxr-xr-x  1 root  wheel    368480 14 Apr 18:36  
libboost_program_options-xgcc40-mt-1_38.dylib
lrwxr-xr-x  1 root  wheel        41 14 Apr 18:50  
libboost_program_options-xgcc40-mt.a -> libboost_program_options- 
xgcc40-mt-1_38.a
lrwxr-xr-x  1 root  wheel        45 14 Apr 18:42  
libboost_program_options-xgcc40-mt.dylib -> libboost_program_options- 
xgcc40-mt-1_38.dylib

Silly-iMac:lib Will$ pwd
/usr/local/lib
Silly-iMac:lib Will$ ls
libboost_date_time-xgcc40-mt-1_38.a			libboost_math_tr1l-xgcc40- 
mt.a				libboost_unit_test_framework-xgcc40-mt.a
libboost_date_time-xgcc40-mt-1_38.dylib			libboost_math_tr1l-xgcc40- 
mt.dylib			libboost_unit_test_framework-xgcc40-mt.dylib
libboost_date_time-xgcc40-mt.a				libboost_prg_exec_monitor-xgcc40- 
mt-1_38.a		libboost_wave-xgcc40-mt-1_38.a
libboost_date_time-xgcc40-mt.dylib			libboost_prg_exec_monitor-xgcc40- 
mt-1_38.dylib		libboost_wave-xgcc40-mt-1_38.dylib
libboost_filesystem-xgcc40-mt-1_38.a			libboost_prg_exec_monitor- 
xgcc40-mt.a			libboost_wave-xgcc40-mt.a
libboost_filesystem-xgcc40-mt-1_38.dylib		libboost_prg_exec_monitor- 
xgcc40-mt.dylib		libboost_wave-xgcc40-mt.dylib
libboost_filesystem-xgcc40-mt.a				libboost_program_options-xgcc40- 
mt-1_38.a		libboost_wserialization-xgcc40-mt-1_38.a
libboost_filesystem-xgcc40-mt.dylib			libboost_program_options-xgcc40- 
mt-1_38.dylib		libboost_wserialization-xgcc40-mt-1_38.dylib
libboost_graph-xgcc40-mt-1_38.a				libboost_program_options-xgcc40- 
mt.a			libboost_wserialization-xgcc40-mt.a
libboost_graph-xgcc40-mt-1_38.dylib			libboost_program_options-xgcc40- 
mt.dylib		libboost_wserialization-xgcc40-mt.dylib
libboost_graph-xgcc40-mt.a				libboost_python-xgcc40-mt-1_38.a			 
libfuse.0.dylib
libboost_graph-xgcc40-mt.dylib				libboost_python-xgcc40- 
mt-1_38.dylib			libfuse.2.7.3.dylib
libboost_iostreams-xgcc40-mt-1_38.a			libboost_python-xgcc40-mt.a				 
libfuse.2.dylib
libboost_iostreams-xgcc40-mt-1_38.dylib			libboost_python-xgcc40- 
mt.dylib				libfuse.dylib
libboost_iostreams-xgcc40-mt.a				libboost_regex-xgcc40-mt-1_38.a				 
libfuse.la
libboost_iostreams-xgcc40-mt.dylib			libboost_regex-xgcc40- 
mt-1_38.dylib			libfuse_ino64.2.7.3.dylib
libboost_math_c99-xgcc40-mt-1_38.a			libboost_regex-xgcc40-mt.a				 
libfuse_ino64.2.dylib
libboost_math_c99-xgcc40-mt-1_38.dylib			libboost_regex-xgcc40- 
mt.dylib				libfuse_ino64.dylib
libboost_math_c99-xgcc40-mt.a				libboost_serialization-xgcc40- 
mt-1_38.a			libfuse_ino64.la
libboost_math_c99-xgcc40-mt.dylib			libboost_serialization-xgcc40- 
mt-1_38.dylib		libprl_sdk.3.0.0.dylib
libboost_math_c99f-xgcc40-mt-1_38.a			libboost_serialization-xgcc40- 
mt.a			libprl_sdk.3.0.dylib
libboost_math_c99f-xgcc40-mt-1_38.dylib			libboost_serialization- 
xgcc40-mt.dylib			libprl_sdk.3.dylib
libboost_math_c99f-xgcc40-mt.a				libboost_signals-xgcc40-mt-1_38.a			 
libprl_sdk.dylib
libboost_math_c99f-xgcc40-mt.dylib			libboost_signals-xgcc40- 
mt-1_38.dylib			libusb-0.1.4.4.4.dylib
libboost_math_c99l-xgcc40-mt-1_38.a			libboost_signals-xgcc40-mt.a				 
libusb-0.1.4.4.5.dylib
libboost_math_c99l-xgcc40-mt-1_38.dylib			libboost_signals-xgcc40- 
mt.dylib			libusb-0.1.4.dylib
libboost_math_c99l-xgcc40-mt.a				libboost_system-xgcc40-mt-1_38.a			 
libusb.a
libboost_math_c99l-xgcc40-mt.dylib			libboost_system-xgcc40- 
mt-1_38.dylib			libusb.dylib
libboost_math_tr1-xgcc40-mt-1_38.a			libboost_system-xgcc40-mt.a				 
libusb.la
libboost_math_tr1-xgcc40-mt-1_38.dylib			libboost_system-xgcc40- 
mt.dylib				libusbpp-0.1.4.4.4.dylib
libboost_math_tr1-xgcc40-mt.a				libboost_test_exec_monitor-xgcc40- 
mt-1_38.a		libusbpp-0.1.4.4.5.dylib
libboost_math_tr1-xgcc40-mt.dylib			libboost_test_exec_monitor-xgcc40- 
mt.a			libusbpp-0.1.4.dylib
libboost_math_tr1f-xgcc40-mt-1_38.a			libboost_thread-xgcc40- 
mt-1_38.a			libusbpp.a
libboost_math_tr1f-xgcc40-mt-1_38.dylib			libboost_thread-xgcc40- 
mt-1_38.dylib			libusbpp.dylib
libboost_math_tr1f-xgcc40-mt.a				libboost_thread-xgcc40-mt.a				 
libusbpp.la
libboost_math_tr1f-xgcc40-mt.dylib			libboost_thread-xgcc40- 
mt.dylib				pkgconfig
libboost_math_tr1l-xgcc40-mt-1_38.a			libboost_unit_test_framework- 
xgcc40-mt-1_38.a
libboost_math_tr1l-xgcc40-mt-1_38.dylib			libboost_unit_test_framework- 
xgcc40-mt-1_38.dylib

On 16 Apr 2009, at 15:17, Michael Hofmann wrote:

>> linking ../../bin/debug/igotu2gpx.app/Contents/MacOS/igotu2gpx
>> ld: library not found for -lboost_program_options-mt
> Hmm, the boost program options library consists of headers
> (in /usr/local/include/boost...), but also a library.
>
> So let's figure out the name of the library on Mac OS X and where it  
> is.
> Can you give me a ls of /usr/local/lib/*boost*? The libraries should  
> be
> called sth. like libboost_program_options-....dylib.
>
> 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.