Add liblo to the feature list #146
Conversation
|
I have cleaned the history. I consider this a small addition that it does not rectify to fork a 2.6 branch. Having this merged releases us from some maintenance when developing the OSC interface. What do you think? |
|
@fwcd Can you verify this as well? Here I have picked explicit Xcode_13.1 Without it it would default to Xcode 14.2. What would be best? (This is currently used for the 2.5 and main (2.6) branch) |
|
If it builds, I'd say this looks good. Not bumping Xcode too far on 2.5 is probably a good idea in terms of risk, even though in principle it shouldn't matter. Same goes for making sure we use the same Xcode version here and in the mixxx repo. |
|
Currently we use an environment that has been build on older macOS and Xcode. In the mixxx repository we are on Xcode 14.2. So this is already an issue if it is an issue. |
|
Ah okay, then I see no reason why this should be an issue |
|
@fwcd can this be merged? |
|
I think so, yes |
|
Ok, than let's merge. |
No description provided.