Ceedling 1.0.0 and :support

[CJCombrink]

Quick question just to make sure if I am not missing something while trying to migrate to ceedling 1.0.0:

My project has :paths: -> :support: -> - test/support/** which contains files platform_mocking.h and platform_mocking.c
Without much effort I am able to build the project and run the tests.

When I migrate to ceedling 1.0.0 and add the :paths: -> :support: -> - test/support/** to my project I get linker errors for all test files that does not include the mock file

#include "mock_platform_mocking.h"

The error undefined reference to XXX for each function in the platform_mocking.h header.

So the question is did I misconfigure my project so that this is now included for each test file or is this expected for ceedling 1.0.0?

[mvandervoord]

Hi :)

I'm not clear on how it was working previously given your description? In the past, if you were not #includeing mock_platform_mocking.h or platform_mocking.h in the test files, where were the test files picking up function definitions for these functions?

The test files DO need to include all the files that are to be linked, either by using #include or TEST_SOURCE_FILE.

[CJCombrink]

From what I see the test file does not include either one as it does not need platform functions.
Moving to ceedling 1.0.0 I get linker errors,

This is the verbose output

> Shell executed command:
`gcc "build/test/out/<test_folder>/<test_file>.o" "build/test/out/<test_folder>/filter.o" "build/test/out/<test_folder>/<test_file>_runner.o" "build/test/out/<test_folder>/unity.o" "build/test/out/<test_folder>/platform_mocking.o" "build/test/out/<test_folder>/platform_testing.o" -L build/native_all -o "build/test/out/<test_folder>/<test_file>.out" -l<my_lib> -lm`
> With $stdout: <empty>
> With $stderr: 
/usr/bin/ld: build/test/out/<test_folder>/platform_mocking.o:/home/ccombrink/dev/<project>/test/support/platform_mocking.c:8:(.data.rel+0x0): undefined reference to `PLATFORM_MOCK_Log'
/usr/bin/ld: build/test/out/<test_folder>/platform_mocking.o:(.data.rel+0x8): undefined reference to `PLATFORM_MOCK_Print'
/usr/bin/ld: build/test/out/<test_folder>/platform_mocking.o:(.data.rel+0x10): undefined reference to `PLATFORM_MOCK_ZeroedMalloc'
...

The header being compiled is not including platform_mocking.h. For some reason when I add the :paths: -> :support: part to my ceedling 1 project file it is compiled as if it is included.

If I just remove the :support: part from my project file (still ceedling 1.0.0) I get the following, which builds fine

> Shell executed command:
`gcc "build/test/out/<test_folder>/<test_file>.o" "build/test/out/<test_folder>/filter.o" "build/test/out/<test_folder>/<test_file>_runner.o" "build/test/out/<test_folder>/unity.o" -L build/native_all -o "build/test/out/<test_folder>/<test_file>.out" -l<my_lib> -lm`
> With $stdout: <empty>
> With $stderr: <empty>
> And terminated with status: pid 344649 exit 0

note the absence of the "build/test/out/<test_folder>/platform_testing.o" in the second one

[mvandervoord]

Ah. Is PLATFORM_MOCK_Print (for example) defined in the C file or is it fully defined in the header? Is it static? Inline? externed?

[CJCombrink]

Only declared in the header file.
No implementation exists in the source file

platform_mocking.h:

#ifndef <GAURRD_H>
#define <GAURRD_H>

#include <stdarg.h>
#include <stdlib.h>
#include "standards.h"

void PLATFORM_MOCK_Print(const char* fmt, ...);
void *PLATFORM_MOCK_ZeroedMalloc(size_t size);
...

#endif //<GAURRD_H>

[mvandervoord]

Ah, sorry. I wasn't clear. You're showing function declarations in the header (the "footprint" for the function... what arguments it takes and returns, etc). Where does the actual function definition (the implementation) exist?

[CJCombrink]

That is the thing, there is no implementation that I can see, the mock provides it for the ones that includes it in ceedling pre 1.
This is only an issue in ceedling 1.0.0 which is strange for me

[mvandervoord]

I understand your confusion. I'm also confused. If you aren't calling the PLATFORM_MOCK_ functions anywhere in your test files, I'm not sure why it would be looking for them?

It is definitely not the expected behavior... and I'm not able to reproduce it, unfortunately. :(