[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: isremote and unix board special handling question
From: |
Pedro Alves |
Subject: |
Re: isremote and unix board special handling question |
Date: |
Sat, 1 Dec 2018 17:09:07 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 |
On 11/30/2018 11:48 PM, Steve Ellcey wrote:
> On Thu, 2018-11-29 at 22:59 +0000, Pedro Alves wrote:
>>
>> Yeah, GDB does in its internal board files. Non-remote boards source
>> a file with this:
>>
>> ~~~~~
>> 16 # By default, DejaGnu makes the board remote unless the board
>> name
>> 17 # matches localhost. Sourcing this script from a board file
>> forces
>> 18 # the board to be NOT remote.
>> 19
>> 20 global board
>> 21 global board_info
>> 22 # Remove any target variant specifications from the name.
>> 23 set baseboard [lindex [split $board "/"] 0]
>> 24 set board_info($baseboard,isremote) 0
>> ~~~~~
>
> Just to return to my original question, I added
>
> unset_board_info isremote
>
> in front of
>
> set_board_info isremote 0
>
> and I got the behaviour I expected/wanted. I am still
> thinking about using a different target/site.exp file
> instead of a new baseboard but I haven't actually tried
> it yet.
Note that the unset_board_info/set_board_info approach won't
work if you pass down a target variant specification, like
e.g. '--target_board=yourboardname/-m32'.
That's the reason for the "Remove any target variant"... part in
the hack above.
Thanks,
Pedro Alves
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: isremote and unix board special handling question,
Pedro Alves <=