<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><p style="font-family: Verdana, Arial, "Bitstream Vera Sans", Helvetica, sans-serif; font-size: 13px;" class="">That will save a lot of heartburn with all the gcc ports, python, perl, and all the others that bake in a path to the SDK.</p><p style="font-family: Verdana, Arial, "Bitstream Vera Sans", Helvetica, sans-serif; font-size: 13px;" class="">And it's how Apple is going now anyway.</p><p style="font-family: Verdana, Arial, "Bitstream Vera Sans", Helvetica, sans-serif; font-size: 13px;" class="">And helps ports build when they need a newer SDK than the versioned one that matches their system.</p><p style="font-family: Verdana, Arial, "Bitstream Vera Sans", Helvetica, sans-serif; font-size: 13px;" class="">This was undesirable in the 10.4 to 10.13 era, but it may be time to do it now for 11.x and up.</p><div class=""><br class=""></div><div class="">and <a href="https://trac.macports.org/ticket/61866" class="">https://trac.macports.org/ticket/61866</a></div><div class=""><br class=""></div><div class="">and no doubt many more similar headaches to come…</div><div class=""><br class=""></div><div class="">K</div></body></html>