octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MXE: qt error with native build


From: Philip Nienhuis
Subject: Re: MXE: qt error with native build
Date: Fri, 21 Jun 2013 08:18:02 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6

John D wrote:
*From:* Michael Goffioul [mailto:address@hidden
*Sent:* Thursday, June 20, 2013 5:54 PM
*To:* John D
*Cc:* Philip Nienhuis; Octave Maintainers List
*Subject:* Re: MXE: qt error with native build

On Thu, Jun 20, 2013 at 5:13 PM, John D <address@hidden
<mailto:address@hidden>> wrote:
    -----Original Message-----
    From: Philip Nienhuis [mailto:address@hidden
    John D wrote:
     >
     >
     > -----Original Message-----
     > From: Philip Nienhuis [mailto:address@hidden
    <mailto:address@hidden>]
     > Sent: Thursday, June 20, 2013 4:11 PM
     > To: John D
     > Cc: address@hidden
    <mailto:address@hidden>
     > Subject: Re: MXE: qt error with native build
     >
     > John D wrote:
     > <snip>
     >>
    X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensou
     >> r
     >> ce-src
     >> -4.8.3//projects.pro <http://projects.pro>
     >> -o Makefile -spec win32-g++
     >> "make" -w -- JOBS=1 -f Makefile
     >> make[3]: Entering directory
     >> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
     >> make[3]: *** No rule to make target `-f'. Stop.
     >> ------------------------------
     >>
     >> It does the same on mine
     >> Running just normal 'make' to create octave works fine though
     >
     > Not here:
     >
     > :
     > make[8]: Entering directory
     >
    `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src
     > /plugi
     > ns/imageformats/mng'
     >
    X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
     > ce-src
     > -4.8.3/bin/qmake
     >
    X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
     > ce-src -4.8.3/src/plugins/imageformats/mng/mng.pro <http://mng.pro>
     > -o Makefile -spec win32-g++
     > Project ERROR: Package libmng not found
     > make[8]: *** [all] Error 2
     >

:<snip>
<John D:>
     > That's from running make from the mxe-octave root directory?

    Of course.
    It wasn't obvious to me from what other subdir I should run make.

    I suppose ~/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3 ?
    (just tried - see below)

    <from your other email:>
     >
     > Have you set PKG_CONFIG_PATH to
     > `/home/Philip/mxe-octave/usr/i686-pc-mingw/lib/pkgconfig ?

    No, but after checking I'll rather set it to:
    /home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig
:
<snip>
<John D:>
    Check that mng was installed - installed-packages/libmng, and if it was:
    export /home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig
    make

    (in the /home/Philip/mxe-octave) folder and see what happens.

    Also, just for info, I created a script in tools/set_mxe_env.sh you
    can run
    as source tools/set_mxe_env.sh, that sets all the bin/lib/config
    paths that
    may help.
    I created it for compiling the octave_hg versions of code in mingw after
    having a working mxe-octave.
    It isn't much use for anything except for native mingw builds.

I only followed the discussion a little bit, but I've the impression
these specific variables should be set by the top-level Makefile.

Michael.

------------------------------------------------------------------------

They are(with the exception of PKG_CONFIG_PATH, which used to be there,
but I believe no longer is)

My script is more for use with compiling the octave directly from the
main hg repo than for compiling mxe-octave.

After properly setting PKG_CONFIG_PATH and restarting "make" in ./mxe-octave top dir, I found that the build got as far as octave itself. It stopped with "no space left on device" but that is obviously my side of things. (Good to know that this joke needs some 2.5 - 3 GB disk space all together)
Another 2-3 hour wait I suppose.....

Philip


reply via email to

[Prev in Thread] Current Thread [Next in Thread]