Messages

16

Mac / Re: OSX installers

« on: January 26, 2012, 06:52:25 pm »

Produces exactly the same last 2 error messages. (After launching the one I compiled myself.)

Don't understand this -- I'd expect a "file not found" type message.

17

Mac / Re: OSX installers

« on: January 26, 2012, 01:00:29 am »

Downloaded the 2.4-dev Intel above again. This time, the md5 checks and the dmg opens. Recall that, previously, I downloaded it twice before reporting. Don't understand this inconsistency.

New copy crashes on launch in exactly the same way as the one I compiled myself.

Is it possible that people who download the .dmgs or follow the instructions to git the source for the first time somehow get a damaged intro.ogm?

18

Mac / Re: OSX installers

« on: January 25, 2012, 09:12:13 pm »

did you check the md5sum of your download? is it really the same file?

md5 check of the 2.4-dev Intel installer provided above fails.

19

Mac / Re: OSX installers

« on: January 25, 2012, 08:47:13 pm »

the problem is the ui_hunksize - it looks like it's too small. so running self-compiled binaries will work with

Code: [Select]

./ufo +set ui_hunksize 4

Issued this command in Terminal, but still get the same crash on launch and UFOAI console complaints re. intro.cgm:

2012/01/25 13:11:16 Haven't found a video stream in ogm-file (videos/intro.ogm)
2012/01/25 13:11:16 Could not load cinematic 'videos/intro'

Terminal ends with these messages:

music change to van_theme (from PsymongN3)
s_language has no value
executing autoexec.cfg
"version" is "UFO: Alien Invasion 2.4-dev AMD64 Jan 20 2012 MacOSX DEBUG"
150 static models loaded
]Segmentation fault: 11

Also, I discovered 2 things I don't understand:

• Although I followed the "Non-universal binaries" instructions, I ended up with an Intel version in ~/ufoai/contrib/installer/mac and a universal version one-folder-deeper in /ufoai-2.4-dev-maxosx-universal.
• The dmg (which opens fine on my system) that appeared in ~/Document/UFOAI-2.4-dev contains the universal version.

Both versions crash as described. Can send OSX Console logs via PM, if desired.

for running the dmg you have to start a terminal and type:

Code: [Select]

mkdir -p ~/Documents/UFOAI-2.4-dev/base
echo "seta ui_hunksize 4" >> ~/Documents/UFOAI-2.4-dev/base/config.cfg

please let me know whether this works for you. the next version of the dmg will have this fixed.

No help. The 2.4-dev Intel installer above and latest snapshot dmgs still say "no mountable file systems" on my 10.7.2.

20

Mac / Re: OSX installers

« on: January 24, 2012, 11:16:29 pm »

Out of curiosity, I tried the 15-Oct-11 PPC 2.4-dev in snapshots. That dmg opens fine for me in 10.7.2, although I can't run it of course.

21

Mac / Re: OSX installers

« on: January 24, 2012, 05:31:10 am »

Already listed my OSX as 10.6.8 above

Sorry -- missed it. Bears repeating for the benefit of the visually challenged. 

Otherwise, I just meant that if you have a graphics problem, for example, it's worth mentioning which card you have.

UFOAI console logs appear in your Documents folder, in folders named according to the UFOAI version. But you have none yet since you can't even open the dmgs.

22

Mac / Re: OSX installers

« on: January 24, 2012, 04:42:03 am »

I have no real knowledge of .dmg files, and wouldn't be comfortable manually adjusting the file or whatever mechanism the computer uses to read it.

Not possible to fix this ourselves. Furthermore, the current 2.4-dev Intel crashes on launch even if you compile it yourself, anyway. See the posts from PazAmericano and me, 20- and 22-Jan, above.

It looks like Mac users won't have access to new versions for the time being.  Is that an accurate conclusion?

Right. My guess is that Mattn is looking into all this and will enlighten us shortly.

BTW, suggest you start mentioning what version of OSX you're using and perhaps hardware (as relevant) when reporting problems. Helps them make better-educated guesses about what might be wrong.

23

Mac / Re: OSX installers

« on: January 24, 2012, 01:04:12 am »

EDIT: I just downloaded ufoai-2.4-dev-macosx-intel, and like with the file I downloaded from the normal download page, it says the file can't be opened because the disk image is not recognized.  Do you know the cause of that?

If you're referring to the latest (16-Oct-11) 2.4-dev Intel install from this thread, I reported the same error on 20-Jan-12, above.

If you mean the latest (21-Jan-12) build in snapshots, OSX 10.7.2 gives me a slightly different error when I try to mount that .dmg: "No mountable file systems."

Looks like the process being used to create these .dmgs is faulty, as far as 10.7.2 is concerned anyway.

24

Mac / Re: Corrections to instructions for compiling Mac non-universal 2.4-dev

« on: January 21, 2012, 12:04:37 am »

Done.

