Right, but only because the implementation was done in such way. Frankly, if I used ST's libraries, it would have saved me a lot of time during porting. Instead, I followed the example set by

if you think doing this # make ZEPHYR_BASE=/path/to/source/tree BOARD=blah blah hundreds of times per day is more convenient than doing 'source zephyr-env.sh’ once a day per shell then we have a

Certainly, ZEPHYR_BASE is tree-specific (so could be the other in certain cases, but uncommon). I also do set it manually (in fact, as I said somewhere, I feed it to make's command line) This is the

I use it instead of polluting my .bashrc with zephyr stuff. Basically, your two export lines above go in there. I personally like that zephyr-env.sh exists: you just have to source it and your

I don't believe this is the case. You do have to set ZEPHYR_GCC_VARIANT and ZEPHYR_SDK_INSTALL_DIR. I put them in my .bashrc: export ZEPHYR_GCC_VARIANT=zephyr export

to avoid those issues I usually run make ZEPHYR_BASE=DIR <blah>, which is kind of more verbose, but gets the trick done. However, I hear your call. I think it's worthwhile to consider the posibility

Hi Inaky,

Hi Maciek,

Hello All https://jira.zephyrproject.org/browse/ZEP-211 has been entered to track a proposal to remove zephyr-env.sh. <<from the ticket>> Currently we require the user to source the zephyr-env.sh

<Carles.Cufi(a)nordicsemi.no> wrote: What I meant is that you keep the {S,M}DK externally and just configure a path to it inside Kconfig. You can add a config entry like CONFIG_STM32F1_STDLIB_PATH.

NEW JIRA items within last 24 hours: 1 [ZEP-208] Zephyr's cc2520 driver (together with Zephyr's IP stack) does not handle fragmentation of packets properly

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/1544 : qmsi: pinmux: use built-in qmsi driver - https://gerrit.zephyrproject.org/r/1546 : Bluetooth: Kconfig: Split debug selection

Guys, Thoughts or answers on that one: Tomasz

Hi Luiz, Giving the pointer on current sys_timer instead you could: remove that pointer, and up to user to use CONTAINER_OF() if he wants to. (yes I am reusing ideas from Johan ;) ) Are you ever

I fully agree with your plan of implementing the IoT protocols but have a few questions related to the planned implementation. What is the minimal SoC required for the implementation of let’s

[RFC] Zephyr IoT Protocols Problem definition Currently, Zephyr does not support any machine-to-machine protocol  (M2M). These protocols were defined for inter-communication between  devices or

Hi Anas,

Hi Maciek,

Hi there,

Thanks Anas. This documentation was what I was missing. As regards to building with Yocto, it was not necessary use case. The use case was just a quick way to build & rebuild the zephyr kernel with