That's useful information, thanks! If there's a better way of avoiding this issue, I'm definitely game for trying it.
There are a few possibilities for how/where this arises:
1) This is a compiler bug
2) This is a toolchain incompatibility
3) This is gremlins
If you can send me a link to a copy of the vagrant box that you use to build the 10.11, I could use that to build a debug variant and track down the issue. If this is (1) or (3), we could find it this way and fix it in code.
If it is (2), we may need to provide a second download build under Mojave. This could either be in place of the current builds or in addition.
I don't see much in the way of Library commits to the 5.0 branch. @Jeff can comment more here but I doubt much of the work in the 5.1 branch directly affects us in 5.0.
Hi Adam-
That's useful information, thanks! If there's a better way of avoiding this issue, I'm definitely game for trying it.
There are a few possibilities for how/where this arises:
1) This is a compiler bug
2) This is a toolchain incompatibility
3) This is gremlins
If you can send me a link to a copy of the vagrant box that you use to build the 10.11, I could use that to build a debug variant and track down the issue. If this is (1) or (3), we could find it this way and fix it in code.
If it is (2), we may need to provide a second download build under Mojave. This could either be in place of the current builds or in addition.
I don't see much in the way of Library commits to the 5.0 branch. @Jeff can comment more here but I doubt much of the work in the 5.1 branch directly affects us in 5.0.
-S