-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.12.0 is out - lets break some **** #279
Comments
Looking into addons there are quite a lot that still use Poco. Wondering if we should maybe move ofxPoco to openFrameworks/ofxPoco with all the libs in place and then people can download as needed for 0.13.0 onwards? |
Most of my add-ons use it. So if it's available somewhere that would be great. |
+1 for getting ofxPoco out of the core! There were times where I needed
more of what poco offers than what ofxPoco has in it. Having to swap out
the core was a bit frustrating cause it made shipping the addon for others
to use challenging.
Dan
Sent from Gmail Mobile #autocorrect
…On Thu, Aug 31, 2023 at 8:41 PM Christopher Baker ***@***.***> wrote:
Most of my add-ons use it. So if it's available somewhere that would be
great.
—
Reply to this email directly, view it on GitHub
<#279 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFPVTAJ3KCJHDSEZTJO53DXYEVMPANCNFSM6AAAAAA4GRASUA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Okay I'll merge into latest master apothecary/android pr now and start this underway now Noticing the sizes of VS libs is now very much more compressed to, I think most are just release now but down from like 700mb to 30-50mb That's like 2.2gb deployed to 400-500 with arm64, x86_64 (64bit) Once we get it mergable we can do a release called daily instead of nightly tag and use to download and test on PR / scripts on openFrameworks core to start testing and merging with updated libraries |
@danoli3 - curious why the bleeding branch isn't uploading the files anymore. was that intentional? is it possible to get a short list of the platforms that need the most work in bleeding? |
Not completely sure, might need to trigger a rebuild with a new commit on
that branch! Let me do that now.
macOS is pretty much ready to go I think I was battling Cairo last one to
do.
I’m doing super better I think I can commit to this week sorting everything
out
…On Sat, 4 Nov 2023 at 7:35 am, Theodore Watson ***@***.***> wrote:
@danoli3 <https://github.com/danoli3> - curious why the *bleeding* branch
isn't uploading the files anymore. was that intentional?
is macOS safe to enable in terms of GitHub actions?
is it possible to get a short list of the platforms that need the most
work in *bleeding*?
—
Reply to this email directly, view it on GitHub
<#279 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGK2HFUE52MWJNSULBXCNDYCVIRXAVCNFSM6AAAAAA4GRASUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTGA3DGMJUGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Okay I think we broken a lot of things, but overall I think fixed most of the big issues. Done
Experimental
TODO:
Todo: Experimental:
|
@danoli3 this is great, thank you for all of the updates and effort. |
🙂
@danoli3 there are some aarch64 changes I got working just fyi
8c57dcf
fea8f77
Reminder we are only doing 64bit going forward so no VS 32bit libs etc.
The text was updated successfully, but these errors were encountered: