Hello,
I'm a fresh guy on the KEIL, and here are 3 general questions, thanks any masters helping on it.
1. Is it possible to build a library by keil which could be linked in another project, while in this project, the device CPU is different w/ the one of the library ?
For instance, in the library keil project , its device is stm32L075RZ(cpu type is Cortex-M0), while another project's device is stm32F1xx. In this case, it seems the library could not link in the later project. For my requirements, the library is not necessary to bind w/ a specific device/cpu, but the KEIL seems not allow this. Is it way to make the link happen?
2. Is there way to create multiple libraries in one KEIL project ? Or is there any work around ? It is a common thing if using MAKEFILE.
3. The KEIL could create multi-projects workspace. In this workspace, is it possible to bulk changing all projects from one device to another ?
Thanks in advance.
Hi Hans,
Really appreciate for the answer. The introduction is very detailed and the solution do work for my case.
It really fits w/ the functional requirements while not w/ usage conveniences.
I think the limitation comes from the KEIL compiler itself which result the whole things (libraries release, multiple targets maintaining etc) are very complicated.
In the case, the middleware developer have to release multiple libraries for different ARM targets/devices. And different targets, the components options might be different to maintain too. More, for kind of specific functional platform developers, they might have to maintain multiple projects w/ multiple targets and multiple settings in one KEIL workspace. Either,the batch tools management might be hard for developer if there's too many project and target need be selected. The CLI(command line interface) of KEIL is the ONLY sugar for them to mitigate.
If the KEIL compiler could put the devices related handler to a later time would be great.
Anyway, really thank you for the answer. It could make us survive at least. :)