Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mekasha

Pages: [1]
1
Troubleshooting / Re: Rasp Pi - OpenXcom screen flicker
« on: December 30, 2016, 12:28:28 am »
You seem to be correct. I got my RP3 today but it was the same, however lowering the FPS to 20 seems to have fixed it. It does look to be the cutoff point, as 25 still allows some tearing.

2
Troubleshooting / Re: Rasp Pi - OpenXcom screen flicker
« on: December 26, 2016, 07:17:12 pm »
Building in release didn't fix it, but I'm going to order an RP gen 3 and see if that will handle it. Thanks for the help guys.

3
Troubleshooting / Re: Rasp Pi - OpenXcom screen flicker
« on: December 25, 2016, 07:59:51 pm »
I couldn't get CMake to work, is there a way to change it to compile in debug using just the included Make file?

4
Troubleshooting / Re: Rasp Pi - OpenXcom screen flicker
« on: December 25, 2016, 07:10:01 pm »
It is a Raspberry Pi B+, so not quite first generation. It's able to run SNES emulators out of the HDMI without problems.

I've also attached "options.cfg" in case that has any more indepth settings.


5
Troubleshooting / Re: Rasp Pi - OpenXcom screen flicker
« on: December 25, 2016, 07:02:02 pm »
Grab of the video settings screen is attached. I should mention that the opening cutscene doesn't flicker, it only starts once the main menu comes up (and does persist in the geoscape/battlescape).

6
Troubleshooting / Rasp Pi - OpenXcom screen flicker
« on: December 25, 2016, 06:21:40 pm »
I was able to get Openxcom built and running on a Raspberry Pi, but when I launch the screen has significant flickering. It seems to lessen when I set the resolution t around 1024x768, but I couldn't get it 100% working. Are there any common troubleshooting steps I can try?

7
Builds & Ports / Re: Rasp Pi compile error logs
« on: December 25, 2016, 06:16:13 pm »
After a string of issues trying to get YAML updated, I re-installed Raspbian from the latest image and was able to build, although without using CMAKE (not sure if this is suboptimal compared to using the supplied Make file). Thanks for your help.

8
Builds & Ports / Re: Rasp Pi compile error logs
« on: December 24, 2016, 01:34:14 am »
Running "dpkg-query -l | grep yaml" gives me these 3:

libyaml-0-2:armhf       0.1.4-2+deb7u5
libyaml-cpp-dev          0.3.0-1
libyaml-cpp0.3:armhf  0.3.0-1

9
Builds & Ports / Rasp Pi compile error logs
« on: December 23, 2016, 10:37:05 pm »
Somewhat new to Linux and compiling, but I was hoping someone could take a look at my attached error logs for some ideas on what I'm doing wrong. Here are the commands I run through to get to the point I'm at:

Code: [Select]
git clone https://github.com/SupSuper/OpenXcom.git openxcom
<copy DATA folders and patched files into /OpenXcom/bin/UFO>
mkdir openxcom/build
cd openxcom/build
cmake ..
cmake -DCMAKE_BUILD_TYPE=Release
make -j3

After "cmake ..", I get this error for the missing "doxygen" command:

Code: [Select]
-- Configuring done
-- Generating done
-- Build files have been written to: /home/pi/OpenXcom
found SDL 1.2.15 (/usr/lib/arm-linux-gnueabihf:/usr/include/SDL)
found SDL_mixer 1.2.12 (/usr/lib/arm-linux-gnueabihf:/usr/include/SDL)
found SDL_gfx 2.0.23 (/usr/lib/arm-linux-gnueabihf:/usr/include/SDL)
found SDL_image 1.2.12 (/usr/lib/arm-linux-gnueabihf:/usr/include/SDL)
found yaml-cpp(/usr/lib/arm-linux-gnueabihf:/usr/include/yaml-cpp;/usr/include/yaml-cpp/..)
git found: /usr/bin/git
version:1.0.
No doxygen command found. Disable API documentation generation
-- Configuring done
-- Generating done
-- Build files have been written to: /home/pi/OpenXcom

If I try to push through and do the "make" portion, I then get a bunch of errors related to YAML::Node:

