[LITMUS^RT] [PATCH 0/2] Add module functionality to liblitmus
Manohar Vanga
mvanga at mpi-sws.org
Wed Feb 5 18:44:36 CET 2014
Hey Björn,
I just wanted to point out that this method places certain restrictions on the filenames that you must use for your tasks. If you specify a different output binary name with regard to the source file name, the linker will not get called since that’s how the implicit rules work.
eg. if you’re compiling a binary called ‘example’ consisting of ‘task.o’, the linker will not get called.
eg. if you’re compiling a binary called ‘example’ consisting of ‘task.o’ and ‘another.o’, the linker will not get called.
eg. if you’re compiling a binary called ‘example’ consisting of ‘example.o’, the linker will get called.
eg. if you’re compiling a binary called ‘example’ consisting of ‘example.o’ and ‘another.o', the linker will get called.
:-/
On Feb 4, 2014, at 8:39 AM, Manohar Vanga <mvanga at mpi-sws.org> wrote:
> Hey Björn,
>
>> 1) Copy the basic task skeleton somewhere.
>>
>> 2) Create a local Makefile and include ${LIBLITMUS}/inc/config.makefile at the top.
>>
>> 3) If you want dependency tracking (ie., that changes in headers cause recompilation), include ${LIBLITMUS}/inc/depend.makefile.
>
> Ah thanks for that. I knew I was missing something. Please ignore these patches ;-)
>
> Thanks!
>
> —
> /mvanga
>
>
> _______________________________________________
> litmus-dev mailing list
> litmus-dev at lists.litmus-rt.org
> https://lists.litmus-rt.org/listinfo/litmus-dev
—
/mvanga
More information about the litmus-dev
mailing list