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 make a project with existing source code and makefile

Posted by thijs on 2016-07-19 13:19

Hey,

I am trying to make a project with existing source code includes and makefile.
The compiler automatically includes the auto generated makefile how do i change that in my own makefile?

Reads: 12264
Link
Posted by tarek bouchkati on 2016-07-19 15:03 Tunisia
Could you try to uncheck “Generate Makefile automatically” in Project Properties > C/C++ Build > Builder Settings (TAB)
Link
Posted by thijs on 2016-07-19 15:27

thanks it doesnt generate a auto make file now.
now i have the following problem:
15:39:51 **** Build of configuration Debug for project trillwekker test ****
make all
make: *** No rule to make target `all’. Stop.

i think it is because i dont have a set path or link to my make file. i dont now where i need to declare that. can you help me with that ?

Link
Posted by Guy on 2016-07-20 16:31

in the same TAB Project Properties > C/C++ Build > Builder Settings
try to inform the Build directory

Link

Posted by cbear on 2016-07-20 18:36

Hey,

I am having a similar problem and have followed the steps given. The error is still present however. It seems as if it is ignoring the directory choice.

This is the designated build directory:
C:\Users\****\Local Documents\Projects\Multi\Examples\VL6180X\RangingAndALS\SW4STM32\STM32F401RE-Nucleo

Within that folder lies all the necessary folders including the makefile and the drivers.

Despite this, I get the same “make: *** No rule to make target `all’. Stop. ” error.

Plus some additional warnings:
Invalid project path: Include path not found (C:\Users\****\Local Documents\Drivers\BSP\Components\VL6180x).

That was one of six such warnings. The path they are looking for exists in the dircetory I set, but it is obviously not taking the bait.

Any idea why it is not working? Thanks.

Link
Posted by Karel Jelinek on 2016-07-21 09:39

Hi,
I had similar problem with existing projects from ST example. The only solution for me to make it work was to place workspace directory to C:\workspace and import there the example project.
There is some BUG probably, maybe the problem raise when there is too deep subdirs structure of the projects.

Link
Posted by cbear on 2016-07-21 12:53

Hi,

I tried moving the workspace into the root directory but the “no rule to make target” error is still persisting I’m afraid. As for the thought on deep structure in the folders I don’t think they can really be much shortened than that. I tried reducing the folder structure to the smallest it can be and then put that into the root as well:

C:\RangingAndALS\

But this brings up over a hundred semantic errors:

Description Resource Path Location Type
Field ‘AddressingMode’ could not be resolved main.c /RangingAndALS_NucleoF401/src line 1004 Semantic Error

This is in addition to the original error.

Link

 

Newest Forum Posts

  1. SPI on Nucleo_STMH533RE by royjamil, 20:13
  2. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-25 07:37
  3. SPI on Nucleo_STMH533RE by royjamil, 2025-03-23 11:31
  4. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-23 09:33
  5. Configuring DMA for ADC in SW? by sam.hodgson, 2025-03-04 12:58
  6. Build a project in "release" mode by info@creosrl.it, 2025-02-20 18:12
  7. Build a project in "release" mode by info@creosrl.it, 2025-02-20 17:05
  8. Build a project in "release" mode by tang, 2025-02-20 10:36
  9. Build a project in "release" mode by info@creosrl.it, 2025-02-19 17:35
  10. Fail to debug in Win 11 C/C++ by mortenlund, 2024-12-26 20:27

Last-Modified Blogs

  1. System Workbench for STM32