Proper way to build a library for another platform

[kahlenberg]

Hi,

I want to build a library for rfal and ndef from https://www.st.com/en/nfc/st25r3916b.html and use it with nRF connect SDK https://www.nordicsemi.com/Products/Development-software/nRF-Connect-SDK

What is the proper way to build a static library? 

Thanks.

[Andrew Neil]

Isn't that already answered?

https://community.st.com/t5/st25-nfc-rfid-tags-and-readers/porting-st25r3916b-software-to-nrf5340/m-p/656694#M10572

[kahlenberg]

It was a different question and this one is another question.

I have two choices:

1) List all header directories of rfal and ndef into CMake as include directories and list all source files as source list in CMake and then compile it. The project will have lots of source files.

2) Build a static library from rfal source code and ndef source code and link it to my nRF application.

My question is about 2.

Thanks.

[Andrew Neil · Accepted solution]

https://community.st.com/t5/stm32cubeide-mcus/writing-stm32cubeide-libraries-what-is-the-best-practice/td-p/250393

https://community.st.com/t5/stm32cubeide-mcus/how-to-create-a-static-lib-with-cube-without-any-debug/td-p/115139