Code: [Select]
[  0%] [  0%] [  0%] Building CXX object src/CMakeFiles/openxcom.dir/Basescape/BaseInfoState.cpp.o
Building CXX object src/CMakeFiles/openxcom.dir/Basescape/BasescapeState.cpp.o
Building CXX object src/CMakeFiles/openxcom.dir/Basescape/BuildFacilitiesState.cpp.o
In file included from /home/pi/OpenXcom/src/Basescape/../Mod/Mod.h:27:0,
                 from /home/pi/OpenXcom/src/Basescape/BuildFacilitiesState.cpp:21:
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:130:9: error: ‘convert’ is not a template
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:131:2: error: explicit specialization of non-template ‘YAML::convert’
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h: In static member function ‘static YAML::Node YAML::convert::encode(const OpenXcom::UnitStats&)’:
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:135:21: error: no match for ‘operator=’ in ‘node.YAML::Node::operator[](((const char*)"tu")) = rhs.OpenXcom::UnitStats::tu’
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:135:21: note: candidate is:
/usr/include/yaml-cpp/node.h:33:21: note: YAML::Node& YAML::Node::operator=(YAML::Node&)
/usr/include/yaml-cpp/node.h:33:21: note:   no known conversion for argument 1 from ‘const int’ to ‘YAML::Node&’
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:136:26: error: no match for ‘operator=’ in ‘node.YAML::Node::operator[](((const char*)"stamina")) = rhs.OpenXcom::UnitStats::stamina’
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:136:26: note: candidate is:
/usr/include/yaml-cpp/node.h:33:21: note: YAML::Node& YAML::Node::operator=(YAML::Node&)
/usr/include/yaml-cpp/node.h:33:21: note:   no known conversion for argument 1 from ‘const int’ to ‘YAML::Node&’
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:137:25: error: no match for ‘operator=’ in ‘node.YAML::Node::operator[](((const char*)"health")) = rhs.OpenXcom::UnitStats::health’
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:137:25: note: candidate is:
/usr/include/yaml-cpp/node.h:33:21: note: YAML::Node& YAML::Node::operator=(YAML::Node&)
/usr/include/yaml-cpp/node.h:33:21: note:   no known conversion for argument 1 from ‘const int’ to ‘YAML::Node&’
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:138:26: error: no match for ‘operator=’ in ‘node.YAML::Node::operator[](((const char*)"bravery")) = rhs.OpenXcom::UnitStats::bravery’
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:138:26: note: candidate is:
/usr/include/yaml-cpp/node.h:33:21: note: YAML::Node& YAML::Node::operator=(YAML::Node&)
/usr/include/yaml-cpp/node.h:33:21: note:   no known conversion for argument 1 from ‘const int’ to ‘YAML::Node&’
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:139:28: error: no match for ‘operator=’ in ‘node.YAML::Node::operator[](((const char*)"reactions")) = rhs.OpenXcom::UnitStats::reactions’
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:139:28: note: candidate is:
/usr/include/yaml-cpp/node.h:33:21: note: YAML::Node& YAML::Node::operator=(YAML::Node&)
/usr/include/yaml-cpp/node.h:33:21: note:   no known conversion for argument 1 from ‘const int’ to ‘YAML::Node&’
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:140:25: error: no match for ‘operator=’ in ‘node.YAML::Node::operator[](((const char*)"firing")) = rhs.OpenXcom::UnitStats::firing’
/home/pi/OpenXcom/src/Basescape/../Mod/Unit.h:140:25: note: candidate is:
/usr/include/yaml-cpp/node.h:33:21: note: YAML::Node& YAML::Node::operator=(YAML::Node&)
<snip>
/home/pi/OpenXcom/src/Basescape/../Mod/RuleRegion.h:130:9: error: ‘convert’ is not a template
/home/pi/OpenXcom/src/Basescape/../Mod/RuleRegion.h:130:38: error: ‘YAML::convert’ is not a template type
/home/pi/OpenXcom/src/Basescape/../Mod/RuleRegion.h:160:9: error: ‘convert’ is not a template
/home/pi/OpenXcom/src/Basescape/../Mod/RuleRegion.h:160:38: error: ‘YAML::convert’ is not a template type
src/CMakeFiles/openxcom.dir/build.make:100: recipe for target 'src/CMakeFiles/openxcom.dir/Basescape/BaseInfoState.cpp.o' failed
make[2]: *** [src/CMakeFiles/openxcom.dir/Basescape/BaseInfoState.cpp.o] Error 1
src/CMakeFiles/openxcom.dir/build.make:146: recipe for target 'src/CMakeFiles/openxcom.dir/Basescape/BasescapeState.cpp.o' failed
make[2]: *** [src/CMakeFiles/openxcom.dir/Basescape/BasescapeState.cpp.o] Error 1
CMakeFiles/Makefile2:90: recipe for target 'src/CMakeFiles/openxcom.dir/all' failed
make[1]: *** [src/CMakeFiles/openxcom.dir/all] Error 2
Makefile:133: recipe for target 'all' failed
make: *** [all] Error 2

My google-fu is failing on this, can someone provide some insights? I have attached the full logs.

10
Builds & Ports / Working install instructions for Raspberry Pi?
« on: December 22, 2016, 07:26:48 pm »
Looking for up to date/working instructions for getting OpenXCOM running on a Raspberry Pi. I've tried using Knapsu's instructions/package here without much success: https://knapsu.eu/openxcom/.

Thanks!

Pages: [1]