All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5102] New: qt package moc, uic, rcc read from wrong place
Date: Sat, 14 Apr 2012 11:54:23 +0000 (UTC)	[thread overview]
Message-ID: <bug-5102-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=5102

           Summary: qt package moc, uic, rcc read from wrong place
           Product: buildroot
           Version: 2012.02
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: mehsamadi at yahoo.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


when cross compiling qt, building application with cross compiled qmake creates
a wrong location for moc, uic, and rcc in Makefile.
qmake expect finding moc in host/usr/arm-unknown-linux-uclibcgnueabi/usr/bin/
while the actual files are located in the host/usr/bin/

I compiled this with 2011.11 and it was ok. I guess this is something that is
introduced in 2012.02.

Thank you
sorry for bad english. :-)

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2012-04-14 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-14 11:54 bugzilla at busybox.net [this message]
2012-04-14 16:47 ` [Buildroot] [Bug 5102] qt package moc, uic, rcc read from wrong place bugzilla at busybox.net
2012-04-15  5:32 ` bugzilla at busybox.net
2012-04-25 15:40 ` bugzilla at busybox.net
2012-04-28 19:49 ` bugzilla at busybox.net
2012-04-28 20:24 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-5102-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.