Ready 0.9

32 views
Skip to first unread message

Tim Hutton

unread,
Dec 22, 2019, 3:30:54 AM12/22/19
to reaction-...@googlegroups.com
Hello,

We've made a 0.9 release of Ready. Changes: https://gollygang.github.io/ready/Help/changes.html

Binaries are available for Windows and MacOS: https://github.com/GollyGang/ready

Before we spread the word any further, please give it a go on your machines. Let me know if you want a binary for a platform that we haven't built.

Thanks to everyone for helping out. As always this is a collaborative effort.

Tim

Dan Wills

unread,
Dec 22, 2019, 9:06:26 AM12/22/19
to reaction-...@googlegroups.com
Hi Tim,
Nice work on getting 0.9 out the door! brilliant! :D

I think I should have contributed a line in the changes about the new Scripts/Houdini HDAs, should I go ahead and add something? (never mind if that line is not in the prebuilt packages). I intend to write a blog post with some howto info on it too, and will post a link when I do.

I kinda liked that there were linux builds before, why is it that we stopped doing them? Not a biggie but currently the GUI binary does build on my system but crashes on execute (could put in a ticket for that, but .. Gentoo, so I need to look into it) I was kinda hoping to have a chance to try a prebuilt version. I think I'd be ok with redhat/Fedora-style libs/compatibility, if that's an option.
Thanks again for all your work on this release!,
Dan

--
You received this message because you are subscribed to the Google Groups "reaction-diffusion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reaction-diffus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/reaction-diffusion/CAAcZTPRnwMGr%3DQ2bVRaqQcYE%3DmrNUvPVC4qvPoivCjx6BHbm5g%40mail.gmail.com.

Tim Hutton

unread,
Dec 22, 2019, 12:52:20 PM12/22/19
to reaction-...@googlegroups.com
I'll make a Fedora build, if that's useful.

Dan Wills

unread,
Dec 22, 2019, 5:44:17 PM12/22/19
to reaction-...@googlegroups.com
Yeah, thanks Tim that would be great, if it's not too much trouble!
I saw the amount of tweaking you had to do to get the other platforms to build, hope it's easier for Fedora!

I wrote this line about the new HDAs:
    Improvement: Added new HDAs (Houdini Digital Assets) for importing Ready VTIs into Houdini. See Scripts/Houdini/README.md
I'll check that in soon.

Dan Wills

unread,
Dec 22, 2019, 10:25:55 PM12/22/19
to reaction-...@googlegroups.com
I've pushed that line to changes.html in gh-pages now

I wanted to note that in order to get rdy to build on my Gentoo (where I have vtk/7.1.0 installed) I had to comment 4 lines in CmakeLists.txt because these libs don't appear to be present on my system.
3 of them are (presently) lines 444-446 that now say this for me:

# if( UNIX AND NOT APPLE )
#  set( EXTRA_VTK_LIBS vtkIOMPIImage vtkIOMPIParallel vtkRenderingFreeTypeFontConfig vtkRenderingMatplotlib )
# endif()

And the other is a few lines down at 497:

#    vtkFiltersParallelDIY2

Not really sure what effect this might have on the build.. just that it goes ahead with those lines commented.
Unfortunately I can't run the 'ready' binary that it produces (though the 'rdy' binary works fine)

The error I get when I try to run 'ready' (I haven't tried to google this yet) is this:

Fatal Error: Mismatch between the program and library build versions detected.
The library used 3.0 (wchar_t,compiler with C++ ABI 1010,wx containers,compatible with 2.8),
and your program used 3.0 (wchar_t,compiler with C++ ABI 1013,wx containers,compatible with 2.8).

I presume this is just something in my Gentoo Linux that needs to be rebuilt, so probably not a huge concern. I'll keep trying and let you know if I work it out.

Dan Wills

unread,
Dec 23, 2019, 3:02:14 AM12/23/19
to reaction-...@googlegroups.com
On this page (about gcc upgrade on Gentoo) I found a mention of the same sounding error (as the one I was getting on ready-GUI launch on my local build) :


I thought I had upgraded/rebuilt wxGTK recently, but now I'm doubting that (or at least I seem to have managed to upgrade the 3.0-gtk3 slot but not the plain 3.0 slot (I know, probably sounds like gibberish if you don't use Gentoo). Aaanyway I rebuilt the other slot, and now it works a charm!

I'd say not to worry about the Fedora build except that I do think that it will likely still be useful. It will definitely save some people the trouble of working out all the VTK gear.. I found the other day that compiling VTK from its github source can certainly take some time! (ultimately I didn't even need to, it turns out).

Would still be keen to hear your thoughts about the lines I had to comment in CmakeLists.txt to get it to build Tim! Maybe there are some circumstances in which those lines could switch themselves off, and it'll build in more scenarios?

Have a choice one,
Dan

Tim Hutton

unread,
Dec 23, 2019, 7:20:52 PM12/23/19
to reaction-...@googlegroups.com
Hi Dan,

I'm not surprised about the VTK lib lines in CMakeLists - as you can see they seem to be different with every version and have an ad-hoc sort of naming which implies that there is no grand scheme behind them. If there's a better way of linking them then I'd like to know what it is.

If the rdy binary works fine then I would say that you've succeeded with the VTK libs.

Can you now run the Ready GUI?

I've uploaded a Fedora binary anyway. Looks like the move to Wayland is causing problems for wxWidgets but there's a workaround (pushed to BUILD.txt) that seems to work. (I get a crash when I do Action > Select OpenCL device... but apart from that everything seems fine.)

Tim

Dan Wills

unread,
Dec 23, 2019, 10:06:53 PM12/23/19
to reaction-...@googlegroups.com
G'day Tim,
Yep I got the Ready GUI to build and it runs (now that it is linked with an updated wxGTK). Hooray!

I pulled down the Fedora build that you made, and perhaps unsurprisingly I couldn't get it to run on my system (I did try forcing it to use the versions of libs that I have via soft-links but then I got to libvtkTestingRendering.so.1 and I have no equivalent for that). Not a huge surprise since I have a mixture of lib versions that doesn't line up with what it needs.

Would static linkage be a possibility? I'm guessing it would be a pain because you'd have to have all the deps built for static linkage (.a) to link that way.

Have an ace one!
Dan

Dan Wills

unread,
Dec 24, 2019, 6:16:28 AM12/24/19
to reaction-...@googlegroups.com
I checked out what the linux package 'statifier' might do to the 'rdy' and 'ready' binaries that I built on my system, but for me at least, whatever it produces (so far) says exec format error:

exec format error: ./ready-static

All good, maybe it's just a pipedream ;D
Have a merry season!
Dan
Reply all
Reply to author
Forward
0 new messages