Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32

Forum List Topic List

[ prev topic ]  

How to run source *.sh before build at SW4STM32

Posted by starlin2 on 2017-07-13 08:36

Dear Sir:
I had a project, base on zephyr RTOS,
Before build, I need do “source init-build.sh”
Then what do I do if I using SW4STM32?

Reads: 9941
Link
Posted by tang on 2017-07-13 09:30

Hi,

You can try replacing the pre-build steps in your project properties > C/C++ Build > Settings > Build Steps.

Regards,
Kevin.

Link
Posted by starlin2 on 2017-07-13 10:42

I can see Build Steps, if I import ST sample code by “Import > General > Existing Projects into Workspace” form STM32Cube_FW_L4_V1.8.0.

But if I import my project by using “Import > C/C++ > Existing Code as Makefile Project” then I can’t see Build Steps....><
The Settings only have “Binary Parsers” and “Error Parsers”, didn’t have “Build Steps”
how come??

Link
Posted by tang on 2017-07-17 10:20

“Import > General > Existing Projects into Workspace” imports a project without modifying the settings. The Makefile is automatically generated when building the project (pre-build and post-build are added to the generated makefile)

“Import > C/C++ > Existing Code as Makefile Project” creates a new Eclipse generic makefile project (and not System Workbench project). It means that you provide your own Makefile so you can modify it.
By the way, If you really wanted to import a Makefile project, my advise to create a new project then copy/paste your sources into it.
New > C Project, select Makefile project and Ac6 STM32 MCU GCC toolchain.

Link

Posted by dautrevaux on 2017-07-13 10:31 France

Hi,

If you really need to source this script (to set environment variables for example) then there are two possibilities:

  1. set the environment variables before starting Eclipse
  2. create a small script that source your init-build.sh script, then launch make (by make “$@”) then use this script as the build tool instead of calling directly make.
    • note it will be called from the “Debug” directory, so you could reference it as ../make.sh if you place it in the root directory of your project.


Best regards,

Bernard (Ac6)

Link