Re: problem after updating gui

[Ben Abbott]

On Feb 1, 2012, at 2:32 PM, Ben Abbott wrote:

> On Feb 1, 2012, at 1:57 PM, Robinson, Melvin D wrote:
> 
>> On 2/1/12 9:10 AM, "Ben Abbott" <address@hidden> wrote:
>> 
>>> On Feb 1, 2012, at 8:37 AM, Robinson, Melvin D wrote:
>>> 
>>>> From: Jacob Dawid <address@hidden>
>>>> 
>>>>> Hello everyone!
>>>>> 
>>>>> What I did is I simplified the build process and added
>>>>> subrepositories, instead of scripts that fetch the git repositories.
>>>>> Building the gui should now be simple as navigating into the
>>>>> gui/-directory and typing:
>>>>> 
>>>>> qmake
>>>>> make
>>>>> 
>>>>> You probably need to clone a fresh repository.
>>>> 
>>>> I think that I've narrowed down the problem.  The include options are a
>>>> directory that I have recently deleted:
>>>> 
>>>> -I/opt/local/include/octave-3.5.91+/octave/..
>>>> -I/opt/local/include/octave-3.5.91+/octave
>>>> 
>>>> How would the build process pick up this old directory and how can I
>>>> set it to the right path?
>>> 
>>> I assume you still have a recent version of Octave installed ? I think
>>> that is necessary.
>>> 
>>> Ben
>> 
>> Just to make sure I tried by rebuilding everything from scratch.  For some
>> reason the GUI build calls out the non-existent directory associated with
>> 3.5.91.  How could it possibly pick up this directory?  It is not in any
>> of the environment variables on my system.
>> 
>> The problem lies with an entry in the Makefile in the src/ directory:
>> CXXFLAGS      = -pipe -I/opt/local/include/octave-3.5.91+/octave/..
>> -I/opt/local/include/octave-3.5.91+/octave -O2 -arch x86_64 -Xarch_x86_64
>> -mmacosx-version-min=10.7 -Wall -W $(DEFINES)
>> 
>> My question is how the build process chooses CXXFLAGS and why does it pick
>> up something different from qterminal and qirc  
> 
> My understanding is that building the gui part is independent of the rest of 
> Octave.
> 
> The makefile in gui/src is generated by qmake, not by ./configure.
> 
> The qmake process calls octave-config to figure out these things. You can get 
> an idea of what is done by looking at gui/src/src.pro.
> 
> My CXXFLAGS in gui/src/Makefile is below. 
> 
> CXXFLAGS = -pipe -I/opt/local/include/octave-3.6.0-rc1/octave/.. 
> -I/opt/local/include/octave-3.6.0-rc1/octave -g -gdwarf-2 -Wall -W $(DEFINES)
> 
> This is pointing at to the last Octave I installed.
> 
> If I understand correctly, to run the latest sources using the gui (1) build 
> octave, (2) install octave (which installs octave-config as well), and then 
> (3) build the gui.
> 
> Ben

I overlooked that src.pro also includes a call to "mkoctfile -p INCFLAGS". I 
think this is how qmake is obtaining the parts below.

        -I/opt/local/include/octave-3.5.91+/octave/..
        -I/opt/local/include/octave-3.5.91+/octave

It appears that the mkoctfile from your earlier installation is still present.

Ben