On Aug 27, 2021, at 12:02 AM, Marcel Taeumel ***@***.***> wrote:
I still wonder about the execution path of "conf.COG". Well, I changed "S=" because it is now one level deeper because of "building" but "../../../../processors" still doesn't make sense because "building/macos64ARMv8/gdbarm32/" is only 3 levels away from the top folder, not four. Same for the addition of "-I" in this commit, which assumes even 5 levels deep.
For "macos64x64/bochsx64/conf.COG" is looks reasonable: "../../../processors/IA32/bochs/configure", which is 3 hops back to the top level.
Can you explain this?
The configure script creates makefiles in subdirectories, so one needs one additional step up. In addition in gdbarm32 to be has to build in gdbarm32/sim/arm so one needs an extra step in the include path for platforms/Cross/plugins/GdbARMPlugin
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.