"Cufi, Carles" <Carles.Cufi@...> writes: I don't think that's the issue here. Jaemin can run west, but west can't import pykwalify. That's not a PATH (environment variable) issue, but a sys.

Allen Curtis <allen@...> writes: What distro are you using? Did you try running python3 -m site as described below to debug?

Hi Jaemin, Allen, "Allen Curtis via Lists.Zephyrproject.Org" <allen=criticalsoftwaresolutions.com@...> writes: Hmm, that shouldn't be needed if the Python dependencies were install

Hi Paul, These are important questions, and I'm glad you've asked them. I will try to provide a fair amount of detail along with short answers. Paul Sokolovsky <paul.sokolovsky@...> writes: Sho

Joris Offouga <offougajoris@...> writes: Great! Glad it helped.

"Joris Offouga via Lists.Zephyrproject.Org" <offougajoris=gmail.com@...> writes: Just a couple of notes: - the board doesn't have to be specified twice - the default source directo

Hi, " via Lists.Zephyrproject.Org" <tcpipchip=hotmail.com@...> writes: It looks like Carles helped you out on Slack and your question was answered. (Posting this just to track the

"Youse, Charles via Lists.Zephyrproject.Org" <charles.youse=intel.com@...> writes: I agree that it is a serious bug (see "high impact", below), and again, I'm sorry for the lack of

"Youse, Charles" <charles.youse@...> writes: Of course. We have a process in place. It failed here due to lack of coverage, which unfortunate oversight and I'm very sorry for it, especially for

Marti Bolivar <marti.bolivar@...> writes: I was requested to add a link to the bug: https://github.com/zephyrproject-rtos/west/issues/298 It won't cause data loss, but it will cause west upd

Hi, West v0.6.1 contains a high impact bug in the "west update" behavior that is fixed in v0.6.2. Users of v0.6.0 and earlier are not affected. If you are using west v0.6.1 (check with west --version)

"Alberto Escolar Piedras (ALPI)" <ALPI@...> writes: You're right, of course. I looked at the output itself without seeing the "warning" prefix. This is building and running fine (apart from the

#samples #adc

I can't reproduce this exact issue, but I can confirm that with ZEPHYR_TOOLCHAIN_VARIANT=zephyr and ZEPHYR_TOOLCHAIN_VARIANT=host, I get a build error following along with the getting started guide: [

#samples #adc

"David Leach via Lists.Zephyrproject.Org" <david.leach=nxp.com@...> writes: FTR, I rarely have ZEPHYR_BASE set in my parent environment because I only need it to run sanitycheck, w

Hi, I’ve just tagged RC3. This includes some bug fixes and related features: An optional “repo-path” project attribute to allow override the project’s “name” when forming the fetch URL, added to allow

I forgot to add: it would be nice if any issues could be reported via the west bug tracker (https://github.com/zephyrproject-rtos/west/issues) rather than email, if possible. Thanks again.

Hi, West version 0.6.0rc1 has been tagged. Release notes are in this pull request: https://github.com/zephyrproject-rtos/zephyr/pull/17714 Testing and feedback are welcome; I’d like this to be the min

Hi, Is anybody using the HEX_FILES_TO_MERGE build system property? It was originally added by Nordic, but has since been removed from our downstream Zephyr distribution, and I personally think it woul

Hi, "hotkernel via Lists.Zephyrproject.Org" <hotkernel=163.com@...> writes: It doesn't matter how you get the source code; west will work too. The important thing is that you need

#gettingstartedguide