You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 17, 2021. It is now read-only.
I changed configurations and ended up with a *.a and *.dylib in my _install//lib/ folder. The build.py --framework option complained about multiple libs. This was with commit: a9443b4 . This isn't exactly as bug... (How should it know which type of lib to use?) It is easy enough to delete one and then re-run, but possibly an additional option is required to specify the desired framework type in cases where both libs are present. How do you want to handle this (or just leave as is)? I can probably modify as needed once I get past a couple deadlines.
The text was updated successfully, but these errors were encountered:
I changed configurations and ended up with a *.a and *.dylib in my _install//lib/ folder. The build.py --framework option complained about multiple libs. This was with commit: a9443b4 . This isn't exactly as bug... (How should it know which type of lib to use?) It is easy enough to delete one and then re-run, but possibly an additional option is required to specify the desired framework type in cases where both libs are present. How do you want to handle this (or just leave as is)? I can probably modify as needed once I get past a couple deadlines.
The text was updated successfully, but these errors were encountered: