Hosted Projects - Standalone > The Babylon Project

TBP on Linux/MacOSX

<< < (3/41) > >>

Biscuit:
When using the *nix package , ships that have suffered damage and are on fire. The graphics for the fire have square black artifacts, same applies when a ship explodes. I have played around with settings and various switchs but to no effect. Am i missing something simple?

karajorma:
Basically that's cause the build is relatively new but the textures are relatively old. As a result they suffer from a change in how FS2_Open handles textures.

Should be fixed when TBP updates to be compatible with 3.6.9. (whenever that is).

Biscuit:
Thanks again. Guess I can live with that

Biscuit:
I have just checked out from CVS the latest version, using the script from the wikipage, complete fresh checkout as i deleted the fs2_open directory beforehand. Followed the instructions on the wiki page for configuration and compiling. I have also tried it with a fresh manual checkout.The Compile process bombs out with:

mission/missionparse.cpp: In function ‘int parse_object(mission*, int, p_object*)’:
mission/missionparse.cpp:3405: warning: operation on ‘num_alts’ may be undefined
mission/missionparse.cpp:3764: error: expected `)' before ‘{’ token
mission/missionparse.cpp: In function ‘void parse_asteroid_fields(mission*)’:
mission/missionparse.cpp:5778: warning: dereferencing type-punned pointer will break strict-aliasing rules
mission/missionparse.cpp:5783: warning: dereferencing type-punned pointer will break strict-aliasing rules
make[1]: *** [missionparse.o] Error 1
make[1]: Leaving directory `/home/******/fs2_open/code'
make: *** [all-recursive] Error 1

I have tried this with no CFLAGS set and using the CFLAGS set as an example inthe Wiki.
Configure/autogen output as follows:
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for ranlib... ranlib
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
Using Unix defines (for linux-gnu)
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for stdlib.h... (cached) yes
checking for socklen_t... yes
checking for std::ios_base... yes
checking for sdl-config... /usr/bin/sdl-config
checking for SDL - version >= 1.2.6... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating libjpeg/Makefile
config.status: creating lua/Makefile
config.status: creating code/Makefile
config.status: executing depfiles commands

Configure options:

Sound enabled .......... : yes
Text-to-speech enabled . : no

Debug build ............ : no
DEMO build ............. : no
Inferno build .......... : no
GProf support .......... : no

Biscuit:
Ah, found the answer in this thread I think

http://www.hard-light.net/forums/index.php/topic,41750.msg851756.html

Navigation

[0] Message Index

[#] Next page

[*] Previous page