@walkero Not a complete surprise, since I saw a hint maybe December or slightly after. But the rc1 doesn't do joysticks properly. So that if I were to do this now, I'd use dynamic linking, which always catches somebody off guard. I'm going to keep an eye on that, in addition to Flare updates.
But sure, this is pretty much what I have to go on wrt. building that, on AmigaOS: gcc5 c++ can compile the code if CMAKE_CXX_FLAGS:STRING=-std=gnu++14
These are the required libraries for linking: -lSDL2_image -ltiff -lpng -ljpeg -lwebp -lz -lSDL2_mixer -lsmpeg2 -lm -lvorbisfile -lvorbis -logg -lflac -lmikmod -lmodplug -lstdc++ -lSDL2_ttf -lfreetype -lz -lsdl2main -lsdl2 -lauto -lpthread -lm
For some reason, I had to expand a lot of those to point to the actual file. :I
Looks quiet. There's a 1.11 from 2019. I have definitely worked on 1.10 but ran into some issues.
Ah, I have made a note of it...
Quote:
MenuItemStorage.cpp: In member function 'void MenuItemStorage::initGrid(int, const Rect&, int)': MenuItemStorage.cpp:58:35: warning: argument 1 range [2147483648, 4294967295] exceeds maximum object size 2147483647 [-Walloc-size-larger-than=] highlight = new bool[_slot_number]; ^ In file included from /Work/dev/adtools-os4-8-20180502-562/include/c++/8.1.0/bits/stl_construct.h:59, from /Work/dev/adtools-os4-8-20180502-562/include/c++/8.1.0/bits/stl_tempbuf.h:60, from /Work/dev/adtools-os4-8-20180502-562/include/c++/8.1.0/bits/stl_algo.h:62, from /Work/dev/adtools-os4-8-20180502-562/include/c++/8.1.0/algorithm:62, from CommonIncludes.h:23, from EngineSettings.h:25, from MenuItemStorage.cpp:26: /Work/dev/adtools-os4-8-20180502-562/include/c++/8.1.0/new:122:7: note: in a call to allocation function 'void* operator new [](std::size_t)' declared here void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc) ^~~~~~~~ MenuItemStorage.cpp: In member function 'void MenuItemStorage::initFromList(int, const std::vector<Rect>&, const std::vector<std::__cxx11::basic_string<char> >&)': MenuItemStorage.cpp:79:35: warning: argument 1 range [2147483648, 4294967295] exceeds maximum object size 2147483647 [-Walloc-size-larger-than=] highlight = new bool[_slot_number]; ^ In file included from /Work/dev/adtools-os4-8-20180502-562/include/c++/8.1.0/bits/stl_construct.h:59, from /Work/dev/adtools-os4-8-20180502-562/include/c++/8.1.0/bits/stl_tempbuf.h:60, from /Work/dev/adtools-os4-8-20180502-562/include/c++/8.1.0/bits/stl_algo.h:62, from /Work/dev/adtools-os4-8-20180502-562/include/c++/8.1.0/algorithm:62, from CommonIncludes.h:23, from EngineSettings.h:25, from MenuItemStorage.cpp:26: /Work/dev/adtools-os4-8-20180502-562/include/c++/8.1.0/new:122:7: note: in a call to allocation function 'void* operator new [](std::size_t)' declared here void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc) ^~~~~~~~
I suppose it's meant to work on 32-bit systems without adjustments.
my issue was with finding some type of fonts etc. at startup and wouldn't even let me get to main screen which was strange as I had this version running great full screen for a while..anyhow all working again
yes working fine now. It's been a while now not playing Flare so it could be while testing other stuff I sonehow messed up some startup fonts etc needed for Flare to boot up? who knows..all's well that ends well I say
I just noticed that when I exit Flare I get a blank screen and system freeze..have to reset my X1000. This is from a new install..strange as my previous (same version) install had no issue at exit??
Can any X1000 owners confirm if a fresh install does the same thing?
I built the latest Flare engine today using GCC 11.2 without compiler issues. It took some time to install all library dependencies but these are all in OS4Depot. Then I tested Flare using version 1.14 data. Starts and plays OK in SW/HW mode, based on quick tests.
Just for information if you or somebody else is interested to update the port.