GCC Build w/sdk9 (no rule to make target)

RE: GCC Build w/sdk9 (no rule to make target)

Haaris — Fri, 24 Nov 2017 12:10:34 GMT

PLEASE DO IT !!!!!!!! IM DESPERATE

RE: GCC Build w/sdk9 (no rule to make target)

Henrik M. — Fri, 23 Oct 2015 16:24:55 GMT

I may write a guide when I've made it work for both nRF51 and nRF52 more than once, if someone is interested.

RE: GCC Build w/sdk9 (no rule to make target)

Henrik M. — Fri, 23 Oct 2015 16:23:59 GMT

Somehow I managed to get it working by meticulously copying all relevant options from the Makefile into a new, empty C project in Eclipse.

Now it can build fine. And I can run the sample code on nRF51x.

Now I have issues with nRF52 Preview DK. Not with building the examples, but with running them on the hardware using JLink. I'll post a new question.. ;)

Thanks for your suggestions all of you!

RE: GCC Build w/sdk9 (no rule to make target)

Vidar Berg — Fri, 16 Oct 2015 09:48:41 GMT

Hi, it looks like it has trouble resolving paths with whitespaces. Please try to change the path to /Users/me/NordicSemiconductor/nRF51_SDK_9.0.0_2e23562/examples/ble_central_and_peripheral/ble_connectivity/pca10028/ser_s130_spi/armgcc

RE: GCC Build w/sdk9 (no rule to make target)

Scott — Thu, 15 Oct 2015 17:16:21 GMT

I'm also seeing similar problems building from the command line in OSX with an out of the box example from directory:

/Users/me/Nordic Semiconductor/nRF51_SDK_9.0.0_2e23562/examples/ble_central_and_peripheral/ble_connectivity/pca10028/ser_s130_spi/armgcc

I'm seeing:

$ make
rm -rf _build
echo  Makefile
Makefile
mkdir _build
make: *** No rule to make target `_build/Nordic', needed by `nrf51422_xxac_s130'.  Stop.

Also, I've updated MakeFile.posix with correct paths

RE: GCC Build w/sdk9 (no rule to make target)

Vidar Berg — Wed, 30 Sep 2015 08:25:53 GMT

The SDK makefiles have been tested and should not give any build warnings. However, from Eclipse it will appear to be errors since it is not able to resolve include paths and symbols unless added by the CDT parser, or that you have added them manually in your project settings. I would suggest to download SDK 8.0.0., add the hrs example project from the tutorial, then follow the instructions in the 'Enable auto discovery of symbols, include paths and compiler settings' section. Should be not red crosses in Eclipse if done correctly. I think it is better to have a working template, and then you can compare the configurations with your current project.

RE: GCC Build w/sdk9 (no rule to make target)

Henrik M. — Wed, 30 Sep 2015 08:06:23 GMT

Well, I don't remember (don't have the unmodified version in my workspace anymore, but could of course recreate it). I had a gazillion red crosses in the source editor, which I removed one by one, by including extra files via virtual folders, and finally adding constants such as the BSP_LED_APP_TIMERS_NUMBER. And also true and false, by the way.

RE: GCC Build w/sdk9 (no rule to make target)

Vidar Berg — Tue, 29 Sep 2015 08:13:22 GMT

But your are not seeing any errors in the build output (CDT Build console) when building the unmodified project? Actual build errors will be shown there as build is happening outside of Eclipse environment using GNU make and the ARM toolchain. In order for Eclipse to be able to resolve defines, and index header files you will need to have the CDT parser configured correctly as described in the "Enable auto discovery of symbols, include paths and compiler settings" section of the tutorial, and also apply the following changes to your makefile: Search for the $(NO_ECHO)$(CC) $(CFLAGS) $(INC_PATHS) -c -o $@ $< line in the makefile. Add @echo arm-none-eabi-gcc $(CFLAGS) $(INC_PATHS) -c -o $@ $< on the line above to echo the symbols and include paths used when compiling the source files.

