Native Assembler Api Linkage dependency on C Headers

Help/Discuss
1

Hi,

Is there a mechanism to define an API dependency on a separate NativeLibrarySpec in an assembler sourceset for a NativeLibrarySpec or NativeExecutableSpec? Similar to the c/cpp lib dependency mechanism.

I have a scenario where I have a set of c/cpp header files in a NativeLibrarySpec(LibA). In a separate NativeLibrarySpec(LibB) I have a set of c/cpp and asm files. LibB is set to have a header/api linkage dependency on LibA for both the c and cpp sourcesets. This works perfectly, however, I am unable to find a way to do the same for the assembler source set.

One of the assembler source files contains a #include to a C header, with the current setup, it fails as the header is not in the include path.

As a temporary work around I have manually defined the include path in the assembler args but this is not a clean solution, where i would like this to resolve automatically in the same fashion as the c/cpp header sets.

Thinking more generally it would be useful for the same NativeLibrarySpec to be able to internally reference c/cpp headers defined in its c/cppsourceset within the assembler sourceset. Is that possible too?

Any guidance would be appreciated.

Thanks,
Shaun

1 Like
2

I am facing the same problem but whats worse in my case is Gradle does not detect the paths even after I have defined them in the assembler.args space. Could anyone kindly help with it?

3

Hi Ganesh,

This is a missing feature and the only workaround is using assembler.args. I have opened a feature request here. It would be nice if you could verify if such a request could solve your current scenario.

Thanks,

Daniel

4

Hi Daniel,

I raised the original query. I would like to verify it would solve my issue with it. :slight_smile:

Thanks,
Shaun