0.9.0 is almost ready! This version has a lot of new features, we are preparing a blog post explaining the most important.
As with every release lately, before the final version, we put out a Release Candidate for public testing.
It would be great if people could download the packages for the platforms they use and see if they notice any issues.
Also since 0.9.0 we have support for exporting OF applications to run on the web. If you use any platform with support for makefiles (right now linux, osx and mingw) you can install Emscripten and compile any OF application to run on the web calling:
Another change in the supported platforms is that we are dropping support for Codeblocks under windows. The recommended IDE is now Visual Studio and the mingw package now provides only makefiles that will run under msys2.
Weāll put new install guides for both Emscripten and Msys2 in the web soon.
It would be really helpful, if you could try running existing projects with 0.9.0 RC1 to see if issues arise but 0.9.0 is a major version change and as such thereās some breaking changes so testing old projects will likely require some changes in your code. Feel free to ask in this same thread if you find any problem migrating old projects.
If you find any other problem in the release please open an issue in the gihub issue tracker.
If you havenāt reported bugs before, just use this link:
openFrameworks team members will comment on the issue and together weāll figure out how to fix it (either for this release, or 0.9.1 depending on the severity and complexity).
Hi guys! Is it possible to tag this release in github, so its easier to track this release moving forward?
Iām happy to track this thread down in the future, but its hard to reconcile which branch matches with the exported builds provided here if using github exclusively.
hey @grayfuse usually we only tag the releases, not the release candidates, as we tend to find important bugs in the release candidates and would like to discourage any ongoing use of them. once 0.9.0 is released (likely the next two weeks) we will tag the commit that is packaged for download.
@kylemcdonald That totally makes sense. Its been difficult understanding what addons are targeting what builds of oF, especially given people have been saying this is ācompatible with 0.9ā for months, when thereās not actually a tagged release of 0.9. Makes it really hard to teach to students, and also difficult to track from week to week what works with what.
Really looking forward to this release so I can consolidate that part of my brain. Iāll be hunting for issues and posting to github as I find, do let me know if I can be of assistance in any other way!
i totally get that. ācompatible with 0.9.0ā means people are trying to keep up with github/master, but itās a potentially misleading thing to say when github/master is always changing. we would like to move to a faster, fully automated release cycle after this, and that will make the 18-20 month delay between releases less of a confusion factor in teaching. the new project generator should help with that a lot too.
re assistance: more testing would be great! (especially try compiling old projects with 0.9.0)
I have currently issues with loading a 3d model with assimp⦠the supported models by examples are working as expected but my own seems not to work. In version 8.4 my own Mesh was working as expected but with 0.9.0RC1 it seems not so⦠Do I need to have a specific order or way to export it with blender?
regards
Thanks for the great work!
regards
Schreda
Hi, when I try to compile from MSYS2, I get this error. Am I doing something wrong?
I am using the empty project given with the RC.
A tutorial to setup the makefile would be really nice.
Side note: I am using a new IDE called CodeLite, and if I get the makefile working Iād be happy to write a tutorial for that for the website. It sems very good and better than Code::Blocks
@BananasGoMoo there was a missing file in the msys2 distribution and the makefiles werenāt working. also you just need to run:
make
insisde the project directory no need to pass the makefile name. before being able to compile, youāll need to run the install_dependencies script in scripts/win_cb. from the msys terminal run:
I wanted just to ask, if I want to use it on older machines, what is the minim OS version needed ?
(In Snow Leopard 10.6.8) it doesnāt work, even in 32 bit mode.
it seems the script that generates the packages was deleting rtaudio from the mingw ones, it should be fixed in todayās nightly builds. if you can give it a try?
So far compiling on a Raspberry Pi 2 fails:
Iāve downloaded the linuxarmv7l_release.tar.gz, unpacked and ran the debian/install_dependencies.sh . Running make -j4 on one of the examples
produces
this is a bug, i fixed it in tomorrrowās nightly build but if you want to fix it your self you can edit libs/openFrameworksCompiled/project/makeFileCommon/config.linux.comon.mk and remove every appearance of -march=native -mtune=native around line 188
thnx, removed them but now Iām getting a compile error: /home/pi/of_v0.9.0RC1_linuxarmv7l_release/libs/openFrameworks/types/ofTypes.h:284:1: error: expected unqualified-id before āusingā
(gcc 4.6.3)