PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : UT cache manager



pavosos
10.09.06, 11:38
hallo!

ich bin am versuchen einen cache manager für ut2k4 zu installieren
und scheitere bei der kompilierung des programms!

http://gunrealtools.sourceforge.net/#download


./autogen.sh
**Warning**: I am going to run `configure' with no arguments.
If you wish to pass any to it, please specify them on the
`./autogen.sh' command line.

processing .
Running libtoolize...
You should update your `aclocal.m4' by running aclocal.
Running aclocal -I macros ...
macros/linger.m4:4: warning: underquoted definition of AC_STRUCT_LINGER
run info '(automake)Extending aclocal'
or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
macros/gnome-cxx-check.m4:2: warning: underquoted definition of GNOME_CHECK_CXX
macros/check-utmp.m4:11: warning: underquoted definition of AC_CHECK_UTMP
Running autoheader...
autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for `config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced, see the
autoheader: WARNING: documentation.
Running automake --gnu ...
Running autoconf ...
Running ./configure --enable-maintainer-mode --enable-compile-warnings ...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
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 dependency style of gcc... gcc3
checking for library containing strerror... none required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
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 dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
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
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GNOME... Now type `make' to compile the package

auf make passiert nur das
"make: *** Keine Targets angegeben und keine »make«-Steuerdatei gefunden. Schluss."

ich denke das diese zeile relvant sein wird
"checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu"
oder ?

vieleicht könnt ihr mir aber auch eine alternatives cache programm nennen?

mfg

baumgartner
10.09.06, 11:45
auf make passiert nur das
"make: *** Keine Targets angegeben und keine »make«-Steuerdatei gefunden. Schluss."


Dein Configure erzeugt kein Makefile.

pavosos
10.09.06, 12:39
aber es sollte doch....

jeppo
10.09.06, 13:30
also ich clear meinen ut2004 cache mit folgendem kleinenm bash script


#!/bin/bash

# Cachecleaner
cd ~/.ut2004/Cache/ || exit
cache=$(cat cache.ini)
echo '[Cache]' > cache.ini
IFS=$'\n'
for i in $cache;do
cache_datei="${i%=*}.uxx"
ziel_datei=${i#*=}
if [ -f "$cache_datei" ];then
mv $cache_datei $ziel_datei
fi
done
mv *.ukx /usr/local/games/ut2004/Animations/
mv *.ka /usr/local/games/ut2004/KarmaData/
mv *.ut2 /usr/local/games/ut2004/Maps/
mv *.ogg /usr/local/games/ut2004/Music/
mv *.uax /usr/local/games/ut2004/Sounds/
mv *.usx /usr/local/games/ut2004/StaticMeshes/
mv *.utx /usr/local/games/ut2004/Textures/
mv *.int /usr/local/games/ut2004/System/
mv *.u /usr/local/games/ut2004/System/
mv *.ucl /usr/local/games/ut2004/System/
rm *.uxx

pavosos
10.09.06, 14:01
wow !
danke schön!

vieleicht magst dir ja überlegen dein scribt zu veröffentlichen,da in den weiten des www anscheined nur eine und komplizierte alternative zum cache leeren existiert!

ich könnte dabei helfen in dem ich die ut spiele seiten auf das programm hinweise!
mfg

schwarzbarde
11.09.06, 07:20
Ich stehe gerade aufem Schlauch.
Wofür müsst ihr den Cache eigentlich leeren?

baumgartner
11.09.06, 07:33
Damit sie die Maps wiederverwenden können nehme ich mal an...

jeppo
11.09.06, 11:59
naju ist doch jetzt öffentlich
ausserdem ist es kein richtiger cache cleaner da das script alles installiert was sich im cache befindet
beim richtigen cachecleaner kann man aussuchen was man installieren will

wäre relativ einfach mit dialog zu machen aber für mich reichts so

@schwarzbarde die dateien im cache werden nach einer bestimmten zeit (einstellbar in der ini) wieder gelöscht und damit man sie nicht wieder neu laden muss integriert mann sie mit hilfe von einem cachecleaner in seiner ut installation

nen paar sachen zu ut2004 gibts auf meiner hp http://jeppo.de
ansonsten da vorbeischaun http://fahnenfluechtig.de
oder da http://utzone.de