[Buildroot] General questions

[Buildroot] General questions

[Sylvain LG]

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?

Could someone give me the guideline to contribute to Buildroot?


Regards,

Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140909/fc01ef26/attachment.html>

[Buildroot] General questions

[Thomas De Schampheleire]

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.
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
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.

>
> Could someone give me the guideline to contribute to Buildroot?

In general, there is some documentation at
http://buildroot.uclibc.org/downloads/manual/manual.html#_developer_guide
Specifically for adding packages (or modifying existing packages), see
http://buildroot.uclibc.org/downloads/manual/manual.html#adding-packages
.

Best regards,
Thomas

[Buildroot] General questions

[Arnout Vandecappelle]

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

[Buildroot] General questions

[Thomas De Schampheleire]

Hi Arnout,

On Mon, Sep 15, 2014 at 11:27 PM, Arnout Vandecappelle <arnout@mind.be> wrote:
> 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?
>

Sorry, this is a mistake. I originally mistakenly wrote this mail with
target gdb/python in mind but forgot to fix this part.

Best regards,
Thomas

[Buildroot] General questions

[Thomas Petazzoni]

Dear Sylvain LG,

On Tue, 9 Sep 2014 11:20:13 +0200, Sylvain LG wrote:

> 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?
> 
> Could someone give me the guideline to contribute to Buildroot?

FWIW, I've sent a patch series at
http://lists.busybox.net/pipermail/buildroot/2014-September/106205.html
that provides Python support for both the host gdb and target gdb.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] general questions

[Patricia Holden]

[-- Attachment #1.1: Type: text/plain, Size: 177 bytes --]

Where are all buildroot patches that are available for inclusion located on
the buildroot download site?

On reporting issues, what is the "new" reporting system site?

Thanks!

[-- Attachment #1.2: Type: text/html, Size: 258 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] general questions

[Arnout Vandecappelle via buildroot]

On 21/06/2024 00:10, Patricia Holden wrote:
> Where are all buildroot patches that are available for inclusion located on the 
> buildroot download site?

  Are you referring to patchwork [1] which is mentioned on the Contribute web 
page [2] and in the manual [3]?

> On reporting issues, what is the "new" reporting system site?

  Are you referring to the issue tracker on gitlab [4] which is referred to on 
the Contribute web page [2] and in the manual [3]?


  Regards,
  Arnout

[1] https://patchwork.ozlabs.org/project/buildroot/list/
[2] https://buildroot.org/contribute.html
[3] https://nightly.buildroot.org/manual.html#community-resources
[4] https://gitlab.com/buildroot.org/buildroot/-/issues

> 
> Thanks!
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] general questions

[Patricia Holden]

[-- Attachment #1.1: Type: text/plain, Size: 1110 bytes --]

Yes and yes.  Thanks so much for the quick response.

On Fri, Jun 21, 2024 at 4:44 PM Arnout Vandecappelle <arnout@mind.be> wrote:

>
>
> On 21/06/2024 00:10, Patricia Holden wrote:
> > Where are all buildroot patches that are available for inclusion located
> on the
> > buildroot download site?
>
>   Are you referring to patchwork [1] which is mentioned on the Contribute
> web
> page [2] and in the manual [3]?
>
> > On reporting issues, what is the "new" reporting system site?
>
>   Are you referring to the issue tracker on gitlab [4] which is referred
> to on
> the Contribute web page [2] and in the manual [3]?
>
>
>   Regards,
>   Arnout
>
> [1] https://patchwork.ozlabs.org/project/buildroot/list/
> [2] https://buildroot.org/contribute.html
> [3] https://nightly.buildroot.org/manual.html#community-resources
> [4] https://gitlab.com/buildroot.org/buildroot/-/issues
>
> >
> > Thanks!
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot@buildroot.org
> > https://lists.buildroot.org/mailman/listinfo/buildroot
>

[-- Attachment #1.2: Type: text/html, Size: 2044 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot