From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Configuring QMake project issue
Date: Tue, 25 Oct 2011 10:02:17 +0200 [thread overview]
Message-ID: <20111025100217.4be45d40@skate> (raw)
In-Reply-To: <4EA66561.3000002@visionsystems.de>
Le Tue, 25 Oct 2011 09:29:37 +0200,
Yegor Yefremov <yegor_sub1@visionsystems.de> a ?crit :
> I followed your instructions on how to integrate own small project
> into BR. This is Qt project based on a *.pro file. My *.mk looks like
> this:
>
> VSGUITEST_VERSION = 1.0
> VSGUITEST_SITE_METHOD = local
>
> define VSGUITEST_EXTRACT_CMDS
> cp -a $(TOPDIR)/package/vscom/vsguitest/src/* $(@D)/
> endef
If you use _SITE_METHOD = local, then you don't need the custom
_EXTRACT_CMDS.
Just do:
_SITE_METHOD = local
_SITE = $(TOPDIR)/package/vscom/vsguitest/src/
> define VSGUITEST_CONFIGURE_CMDS
> $(QT_QMAKE) $(@D)/vsguitest.pro
> endef
This should be:
(cd $(@D); $(QT_QMAKE) vsguitest.pro)
otherwise:
> My problem is, that after source code copy qmake generates Makefile
> directly in BR's root and overwrites the main Makefile. With
> QSerialDevice I haven't experienced such problems. What can I do
> about this?
This is because in your _CONFIGURE_CMDS, qmake gets executed inside the
Buildroot top directory.
> P.S. what about adding QMake project type in addition to CMake type?
So far, we don't have any package using Qmake inside the tree, which is
why we don't have a package infrastructure for them. So either we could
document how to create Qmake package (which is quite easy), or we could
add a package infrastructure for them.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-10-25 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 7:29 [Buildroot] Configuring QMake project issue Yegor Yefremov
2011-10-25 8:02 ` Thomas Petazzoni [this message]
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=20111025100217.4be45d40@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox