Eclipse Community Forums: C / C++ IDE (CDT) » Sharing .c/.h pairs in Multiple Projects

Home » Language IDEs » C / C++ IDE (CDT) » Sharing .c/.h pairs in Multiple Projects(Mainting .c/.h files whilst they are in development across multiple projects)

Sharing .c/.h pairs in Multiple Projects [message #1821844]

Thu, 20 February 2020 23:48

Eclipse User

Hi,

First post here. I've been using Eclipse previously with SystemWorkbench for STM32 and now the STM32CubeIDE.
I'm working on an embedded project which uses multiple microcontrollers and need to use the same .c and .h files for both (with different configs depending on which micro is being targeted).
I've been using symlinks in windows with the shared files located in a separate folder, however this isn't ideal due to having to setup new symlinks for new projects and iterations.

Ideally I'd like to have a separate folder with all of my different "libraries" (.c and .h) files which I can import into any project, and changes made in any project will update the files, and hance, their usage in other projects.

I've been trying to do this using paths and project preferences, but no luck so far.

Any thoughts?

Re: Sharing .c/.h pairs in Multiple Projects [message #1821937 is a reply to message #1821844]

Sun, 23 February 2020 23:00

Eclipse User

I'm not familiar with STM32CubeIDE.
You may get a better response at their support.
Third party developers sometimes trim the CDT IDE dropping features.

If it's like the standard issue of CDT, you're going to have problems when Eclipse builds the Makefile.
Eclipse built makefiles are limited to one executable.

One way would be to create projects for each "library" and actually create a library.
Then reference the library project from an executable project.
Project --> C/C++ General --> Project References

Another way might be to add source files into project A from project B using soft links.

Frankly, I would write and maintain my own Makefile.

Re: Sharing .c/.h pairs in Multiple Projects [message #1821969 is a reply to message #1821937]

Mon, 24 February 2020 14:35

Eclipse User

One more vote for own Makefile.

I have pretty bad experience of CubeMX and the STM library code. CubeMX is an excellent tool for sorting out the package pin setups, but I would not bet the farm on their code.

Previous Topic:	Can't import simple libraries
Next Topic:	"Launch (project name ) is filtered " ?

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 18 01:32:02 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter