Eclipse Managed Make Project for nRF52

Question

I'm using nRF52 + SDK11.0.0 + s132 and following this tutorial and this blog to make a Managed Make project using the ble_hrs esample. 
 As I was going through the directory structure, I noticed that ble_app_hrs_gcc_nrf52.ld in the Eclipse project directory is exactly the same as armgcc_s132_nrf52832_xxaa.ld (located in the components\softdevice\s132	oolchain\armgcc subdirectory) but armgcc_s132_nrf52832_xxaa.ld is not being used. Why are there essentially two copies of this file? 
 Also, I am trying to match up the Managed Makefile flags with the Standard (tutorial's) Makefile flags and would like clarifications on: 
 
 
 --gc-sections is optional in the Standard build: Standard: -Wl,--gc-sections vs Managed: --gc-sections . Is this an issue? 
 
 
 -Map is optional in the Managed build: Standard: -Map=nrf52.map vs Managed: -Wl,-Map,"nrf52.map" . Is this an issue? 
 
 
 not linking libc and libnosys does not cause errors in the Managed Build. Are these necessary?

butch · Accepted Answer

1,2) Those are just two different forms of the same "option", both have the same effect (e.g. the gc-sections effect) -Wl,foo just says the option foo is passed to the compiler but understood by the linker. Maybe Eclipse managed make is passing the option directly to the linker instead of to the compiler which then invokes the linker. 
 
 Not necessary until your app uses a function from those libraries. The link phase of the build would fail otherwise. 
 
 I use Eclipse managed make. It seems fine but does require you to learn the GUI of Eclipse i.e. build configurations, project properties, etc. Also requires you to extract options and paths from the Nordic example makefiles.

Eclipse Managed Make Project for nRF52

Top Replies