HELP! - Xpresso Shared Library Advice

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

HELP! - Xpresso Shared Library Advice

557 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lonwalker on Mon Mar 02 08:15:06 MST 2015
I am new to the Xpresso platform (LPCXpresso v7.6.0) and have a task at hand I would like to get advice on how best to approach.

I have two NXP platforms which will be communicating with each other using a 'home grown' communication serial protocol over UARTs.
I would like the two target boards,  LPC1114 and the other a LPC1754,  to share the same protocol encode/decode routines within one shared common library.

When creating a library under each of the individual project's workspaces, it seems Xpresso asks for a target processor type and wants the library to be physically located within its own workspace folder. Seems this would not necessarily be accessible by the other processor's project easily and not necessarily the right target code (one is Cortex-M0 and the other is Cortex-M3).

How best would it be to set this up this type of arrangement of shared .C and .H files  between two separate,  individual projects? -  An arrangement in which each project could build from shared .C .H files with its own target processor.

I envision .C .H files in one directory somewhere in which both projects could access and use for their builds without the need of two separate, physical libraries under each workspace that would require a to 'copy' the .C .H files to the other project's workspace whenever a change in code is required.

Thanks in advance for your input, it will be greatly appreciated.

Lon



0 Kudos
Reply
1 Reply

540 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Mon Mar 02 09:16:36 MST 2015
First of all, if you have a library that is build for Cortex-M0, it will work for any Cortex-M processor (M0, M3, M4 etc). The Cortex-M0 code will be a little less efficient (a little larger and a little slower) than if it was built for Cortex-M3, but will happily link and run.

Alternatively, you can use Linked Folders (aka Linked Resources). A Linked Folder will appear in your project as if it is really part of your project. Search the help for Linked Folder (Help->Help Contents) for information.
0 Kudos
Reply