RE: GCC Build w/sdk9 (no rule to make target)

Henrik M. — Mon, 28 Sep 2015 16:20:04 GMT

Makes sense @hnhoan

RE: GCC Build w/sdk9 (no rule to make target)

Henrik M. — Mon, 28 Sep 2015 16:19:41 GMT

With the unmodified version I got more errors. E.g. the BSP_LED_APP_TIMERS_NUMBER that was unresolved. I haven't tested the "import project from existing Makefile" because I couldn't get that to work at all.

RE: GCC Build w/sdk9 (no rule to make target)

Vidar Berg — Mon, 28 Sep 2015 12:06:15 GMT

Hi, please check if you get the same error if building an unmodified version of the ble_app_hrs example if you have not tried so already.

RE: GCC Build w/sdk9 (no rule to make target)

Nguyen Hoan Hoang — Mon, 28 Sep 2015 12:02:20 GMT

That is because there are major changes from 6 to 7 to 8. From 8 to 9 there are no apparent changes except some configuration defines.

RE: GCC Build w/sdk9 (no rule to make target)

Henrik M. — Mon, 28 Sep 2015 11:59:18 GMT

OK, perhaps I just got confused about the headline "Migrating to SDK 8". The blog mentions SDK 6, 7 and 8 ;) Thanks again, I'll try it out, looks promising!

RE: GCC Build w/sdk9 (no rule to make target)

Nguyen Hoan Hoang — Mon, 28 Sep 2015 11:56:10 GMT

It is sdk9. The blog is not just sdk9 but general for any ARM based embedded software development with Eclipse GCC.

RE: GCC Build w/sdk9 (no rule to make target)

Henrik M. — Mon, 28 Sep 2015 11:44:40 GMT

Hi Martin, Yes, and if I change the all target to the following, it correctly prints out the confirmed path to my compiler:

all:
   @echo $(GNU_INSTALL_ROOT)/bin/$(GNU_PREFIX)-gcc

RE: GCC Build w/sdk9 (no rule to make target)

Henrik M. — Mon, 28 Sep 2015 11:39:33 GMT

Thanks, the first 3 things checked out fine. I'll look into the tutorial you refer to, even though it seems a bit old. As a newbie with ARM GCC I'm a bit "scared off" by too many differences between what I need and the tutorial. The one I followed initially only had 1 difference: SDK8 (instead of SDK9). And I still couldn't get it to work ;)

RE: GCC Build w/sdk9 (no rule to make target)

Henrik M. — Mon, 28 Sep 2015 11:30:51 GMT

Thanks, I'll look into it. But that's (also) not for SDK 9.

RE: GCC Build w/sdk9 (no rule to make target)

MartinBL — Mon, 28 Sep 2015 09:26:43 GMT

In your makefile, are you using the correct path to the GCC toolchain pointing to "your_SDK_folder\components\toolchain\gcc"?

RE: GCC Build w/sdk9 (no rule to make target)

Michael Dietz — Sun, 27 Sep 2015 13:39:09 GMT

Some things to check off the top of my head:

First open a command prompt and type: arm-none-eabi-gcc -v It should print a bunch of info & version number. This will tell you the compiler is installed correctly and in your path variables.

Also I had to modify the makefile a bit to get it to work. Namely: GNU_INSTALL_ROOT := /usr/arm-none-eabi and all of the toolchain commands: CC := '$(GNU_PREFIX)-gcc' So double check your paths and make sure they are correctly defined in the Makefile.

Last make sure your make target is set as nrf52832_xxaa_s132 or one of the valid targets.

If none of that works this tutorial should get you there: www.hertaville.com/gcc-arm-toolchain-stm32f0discovery.html

RE: GCC Build w/sdk9 (no rule to make target)

Nguyen Hoan Hoang — Sun, 27 Sep 2015 01:31:51 GMT

Try Eclipse GCC from this blog