← Back to team overview

igotu2gpx team mailing list archive

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

 

Progress - clear advice appreciated

macx:BOOSTINCLUDEDIR = $${BOOSTROOT}/usr/local/include/boost-1_38 was  
added to localconfig.pri resulting in a qmake output as follows:

Silly-iMac:igotu2gpx-0.2 Will$ qmake
Project MESSAGE: ------------------------------------
Project MESSAGE: Required dependencies:
Project MESSAGE: ------------------------------------
Project MESSAGE: Looking for boost-po           : yes
Project MESSAGE: Looking for libusb             : yes
Project MESSAGE: ------------------------------------
Project MESSAGE: Suggested dependencies:
Project MESSAGE: ------------------------------------
Project MESSAGE: Looking for chrpath            : no
Project MESSAGE: ------------------------------------
Project MESSAGE: Additional features:
Project MESSAGE: ------------------------------------
Project MESSAGE: ------------------------------------
WARNING: Ignored (not found) '/Users/Will/.Trash/igotu2gpx-0.2  
23-47-44/src/igotu/igotu.xcodeproj'
WARNING: Ignored (not found) '/Users/Will/.Trash/igotu2gpx-0.2  
23-47-44/src/igotu2gpx/igotu2gpx.xcodeproj'

I've still not been able to find chrpath and am unsure what to do next  
as there's no makefile after te above step. I could send the output  
from qmake -d if that would help.

Will

On 15 Apr 2009, at 22:30, Michael Hofmann wrote:

>> Thanks for looking into this but I wonder if my issues might be more
>> basic than this...?
> No, this is actually going in the right direction :-).
>
>> How would you suggest actually making this? The docs say qmake/make/
>> make install - I guess that using the command line approach should
>> make this simpler so I tried qmake in the project root dir and got  
>> the
>> following:
>>
>> Silly-iMac:igotu2gpx-0.2 Will$ qmake
>> Project MESSAGE: ------------------------------------
>> Project MESSAGE: Required dependencies:
>> Project MESSAGE: ------------------------------------
>> Project MESSAGE: Looking for boost-po           : no
>> Project ERROR: Please install the necessary (devel) packages for  
>> boost-
>> po!
>>
>> So - any idea how/where I should specify the boost rootdir?
> To change the default search paths that the build system uses, do the
> following:
> * copy the file localconfig-template.pri to localconfig.pri
> * uncomment and change the necessary defines so that they match your
> system, e.g. change macx:BOOSTINCLUDEDIR to the boost include  
> directory
> (it needs to contain a subdir named boost/program_options). To look  
> what
> the build system is doing, look into clebs/. For each of the
> dependencies, there is a file with the same name in clebs/*/*.pri.
>
> 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