Alternatives To Using A Library For Common Code

Projects Programming
1

I recently converted some common code (used on several projects) into a Library. My reason for this was so that I had to maintain only one version of the code.

I have not been impressed with the way Libraries 'work' (need for 2 files, extra coding to call from library to library, ...).

Is there an alternative method of keeping only one copy of code to be used in multiple projects?

Thanks, John

2

jburrow:
Is there an alternative method of keeping only one copy of code to be used in multiple projects?

Yup... Roll your own build process. The 'library' is just how the IDE handles shared code.

3

jburrow:
I have not been impressed with the way Libraries 'work' (need for 2 files, extra coding to call from library to library, ...).

What extra coding? You put your .h and your .cpp file into a folder. That's the essence of sharing code. What exactly is the problem with that?

4

Its not the library's fault,

If you programmed your library too generic, then you have to use extra code to specify how you intend to use it.
Your library needs files to store its code.

Library's are great for 'common code' cos its 'reusable' code.

Put the files in your sketch directory and use

#include "lib.h"

instead of

#include <lib.h>

But defeats the purpose of creating a library.