OF 0.12.1 Release Checklist

[dimitre]

Complete List - https://github.com/openframeworks/openFrameworks/milestone/27
Just starting a sketch of things that would be nice to work after 0.12 release, feel free to edit / suggest items

general / all

• Regression: ofGetFrameRate is always off by +0.5 fps #8271
• ofPixels different bit depth support #8282
• remove Boost ( remove from ofConstants.h ) Remove boost as alternative in ofConstants.h #8297 Remove boost from vs and vs2019 projects. #8303 Remove boost references  #8304 Remove boost from linux scripts, download_libs #8306 Remove boost from android. #8307
• remove Poco ( push to 0.13.0 ) (keep poco 12.1.0) Win/OSX
• rethink math constants
• merge @danoli3 's apothecary PR openFrameworks Cmake Dependancy Upgrades - Android NDK 24 / Android ARM64 / X86_64 / iOS / VS ARM64 / VS 2022  apothecary#231
• warning for unused function natural - see: OF 0.12.0 Release Checklist #6692 (comment)
• remove using namespace std; as the default fixing conflicting byte definitions #7628
• Add GLM define to project files - GLM_FORCE_CTOR_INIT needed for preprocessor macros  #6530 GLM Preprocessor Definitions to Project #8352
• ofNoise() -- Memory bad access issue #5820
• consider moving FS functions to internal only Should ofPathToString(), ofGetExtensionLower(), and FS-functions be private? #8410
• "ofSoundStream::stop()" causes error if "ofSoundStream::start()" was called atleast 2 times in a row before #6246

arm

• Error on a Raspberry Pi #7641
• Fix this example oF 0.12.0 shaders on Raspberry Pi 4  #7653
• [RPI] - missing nlohmann/json.hpp #8355
• [RPI] - missing libs #8356
• [RPI] - install_dependencies.sh #8359

android

• get android working again
• fix all examples (some deprecated code)

iOS

• new examples New iOS examples and fix dated iOS examples #7678
• get simulator builds working with xcframework solution
• [iOS] the distribution provides broken .xcodeproj for non-iOS examples  #8305
• [iOS] Debug/Release confusion between iOS-OFLib and the project #8308
• [iOS] Info needs an entry for location consent popup to show up #8310
• [iOS] editing source within an app's project tree OF core does trigger recompile the libs but ofxIOS is absent from sidebar #8312
• [iOS] openCV examples (using ofxOpenCV addon) don't seem to link the lib #8314
• [iOS] videoplayer is missing some link #8315
• [iOS] assimp has wrong lib architecture #8316

macOS

• curl regression - macOS: undefined SSL symbols in curl.a on x64 #7656
• macOS Clean deletes bin folder. [macOS] Xcode "Clean build folder..." aka <cmd-shift-K> removes bin/data directory #8276
• [bug :: macOS] bin/data in DerivedData breaks user interaction with ofToDataPath() #8321
• macOS - ofVideoGrabber device order is inconsistent. #8377

msys2

• make command is not working on msys2 + windows  #7668

vs

• Projects outside of OF folder broken when using addons - Projects outside of the OF folder broken in Windows 10 and Visual Studio when using addons #7560
• Make PG allow for retarget project on update ( as well as the currently working generate ) see: Need help checking / updating setup guides #7625 (comment)
• Dll issue with ofxLaser - 0.12.0 Project Generator errors on VS with ofxLaser #7652
• Windows Video Player doesn’t report back texture sizes in setup. #7665
• Project Generator needs fixing to work with Env Variables #8302
• Windows / VS / MSYS2 libs should ALL be Static builds not Shared apothecary#506
• Nightly: Visual Studio Assimp Debug Lib Errors #8343 Fix copy phase for VS in assimp.sh apothecary#525

linux

• 0.12.0 can't build on Ubuntu16.04 LTS #7633
• VS Code as default Linux IDE / better general IDE #7677
• videoPlayerExample not working/freezing on Linux gst 1.22 #7794
• Linux Mint 22.03 breaks on RtAudio::getApiName #8290
• gstreamer 1.26 - fails to open camera #8425

emscripten

• get camera working - see Bugfix emscripten webcam not working #7631
• get video examples working - see emscripten - video doesn't play in safari if autoplay is enabled #7626
• fix video regression - see emscripten - regression from #7617 - video files are not found #7627
• apply same video for audio files - see Bugfix emscripten audio loading #7632
• audio input example doesn't work on Safari - no request for microphone either. - fix see emscripten - audioInputExample - switch to navigator.mediaDevices.getUserMedia #7638
• make audio track detection work in all browsers - see: Fix video emscripten #7637 (comment)
• PBR examples not working with cubemap
• assimpModelLoader broken for gltf emscripten Emscripten - Assimp loading of GLTF Models crashes / throws exception #7738
• Emscripten - duplicate symbols between ofxOpenCV and FreeImage libs #8289

