CLI can't build code

RE: CLI can't build code

PrinceKuo — Tue, 26 Apr 2022 03:33:35 GMT

Hi Edvin,

Thanks for your passion and helping. 🙂

I have a good news that's I fixing the issue through modifying cmake file to assign SDK's Python while building. I try to record what I did and hope that can help who has the same issue.

As my build server environment, SDK's Python location is "/opt/nordic/ncs/v1.8.0/toolchain/opt/python@3.9/bin/python3.9"

step 1. Launch cmake file that response for detecting Python location

vim $(Nordic_SDK_folder)/zephyr/cmake

step 2. Assign target Python location in cmake file

set(PYTHON_PREFER_EXECUTABLE "/opt/nordic/ncs/v1.8.0/toolchain/opt/python@3.9/bin/python3.9")

Now I can build code through CLI.

Thanks,

Prince

RE: CLI can't build code

Edvin — Fri, 22 Apr 2022 08:24:24 GMT

Hello Prince,

I talked to one of the developers of nRF Connect for Visual Studio Code. He told me you could try this:

"python3 -m west build --build-dir ..."

And if that doesn't work, then:

"/full/path/to/python -m west build --build-dir ..."

where you replace /full/path/to/python with the full path to the python executable that you want to use, so the one inside the toolchain folder.

Best regards,

Edvin

RE: CLI can't build code

PrinceKuo — Fri, 22 Apr 2022 07:45:36 GMT

Hi Edvin,

I test 'alias', the python version really update.

But cmake get python location still wrong, so build process still fail...Orz

Could you have any idea? 🙂

It's very strange and hard, appreciate for your great supporting.

BR,

Prince

RE: CLI can't build code

Edvin — Fri, 22 Apr 2022 06:47:25 GMT

Oh. I thought it was the mac that you were testing on next to your build server. To be honest, I am not sure if you are actually using two computers, or if the build server (which is a mac) is the only computer you are using.

[quote user="PKuo"]Could you share me how to let CLI reference to SDK's python folder?[/quote]

I see that you are asking for this in every post, but I don't know a simple answer to this. Did you test the stackoverflow link in my initial reply? I don't have a mac to test this on, but you need to find some way that your command line sees the version that you want to use instead of the other (wrong) version. This doesn't need to be permanent, but when you are building, the command line (terminal) needs to see that version. I don't know how to do that. You need to do a bit of research.

I tried to do some research, and it ended up in the link in my first reply. The reply that discusses using the "alias" in the terminal.

BR,

Edvin

RE: CLI can't build code

PrinceKuo — Fri, 22 Apr 2022 01:17:06 GMT

Yap, previous post that is build server's screenshot.

So in my build server already had correctly python folder and VS Code can reference it.

But CLI will reference to system's python not SDK's.

Could you share me how to let CLI reference to SDK's python folder?

Thanks,

Prince

RE: CLI can't build code

Edvin — Thu, 21 Apr 2022 10:59:02 GMT

Hello Prince,

I believe the yaml is missing because python can't find it. So solving the python issue should solve the yaml issue.

On your build server, do you have the folder and executable (correct version of) python inside the toolchain folder?

BR,

Edvin

RE: CLI can't build code

PrinceKuo — Thu, 21 Apr 2022 10:00:33 GMT

Hi Edvin,

Thanks for your information, but I still your support...Orz

Base on build fail message No module named 'yaml' we know cmake can't find 'yaml' module while building.

  File "/opt/nordic/ncs/v1.8.0/zephyr/scripts/dts/gen_defines.py", line 33, in <module>
    from devicetree import edtlib
  File "/opt/nordic/ncs/v1.8.0/zephyr/scripts/dts/python-devicetree/src/devicetree/edtlib.py", line 77, in <module>
    import yaml
ModuleNotFoundError: No module named 'yaml'
CMake Error at /opt/nordic/ncs/v1.8.0/zephyr/cmake/dts.cmake:251 (message):
  gen_defines.py failed with return code: 1
Call Stack (most recent call first):
  /opt/nordic/ncs/v1.8.0/zephyr/cmake/app/boilerplate.cmake:545 (include)
  /opt/nordic/ncs/v1.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  /opt/nordic/ncs/v1.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
  CMakeLists.txt:44 (find_package)

I search 'yaml' on my Mac and find it location under Nordic SDK.

So do you know how to let cmake detecting python location to Nordic SDK(/opt/nordic/ncs/v1.8.0/toolchain/opt/python@3.9/bin/python3.9.)?

Thanks,

Prince

RE: CLI can't build code

Edvin — Wed, 20 Apr 2022 12:51:00 GMT

The answer to your question on "why the sample doesn't build" looks like it is that you have the wrong version of python. If you are telling me that you can't update the python version on the computer that you are building on, then I don't know how to fix it.

I know that in Windows you can use the env.cmd file to set temporary workspaces/toolchains, but I don't know how to do that on a Mac. I also don't have a mac that I can experiment on.

Perhaps this discussion can give some clues on how to set a specific python version:
https://gitlab.kitware.com/cmake/cmake/-/issues/19492

Best regards,

Edvin

RE: CLI can't build code

PrinceKuo — Wed, 20 Apr 2022 09:23:02 GMT

Hi Edvin,

Thanks for your replying.

But my build server (Mac mini) without "/opt/nordic/ncs/v1.8.0/toolchain/cmd/" folder.

Because toolchain can't complement install SDK in my build server, so I almost download all files by manual.

BTW, do you know how to setup cmake environment variable PYTHON_EXECUTABLE?

Seem like this environment variable let build fail.

Build fail path:

Build success path:

Regards,

Prince

RE: CLI can't build code

Edvin — Wed, 20 Apr 2022 07:42:29 GMT

Hello Prince,

I don't know how you installed NCS, but since you are able to build it using nRF Connect for VS Code, you have the proper toolchain installed on the computer, at least.

In Windows, you would call this file from the command line, which will set up all the tools you need in that command line window, without changing anything externally.

/opt/nordic/ncs/v1.8.0/toolchain/cmd/env.cmd

But I am not familiar with Mac or linux. Perhaps you can try something like this to temporary change the python path:

https://stackoverflow.com/a/43354441

Best regards,

Edvin