Messages

1

Builds & Ports / Re: PowerPC Mac Support

« on: April 06, 2016, 12:30:01 pm »

If homebrew supports OSX on PPC still, the homebrew build instructions for a Unix style OpenXCOM should work

I doubt any XCode project support will now exist for a sufficiently old XCode on PPC OSX.

2

Suggestions / [FEATURE] Terrain Type display on mouse hover

« on: September 08, 2015, 10:38:48 pm »

I can't keep track in my head what each shade of blue means with respect to the terrain; I'd like to see that in the UI somewhere (in UFO, it was easier, the colours are more distinct and there were less terrain types?)

The point is that some terrains make battle easier or harder, and it would be nice to know if now is a good time to down that USO, or if I should wait a bit more.

3

Troubleshooting / Re: Trouble Installing Nightlies on Yosemite Mac

« on: September 07, 2015, 09:02:56 pm »

I have attached a file listing of the OpenXCOM on OSX directory structure for the nightly builds (with TFTD data only + .ogg remixed soundtrack)

I run OpenXCOM as

george-russells-imac:bin grrussel$ ls
TFTD      UFO      common      openxcom   openxcom.log   standard
george-russells-imac:bin grrussel$ ./openxcom

4

Open Feedback / Feedback from OpenXCOM TFTD

« on: August 11, 2015, 11:39:00 pm »

So far, so good: loving it;

Gods, it got difficult quick. I tried veteran, and the only missions I seemed to get were terror sites... with rookies and starter weapons, eek!

Started again on 'beginner'

So far, all terror missions occur at night, without exception; should they? In the original, the targetting bug let you delay until dawn, but not OpenXCOM, afaict!

