Issues with configuring BSP with waf

Fri Mar 12 11:16:58 UTC 2021

hello Ida,
a few things id like to mention is that after you installed rtems for your
specific bsp and started to write you application you need to also install
waf in you application workspace per:
https://docs.rtems.org/branches/master/user/start/app.html
it tells you to install waf as shown below:

Download the Waf build system and set it to executable:

curl https://waf.io/waf-2.0.19 > waf
chmod +x waf

Initialise a new Git repository:

git init

Add RTEMS Waf support as a Git sub-module and initialise it:

git submodule add git://git.rtems.org/rtems_waf.git rtems_waf
have in mind to pass your rtems installation prefix while running waf
the stuff I mentioned above is for the master branch of rtems.
In the second part of your question which you said that you switched to
branch 5 and it didn't find waf is because the rtems 5 branch simply
doesn't support waf (well you could add it yourself but why go through the
fuss?) and automake is used for building

On Fri, Mar 12, 2021 at 9:25 AM Ida Delphine <idadelm at gmail.com> wrote:

> Hello,
> Please I need some help. Following the GSoC getting started guide(
> https://docs.rtems.org/branches/master/user/start/gsoc.html),everything
> went well to the point I had to do an offline download. I used this command
> ../source-builder/sb-set-builder --source-only-download 5/rtems-sparc
> Seems like there was a mismatch. I got this error:
> b-set-builder --source-only-download 5/rtems-sparc
> RTEMS Source Builder - Set Builder, 6 (5e449fb5c2cb)
> Build Set: 5/rtems-sparc
> error: no build set file found: 5/rtems-sparc.bset
> Build Set: Time 0:00:00.000205
> Build FAILED
> I then replaced 5/rtems in the command with 6/rtems and everything worked.
> I was able to install the suite, build the board support package, and test
> my BSP though along the way I had to replace "5" with "6" in certain
> commands. Everything went well until I wanted to prove I can work on RTEMS.
> I followed the instructions to create my hello application and added the
> necessary .c files. The problem was when I tried configuring this
> application using waf with the command:
>
> ./waf configure --rtems=$HOME/quick-start/rtems/5 --rtems-bsp=sparc/erc32
>
> I got this error:
> Setting top to                           :
> /home/idadel/quick-start/app/hello
> Setting out to                           :
> /home/idadel/quick-start/app/hello/build
> RTEMS path is not valid, "/home/idadel/quick-start/rtems/5/share/rtems5"
> not found.
> (complete log in /home/idadel/quick-start/app/hello/build/config.log)
> I thought I showld startover but and work with rtems.git/5 instead of
> rtems.git/master. Same with rsb. So I got the sources and did a "git
> checkout"  from the master to the "5" branch. Everything went well with me
> not not having to change any "5" to "6" in some commands. I didn't make it
> as far as testing my BSP. I had issues with configuring my BSP with the
> command:
>
> ./waf configure --rtems=$HOME/quick-start/rtems/5 --rtems-bsp=sparc/erc32
>
> I got this:
> bash: ./waf: No such file or directory
> I'm confused and don't know what I missed or where I went wrong.
>
> Ida.
>
>
>
>
> On Thu, Mar 11, 2021 at 6:03 PM Ida Delphine <idadelm at gmail.com> wrote:
>
>> Okay. Thank you :)
>>
>> On Thu, 11 Mar 2021, 5:57 pm Gedare Bloom, <gedare at rtems.org> wrote:
>>
>>> On Thu, Mar 11, 2021 at 9:48 AM Ida Delphine <idadelm at gmail.com> wrote:
>>> >
>>> > Thank you for your response. I am not working on the rtems.git/master
>>> branch. I'm not using it because earlier I tried downloading sources with
>>> it but I got this error
>>> > error: shell macro failed:
>>> /home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c gcc
>>> -l : 2: error: no library (-l) provided
>>> > So I decided to use the other alternative(get the sources from
>>> releases)
>>> >
>>> > Since I'm a GSoC applicant should I wait till the issue at the master
>>> branch is resolved?
>>> >
>>> Yes, that issue has been resolved so please try again. Hopefully,
>>> things work a bit better. We try not to break things, but unexpected
>>> problems come up from time to time, especially based on host OS
>>> dependencies.
>>>
>>> > Cheers,
>>> > Ida.
>>> >
>>> > On Thu, Mar 11, 2021 at 4:18 PM Gedare Bloom <gedare at rtems.org> wrote:
>>> >>
>>> >> On Thu, Mar 11, 2021 at 7:33 AM Ida Delphine <idadelm at gmail.com>
>>> wrote:
>>> >> >
>>> >> > Hello everyone,
>>> >> > Was following the quick build documentation and had issues around
>>> where I have to do a manual BSP build.  In the last step of configuring the
>>> BSP, I ran this command:
>>> >> >
>>> >> > ./waf configure --prefix=$HOME/quick-start/rtems/5
>>> >> >
>>> >> Are you working on rtems.git/master branch or /5 branch? Note that you
>>> >> need to be sure to use a consistent compiler toolchain based on the
>>> >> version of RTEMS that you use.
>>> >>
>>> >> In rtems/5 branch we don't have waf support integrated yet. The
>>> >> upgrade to waf is happening currently on the master branch, which will
>>> >> eventually become the RTEMS version 6 release.
>>> >>
>>> >> For GSoC students we expect development to happen on the development
>>> >> head and not a release, so please make sure that you have the
>>> >> toolchain built from rtems-source-builder.git/master and the rtems
>>> >> source tree from rtems.git/master.
>>> >>
>>> >> > It didn't produce the expected output. I instead got:
>>> >> > bash: ./waf: No such file or directory
>>> >> > As a result I downloaded it with the command:
>>> >> > curl https://waf.io/waf-2.0.19 > waf
>>> >>
>>> >> https://git.rtems.org/rtems/tree/waf
>>> >>
>>> >> Currently, the waf-based build of rtems only supports "in tree"
>>> >> builds, which means you need to run waf from within the rtems.git/
>>> >> root of your source. This is a limitation of the waf build.
>>> >>
>>> >> FWIW, waf build improvements could also fall under GSoC effort,
>>> >> although no one has written it up as a task yet. It would be mostly
>>> >> Python.
>>> >>
>>> >> > I ran  the last command to configure the BSP again but still did
>>> not get the expected  output. I got this rather:
>>> >> > Waf: Run from a folder containing a 'wscript' file (or try -h for
>>> the generic options)
>>> >> > Please how do I fix this? What am I missing?
>>> >> > I have tried looking for solutions but to no avail.
>>> >> >
>>> >> Sometimes the solutions only exist inside other people's heads, so
>>> >> asking questions is encouraged.
>>> >>
>>> >> > Thanks,
>>> >> > Ida.
>>> >> > _______________________________________________
>>> >> > users mailing list
>>> >> > users at rtems.org
>>> >> > http://lists.rtems.org/mailman/listinfo/users
>>>
>> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20210312/d007d09e/attachment.html>