new-sdk: west tool: configure standalone project using imported west

[tq-delimayuki]

Hi I didn't want to open an issue about this, because it could be that I'm just not getting how to do it.

Following:

I imported the new SDK on driver D: but want to have my standalone project for my custom Board in driver C:.

Now like in zephyr I created a folder .west with a file config:

`
[manifest]
path = D:/ThirdParty/nxp/mcuxpresso-sdk/manifests
file = west.yml

[commands]
allow_extensions = true
`

Still if I use west -h

`
The Zephyr RTOS meta-tool.

optional arguments:
-h, --help get help for west or a command
-z ZEPHYR_BASE, --zephyr-base ZEPHYR_BASE
Override the Zephyr base directory. The default is
the manifest project with path "zephyr".
-v, --verbose Display verbose output. May be given multiple times
to increase verbosity.
-q, --quiet Display less verbose output. May be given multiple
times to decrease verbosity.
-V, --version print the program version and exit

built-in commands for managing git repositories:
init: create a west workspace
update: update projects described in west manifest
list: print information about projects
manifest: manage the west manifest
compare: compare project status against the manifest
diff: "git diff" for one or more projects
status: "git status" for one or more projects
forall: run a command in one or more local projects
grep: run grep or a grep-like tool in one or more local
projects

other built-in commands:
help: get help for west or a command
config: get or set config file values
topdir: print the top level directory of the workspace

Run "west help " for help on each .
`

So the config is not recognizing the root path of the mcuxsdk project. Is there something that I'm missing?

Btw. with Zephyr the same procedure works for own project.

Regards and thanks!

[mcuxsusan]

Hi @tq-delimayuki, I see you already raised for nxp-mcuxpresso/mcuxsdk-manifests#1 in our new SDK project, this issue should be related. You could move to the new issue for further discussion.

We have stopped maintaining this old SDK project, thus any contribution should go to our new SDK project mcuxsdk, appreciate for your understanding!