The highlight so far was being hit (well, near misses, but same results!) by 4 disrupter pulse missiles, killing 11 of the 14 strong squad, most still in the sub, (the one that ran got shot subsequently, the lone survivor went beserk and shot his sole other remaining comrade, before eventually regaining control and bailing with the sub. I guess it wasn't a great idea to land a triton right next to the intact medium sub.

Other highlight was the lobsterman that climbed up on the triton roof and kept killing any trooper who came out for a shot; its supposed to be my sniper vantage for the initial deployment

Its July, and I have no surviving aquanauts from January. I know of one base I need to deal with, I am still only with plastic aqua armor, have researched all alien non-melee weapons.

Still alive!

The dots on the geoscope for Alien base / terror site seem small relative to Xcom bases, quite hard to see,
 

5

Builds & Ports / OSX build error

« on: May 04, 2015, 07:06:33 pm »

c++ -Wall -Wextra -O2 -Wall -Wextra -DOSX -D_GNU_SOURCE=1 -D_THREAD_SAFE -I/usr/local/include/SDL -I/usr/local/Cellar/yaml-cpp/0.5.1/include  -c -o ../obj/RNG.o Engine/RNG.cpp
Engine/RNG.cpp:104:15: error: use of undeclared identifier 'rand'
        return (int)(rand() % (max - min + 1) + min);
                     ^
1 error generated.

I believe the stdlib.h header needs included, explicitly, in the .cpp file.

Cheers,
George

6

Programming / Re: Any interest in more CI builds?

« on: March 21, 2015, 10:14:48 pm »

Sounds like a good idea

https://docs.travis-ci.com/user/osx-ci-environment/

We already can and do build each git version in OSX (https://bitbucket.org/grrussel/openxcomosx)

export 'CXXFLAGS=-Wall -Wextra -O2''
export PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
cd src
make -f Makefile.simple clean

The question is really does travis retain the binaries after a build? To allow downloading and testing them, not merely that the source code built

7

Programming / Re: Build fix for OSX 10.9

« on: April 30, 2014, 02:23:18 pm »

The makefile.simple no longer specifies a default target of OSX, so the OSX autobuilder got broken.

Now, the makefile can detect OSX automatically, se

https://gist.github.com/anonymous/626242249065b31f39d9

for the 3 line patch.

8

Programming / Re: Build fix for OSX 10.9

« on: April 10, 2014, 10:10:23 am »

One more;

Basescape/MiniBaseView.cpp:84:20: error: out-of-line definition of 'setSelectedBase' does not match any declaration in 'OpenXcom::MiniBaseView'
void MiniBaseView::setSelectedBase(unsigned int base)
                   ^~~~~~~~~~~~~~~

diff --git a/src/Basescape/MiniBaseView.cpp b/src/Basescape/MiniBaseView.cpp
index 0dbbce3..2c797f4 100644
--- a/src/Basescape/MiniBaseView.cpp
+++ b/src/Basescape/MiniBaseView.cpp
@@ -81,7 +81,7 @@ size_t MiniBaseView::getHoveredBase() const
  * the mini base view.
  * @param base ID of base.
  */
-void MiniBaseView::setSelectedBase(unsigned int base)
+void MiniBaseView::setSelectedBase(size_t base)
 {
        _base = base;
        _redraw = true;

9

Programming / Re: Build fix for OSX 10.9

« on: April 09, 2014, 10:16:41 pm »

Not always 32bit in size, however ;-)

The OSX builds are 64bit, and therefore would have a 64bit size_t type

10

Programming / Re: Build fix for OSX 10.9

« on: April 09, 2014, 10:57:09 am »

diff --git a/src/Interface/TextList.cpp b/src/Interface/TextList.cpp
index 58adef3..f76de21 100644
--- a/src/Interface/TextList.cpp
+++ b/src/Interface/TextList.cpp
@@ -570,7 +570,7 @@ void TextList::setCondensed(bool condensed)
  */
 int TextList::getSelectedRow() const
 {
-       int selRow = std::min(_selRow, _rows.size());
+       int selRow = std::min(_selRow, (unsigned)_rows.size());
        return _rows[selRow];
 }
 
fixes the compilation.

11

Programming / Re: Build fix for OSX 10.9

« on: April 09, 2014, 10:49:07 am »

As of change set:

ensure intro movie is centered on linux (detail)
Added multiline textlists. (detail)

The OSX build fails.

Interface/TextList.cpp:573:15: error: no matching function for call to 'min'
        int selRow = std::min(_selRow, _rows.size());
                     ^~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/algorithm:2322:1: note: candidate template ignored: deduced conflicting types for parameter '_Tp' ('unsigned int' vs. 'unsigned long')
min(const _Tp& __a, const _Tp& __b)
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/algorithm:2314:1: note: candidate function template not viable: requires 3 arguments, but 2 were provided
min(const _Tp& __a, const _Tp& __b, _Compare __comp)
^
1 error generated.

12

Programming / Re: Build fix for OSX 10.9

« on: April 02, 2014, 09:47:29 pm »

and it builds on OSX again :-)

13

Programming / Re: Build fix for OSX 10.9

« on: April 02, 2014, 09:42:09 pm »

FYI: the OSX builds are made with clang, not g++, so it makes for a 3rd possibility of compiler variation. But, essentially, declaring the statics as was done in the header only, and then taking the address of the static (as is done in calling std::min with its reference parameters) seems not to work on clang, some g++ versions, and is also not standard c++; As for the other instances of this, well, perhaps it is simply luck that they are not passed to std::min or a similar function or usage?

14

Programming / Re: Build fix for OSX 10.9

« on: April 02, 2014, 09:29:27 am »

Looks like MSVC have this as an extension, and offer a workaround for the multiple instances too

https://msdn.microsoft.com/en-us/library/34h23df8.aspx

Out of Class Definition of static const Integral (or enum) Members

Under the standard (/Za), you must make an out-of-class definition for data members, as shown here:

class CMyClass  {
   static const int max = 5;
   int m_array[max];
}
...
const int CMyClass::max;   https:// out of class definition

Under /Ze, the out-of-class definition is optional for static, const integral, and const enum data members. Only integrals and enums that are static and const can have initializers in a class; the initializing expression must be a const expression.

To avoid errors when an out-of-class definition is provided in a header file and the header file is included in multiple source files, use selectany. For example:

__declspec(selectany) const int CMyClass::max = 5;

15

Programming / Re: Build fix for OSX 10.9

« on: April 02, 2014, 09:26:13 am »

OSX builder is once again broken.

Looks like the C++ code is non-standard as written.

https://stackoverflow.com/questions/3025997/c-defining-static-const-integer-members-in-class-definition