jextract fails to compile generated source

[Maurizio Cimadamore]

On 29/06/2020 16:36, Ty Young wrote:
> Will there be the ability to dump layout information to a file added 
> anytime soon? I understand plugins are a thing, but I really feel like 
> there is a good use case where people just want to get layout 
> information and nothing else and it should be supported by default. 

https://gist.github.com/mcimadamore/5f002d8177e05780f068dd7874a5020b

(this was shared few weeks ago).

Yes, plugins _are_ a thing and I think it would be more constructive to 
try and understand what the jextract _API_ can do in order for you to 
generate the code the way you like it, rather than trying to convince us 
that "the way you like it" should be "The Way (TM)".

Separately, I personally find it hard to reconcile some of the 
"requests" with things that have been said in the past. At some point it 
was brought up the fact that jextract generated bindings were 
platform-dependent (true) - and that this was a "Bad Thing". Now you 
advocate that having a separation of declarations based on where the 
headers are on your system is the way to go - I believe header 
presence/absence/location is, perhaps the *least* stable thing you can 
get in C-land?

Having all symbols in the same place helped in nearly all the samples we 
tried out - of course this assumes that some filtering of the output is 
applied (I covered that in a separate email). Otherwise you will end up 
pulling up every knob of your system headers, which I agree would be 
undesirable.

Maurizio