How to creating a Keil project for a Mesh example(V3.0.0)

[Beike]

Platform:                  windows

hardware revisions: PCA10056

nrf5 SDK:                15.2.0

mesh SDK:              V3.0.0

IDE:                         Keil MDK \ SEGGER embeded studio

I want to use keil to develop mesh projects, but there are only SEGGER embeded studio examples in SDK, so how can i move the project from segger to keil?

I has found this thread, it tell us how to move mesh project(V0.10.0) to keil, I found there are some difference between mesh SDK V0.10.0 and V3.0.0 .

for example, the include path\ the preprocessor symbols...

And now, I has finished some work, has creating a project by keil for mesh example, and add include paths in keil, but the preprocessor symbols has changed from V0.10.0 to V3.0.0, 

so i can't compile it, it show so many errors and warnings.

could you tell me how can i set the preprocessor Symbols in keil?

 

[awneil]

Beike said:

I want to use keil to develop mesh projects

Why?

Beike said:

there are only SEGGER embeded studio examples in SDK

True.

So, if you want to use a non-supported toolchain, you need to be sufficiently experienced with that toolchain to manage it yourself.

Have you looked at the Keil documentation & examples on how to set up projects using their tools?

I would suggest that you, at least, start with SES - so that you have a supported, working base to go from.

Beike said:

how can i set the preprocessor Symbols in keil?

Follow the Keil documentation.

http://www.keil.com/support/man_arm.htm

Specifically: http://www.keil.com/support/man/docs/uv4/uv4_dg_adscc.htm

Beike said:

it show so many errors and warnings

Your screenshot shows only one warning - it is the same warning repeated 3 times!

So fix that issue once, and you will immediately remove at least 3 warnings - all in one go!

Most likely, the others are similar - either the same problem repeated in multiple places, or one error causing lots of subsequent errors.

Hence the rule is always: address the earliest issue first - it's likely that it will fix a load of follow-on problems.

This is actually standard stuff - not specific to Keil or Nordic or SES.

[Beike]

awneil said:

Why?

I am familiar with this development Tool.

awneil said:

So, if you want to use a non-supported toolchain, you need to be sufficiently experienced with that toolchain to manage it yourself.

I think Keil and SEGGER used the same toolchain, ARM Compiler Version 5

awneil said:

Follow the Keil documentation.

I known how to set preprocessor symbols in keil, but i don't known what the symbols are in relative mesh SEGGER project.

awneil said:

Your screenshot shows only one warning - it is the same warning repeated 3 times!

Yes, it is. But i think we should first ensure that macro definitions are configured correctly

[awneil]

Beike said:

I think Keil and SEGGER used the same toolchain, ARM Compiler Version 5

No, they don't - Segger uses GCC.