subject:"\[Bug target\/105719\] RFE\: fixincludes should handle Frameworks"

[Bug target/105719] RFE: fixincludes should handle Frameworks

2024-06-07 Thread egallager at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105719 Eric Gallager changed: What|Removed |Added Status|ASSIGNED|NEW CC|

[Bug target/105719] RFE: fixincludes should handle Frameworks

2023-05-18 Thread egallager at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105719 --- Comment #6 from Eric Gallager --- (In reply to Iain Sandoe from comment #4) > Created attachment 55084 [details] > Implement the use of fixed framework headers > > this was a proof-of-principle exercise while looking into issues caused by >

[Bug target/105719] RFE: fixincludes should handle Frameworks

2023-05-15 Thread bkorb at gnu dot org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105719 --- Comment #5 from Bruce Korb --- It's been a long time since I mucked with fixincludes. My first guess, without going back and reading code, would be to provide fixincludes with a list of trees to traverse and not have it burned into fixinclud

[Bug target/105719] RFE: fixincludes should handle Frameworks

2023-05-14 Thread iains at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105719 --- Comment #4 from Iain Sandoe --- Created attachment 55084 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55084&action=edit Implement the use of fixed framework headers this was a proof-of-principle exercise while looking into issues ca