[cjdg]

On Ubuntu 23.04, cannot install libopenal-dev, libopenal1 (= 1:1.19.1-2build3) pero 1:1.22.2-0ubuntu1~22.04.sav0 cannot be installed

[ofTheo]

hmm that's strange @cjdg - I can see it here:
https://launchpad.net/ubuntu/lunar/+package/libopenal-dev

did you try:
sudo apt-get upgrade

to upgrade the packages on your system?

sometimes I find aptitude can handle these installs better.

sudo apt-get install aptitude
sudo aptitude install libopenal-dev 

[artificiel]

on my list:

misc #7620 #7621 #6939 #7565 #7271 #7031 #7122
install from GitHub streamline #7606 + #7607 + #7609
deprecate cleanup #1550
default to release #1022

also revisit #7352

(also: can close #7016 #1748 #1966 #7414 #7517)

[dimitre]

This one is a personal favorite to be discussed and maybe solved

• ofSetColor(ofFloatColor) down-samples back to 8 bit #5421

[dimitre]

One thing to plan for next release is if it will be compatible for c++14 or c++11 yet.
I think it is good ot make another release backwards compatible before start incorporating c++17 exclusive on the core.
This way we can get @danoli3 huge PR goodies in macOS 10.14 or earlier. what do you think ?

[ofTheo]

I'm leaning towards c++17 only for the next release, with no boost.
Apothecary has sucked up so much time for me and for others - the smaller the dependency list the better.

For OF we have always tried to support the last three versions of macOS and so that would be macOS 13, 12, 11 now.
10.14 is really out of date at this point.

People can also use 0.12.0 if they need < c++17.
Are you still on 10.14 @dimitre ? 🙂

Edit: that said maybe next release is 0.13.0 and 0.12.1 is a patch-fix release only if needed.

[artificiel]

I'm a bit confused I was under the impression that 0.12 was C++17 (namely std::filesystem, and also some constructs).

In any case i agree that moving forward is the correct course of action, but it would be preemptive vs "long term support" good to document an upfront compatibility list, matching OF "epochs" to OS versions.

I don't know about other platforms -- no windows, and on the linux side I'm with arch which is rolling and does not have a concept of version.

[ofTheo]

@artificiel that is correct but it does currently rollback to C++11 / 14 and uses boosts filesystem if C++17 filesystem is not available.

See: https://github.com/openframeworks/openFrameworks/blob/master/libs/openFrameworks/utils/ofConstants.h#L487

If we dropped boost from apothecary / OF then we would be saying you have to have full C++17 in your compiler to build going forward.

[danoli3]

Awesome yes yes! Okay deployment time, I'll summon the merge this week

[NickHardeman]

This one is a personal favorite to be discussed and maybe solved

• ofSetColor(ofFloatColor) down-samples back to 8 bit #5421

@dimitre Yes! I can add this to my list. :) Would love some more input on how ofSetColor(int c); should be handled.

[Jonathhhan]

Maybe implement webMIDI for Emscripten?
#7259
Its already working, but I guess my implementation is not perfect ;)

[dimitre]

We can assign open issues from older milestones too, if they are pertinent to this release
https://github.com/openframeworks/openFrameworks/milestones

[artificiel]

if I may allow myself to refer to #7320

TLDR my take is that releases should be as small and frequent as possible while being meaningful in one way (i.e. a certain central feature is structuring the release, and along with it comes a bunch of fixes, tweaks, etc.).

so I would turn your question around and instead of thinking of more stuff, I would look at what's the major thing in "12.1" and draw a line around that.

it is a break from semver, but as stated in the discussion above, proper semver creates overhead and pressure which does not really make sense for a toolkit as OF which will be forever in develop (reacting to the evolution of the platforms, IDEs, C++, concepts, etc). 1.0 is a wet dream with little purpose.

instead of building an arbitrary, hard-to-estimate and impossible-to-manage "todo list" that defines a future release, work can be published as it accumulates. (it is not really "original" in thinking as such; the strict semver requirements of course have their use, but it applies better to dependencies (where you blindly include/upgrade a library) and takes for granted that you have the ressources to administer the process). it is simpler to consider the branch and determine "that's an interesting lump" and produce 2023.10. keeping things fresh and up to date across a bunch of platforms has inherent value, at least as much as maintaining backward-compat (specifically if the idea is to embark fresh users, and not just cater to old-timers getting their 007 projects out of their EZ135 backups).

OF should not burden itself with administration. we see in the issues a lot of goodwill with tagging categories etc, as well as attempts to "organize" things, but entropy wins against such efforts because deep down the users-developers that want to contribute to OF-core must at some point make the active decision to allocate a part of their budget of brain-calories, and that comes out of one's other ongoing projects. it is one thing to "synergize" development momentum; it is another to end up with a task list that keeps growing.