https://devzone.nordicsemi.com/f/nordic-q-a/88381/zephyr-in-project-librariesDear Nordic, Could you please suggest and and expamle or advice how to use in-project libraries properly (not &#39;externally built&#39; as an know example shows). It&#39;s better to move some code out to project libraries, but we&#39;ve faced the issue: &gt; c : /en-USTelligent Community 13Mon, 20 Jun 2022 06:37:31 GMThttps://devzone.nordicsemi.com/thread/373132?ContentTypeID=1Mon, 20 Jun 2022 06:37:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0838c572-99b7-458e-81bf-5c4cfd7d468eDmitry Kr<p>At the moment there is an easy temporary overcome for that is just adding of few compile options (just a copy from gcc commannd line call):&nbsp;</p> <div> <div><span>add_compile_options</span><span>(</span></div> <div><span>&nbsp; -mfloat-abi=hard </span></div> <div><span>&nbsp; -mcpu=cortex-m4 &nbsp;</span></div> <div><span>&nbsp; -mthumb &nbsp;</span></div> <div><span>&nbsp; -mabi=aapcs &nbsp;</span></div> <div><span>&nbsp; -mfpu=fpv4-sp-d16 &nbsp;</span></div> <div><span>&nbsp; -mfp16-format=ieee</span></div> <div><span>&nbsp; )</span></div> <div><span></span></div> <div><span>It&#39;s not a solution because you can change some options in the future that could lead to some issues (e.g. change FP16 format) still it works on early development stage.</span></div> <div><span></span></div> <div><span>Dear Nordic, is there any normal way to implement in-project libraries?</span></div> </div><div style="clear:both;"></div>