gopakumarce

Sure, I will attempt a test case. But does my line of reasoning sound logical ? Leaving aside all the Rust wrappers, the matter under discussion here is simply "should...

@ivmarkov any thoughts on this :-?

> > @ivmarkov any thoughts on this :-? > > I don't understand the problem still. Can you elaborate what is the problem, and what you would like to see...

@ivmarkov yes ill take a stab at it

PR here https://github.com/esp-rs/esp-idf-sys/pull/202

@ivmarkov thx for the response, yes I am passing in all the flags I get from build_output - the code is here https://github.com/gopakumarce/esp-idf-sys/commit/d919224f581a82283f67f4f7ae4584db74196f4b#diff-37bbeb3d6061a16a1b78c746bdf8b0c514d591ccdbf4ab731502d5d844b2c6c5R136 And yes I was trying to dig...

Note that in the diff above I tried including xtensa/config/core.h into the bindgen generated C file, thats actually silly of me because including that into a C file should not...

Ok, so as far as I can see, there really is no magic gcc flag, it uses ```xtensa-esp-elf-gcc``` for the actual compilation in Cmake, the xtensa-esp-elf-gcc (without the model number...

I see, thx for the context. ```xtensa-esp-elf-gcc --target-help``` has a 'dynconfig' option and ```xtensa-esp-elf-gcc --help``` also says a "spec" option, I was wondering if either of those are influencing what...

@ivmarkov circling back to this thread - pls see https://github.com/espressif/crosstool-NG/issues/50 - the esp-idf still uses the wrappers to compile/link, its just that the actual compiler is just built once, and...