Wow. I finally made a contribution to this project. I feel good!

25

Mac / Re: OSX installers

« on: January 20, 2012, 10:55:58 pm »

Downloaded the Intel installer posted here 16-Oct-11 twice yesterday. OSX 10.7.2 gives an error when I try to mount: "ufoai-2.40-dev-macosx-intel.dmg not recognized."

So I compiled Intel 2.4-dev from source last night, which I assume is at least as up-to-date as the installer posted here. It crashes on launch, after starting to play the music.

UFOAI console log looks much the same as the one posted here 26-Sep-11, but ends:

2012/01/20 15:07:01 Haven't found a video stream in ogm-file (videos/intro.ogm)
2012/01/20 15:07:01 Could not load cinematic 'videos/intro'

~/ufoai/base/videos does contain an intro.ogm, so I gather there's something wrong with that file?

26

Mac / Corrections to instructions for compiling Mac non-universal 2.4-dev

« on: January 20, 2012, 07:16:44 pm »

I compiled a non-universal version of 2.4-dev on my 10.7.2 system for the first time last night. I offer the following notes for the benefit of people who are inexperienced with UNIX/Darwin, compiling programs, etc. but are nonetheless brave enough to try following the "Non-universal binaries" instructions at http://ufoai.ninex.info/wiki/index.php/Compile_for_Mac .

1. In Step 2, the text that starts "Edit the SDL_config.h..." can be ignored. You won't find the files or folders it speaks of, and the relevant file has been corrected already. Just cut and paste the 3 "sudo port" etc. commands into Terminal, press Return, and all will be well.

2. Before starting the "Compilation" section, you'll need to edit your .profile. This is because UFOAI compilation needs some paths that are not taken care of for you by the MacPorts installation process.

If you don't know what I'm talking about: (a) Download TextWrangler (freeware) from http://www.barebones.com/products/textwrangler/download.html ; (b) Use its File > Open to navigate to your home folder and enable its "Show hidden files" option; and (c) Open the ".profile" file you should see now so you can edit it.

Toward the bottom, substitute this export command: export PATH=$PATH:/opt/local/bin:opt/local/sbin:opt/local

Save the file, quit Terminal, then relaunch Terminal to make the new PATH operative.

Now, the "make" commands should execute without errors. You should also be able to compile newer versions of UFOAI without editing .profile again, i.e., this is a one-time fix.

27

Mac / Re: Question re. compiling 2.3.1 for PPC/OSX 10.5

« on: March 10, 2011, 05:57:27 pm »

I looked at the cflags files, to see whether there's anything obvious there that would enable me to easily change the compiler flags -- no dice.

I was hoping to learn the process for producing universal binaries and make them available to others so non-developer PPC users could run the dev version and participate in the beta testing (as well as run the stable version). But I'm spinning my wheels and can't make progress without help.

28

Mac / Re: Question re. compiling 2.3.1 for PPC/OSX 10.5

« on: March 09, 2011, 05:00:12 pm »

I found documentation about the compiler switches mentioned in the error message (http://gcc.gnu.org/onlinedocs/gcc/Option-Summary.html#Option-Summary):

-S: Stop after the stage of compilation proper; do not assemble.

-E: Stop after the preprocessing stage; do not run the compiler proper.

-save-temps: Store the usual “temporary” intermediate files permanently.

-M: Instead of outputting the result of preprocessing, output a rule suitable for make describing the dependencies of the main source file.

-arch: Specifies the architecture of the target cpu(s), e.g, i386, ppc970, etc. Apple's GCC on Darwin does create “fat” files if multiple -arch options are used; it does so by running the compiler or linker multiple times and joining the results together with lipo.

I suspect the only one that should be used for my purposes is -arch. I've studied the makefile and makefile.local (the latter is created by the configure script) but don't understand them well enough to confidently delete the others. For example, I can't even find a place where the -save-temps switch is set.

29

Mac / Re: Question re. compiling 2.3.1 for PPC/OSX 10.5

« on: March 08, 2011, 04:10:26 pm »

After some searching, I discovered that CFLAGS and LDFLAGS are flags for the compiler and linker, respectively, and my environment includes default paths to them. Therefore, changing those paths shouldn't affect the configure problems I've been reporting.

I concluded that Mattn was implicitly telling me to ignore those problems and try "make" again, after setting the flag paths per his instructions. Unfortunately, I got the same compiler errors as before:

gcc-4.0: -E, -S, -save-temps and -M options are not allowed with multiple -arch flags
make: *** [debug-darwin-powerpc/game/game/g_actor.c.o] Error 1

30

Mac / Re: Question re. compiling 2.3.1 for PPC/OSX 10.5

« on: March 07, 2011, 08:38:01 pm »

No help -- got the same messages. (I notice you used =-I for CFLAGS and =-l for LDFLAGS. Thinking one might be a typo, I tried all permutations.)