All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] General questions
Date: Mon, 15 Sep 2014 23:27:14 +0200	[thread overview]
Message-ID: <541759B2.8050500@mind.be> (raw)
In-Reply-To: <CAAXf6LXwNYVB6VzNT=FNt1DOA=uowhA6DEB-9-8JoAjoiO_m2Q@mail.gmail.com>

On 09/09/14 12:04, Thomas De Schampheleire wrote:
> Hi Sylvain,
> 
> On Tue, Sep 9, 2014 at 11:20 AM, Sylvain LG <forum@sylvainlegourr.com> wrote:
>> Hi,
>>
>> I develop some projects with Qt and run them on ARM embedded systems. OS is
>> built by Buildroot.
>>
>> Since Qt 5.3.1 and QtCreator 3, GDB must support Python scripting.
>>
>> ?The selected build of GDB does not support Python scripting it cannot be
>> used in Qt Creator?
>>
>>
>> I have to recompile gdb with these options:
>>
>> ./configure --prefix /usr/local/gdb-python2 --with-python
>>
>> What is the right way to achieve this?
> 
> In package/gdb/gdb.mk, you will have to update the HOST_GDB_CONF_OPT variable.
> You shouldn't add --prefix, but only the --with-python flag.
> Since not everyone will want this python dependency, you probably
> should add an option for this. This is done in
> package/gdb/Config.in.host
> 
> I suggest to have a look at the recent TUI support that was added in
> Buildroot for GDB, I think that the way to handle python support is
> very similar, except that instead of host-ncurses as dependency,
> you'll add host-python.

 I'm not sure that we want our own-build host-python... You may want to use some
of the system's python packages, for example. So I think it is better to drop
the host-python dependency, and use the system python instead. (Note that python
is a dependency of buildroot.)


> Additionally, from the Config.in.host file, you'll have to select
> BR2_PACKAGE_PYTHON. Due to this, you'll also need to propagate the

 Huh? We are talking about the host-gdb here, so why do you need a target python?


 One more thing: on AVR we still use gdb 6.7 which doesn't have python support,
so something must be done to catch that.


 Regards,
 Arnout

> dependencies of python (seen in package/python/Config.in) as
> dependencies of your new gdb-python-support option.
> Have a look at http://buildroot.uclibc.org/downloads/manual/manual.html#_literal_config_in_literal_file
> for this part.

[snip]


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-09-15 21:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09  9:20 [Buildroot] General questions Sylvain LG
2014-09-09 10:04 ` Thomas De Schampheleire
2014-09-15 21:27   ` Arnout Vandecappelle [this message]
2014-09-16  6:27     ` Thomas De Schampheleire
2014-09-16 20:14 ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2024-06-20 22:10 [Buildroot] general questions Patricia Holden
2024-06-21 20:44 ` Arnout Vandecappelle via buildroot
2024-06-23 20:29   ` Patricia Holden

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=541759B2.8050500@mind.be \
    --to=arnout@mind.be \
    --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.