Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 155788 - dev-games/crystalspace-1.0 version bump
Summary: dev-games/crystalspace-1.0 version bump
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Games (show other bugs)
Hardware: x86 Linux
: High enhancement (vote)
Assignee: Philip Walls (RETIRED)
URL:
Whiteboard:
Keywords:
: 156617 162917 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-11-20 09:21 UTC by loux thefuture
Modified: 2007-02-01 05:20 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Portable 3D Game Development Kit written in C++ (crystalspace-1.1-r25803.ebuild,2.80 KB, application/octet-stream)
2006-11-20 09:22 UTC, loux thefuture
Details
Updated ebuild (crystalspace-1.1-r25803.ebuild,2.78 KB, text/plain)
2006-11-30 13:58 UTC, Frank Richter
Details
crystalspace-1.1-r26005.ebuild (crystalspace-1.1-r26005.ebuild,2.50 KB, text/plain)
2006-12-01 04:14 UTC, loux thefuture
Details
crystalspace-1.1-r26005.ebuild (crystalspace-1.1-r26005.ebuild,2.47 KB, text/plain)
2006-12-01 08:10 UTC, loux thefuture
Details
crystalspace-1.1-r26005.ebuild (crystalspace-1.1-r26005.ebuild,2.62 KB, text/plain)
2006-12-04 09:41 UTC, loux thefuture
Details
crystalspace-1.1-r26005.ebuild (crystalspace-1.1-r26005.ebuild,2.74 KB, text/plain)
2007-01-23 20:05 UTC, loux thefuture
Details

Note You need to log in before you can comment on or make changes to this bug.
Description loux thefuture 2006-11-20 09:21:59 UTC
Find attached crystalspace-1.1-r25803.ebuild 

A Portable 3D Game Development Kit written in C++,
http://crystal.sourceforge.net/
Comment 1 loux thefuture 2006-11-20 09:22:37 UTC
Created attachment 102409 [details]
Portable 3D Game Development Kit written in C++
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2006-11-29 08:47:42 UTC
*** Bug 156617 has been marked as a duplicate of this bug. ***
Comment 3 Frank Richter 2006-11-30 13:58:49 UTC
Created attachment 103065 [details]
Updated ebuild

Updated dependencies (see also bug 120307).
Added optional cegui support.
Removed unneeded perl build-time dependency.
Re-enable python and java bindings -  they *do* work.
Comment 4 loux thefuture 2006-12-01 04:14:59 UTC
Created attachment 103117 [details]
crystalspace-1.1-r26005.ebuild

updated crystalspace-1.1 to version 26005
moving it to regular /usr folder
Comment 5 loux thefuture 2006-12-01 08:10:30 UTC
Created attachment 103134 [details]
crystalspace-1.1-r26005.ebuild

add pkg_postinst for vfs.cfg
Comment 6 Frank Richter 2006-12-01 08:15:55 UTC
The latest r26005 ebuild does not take all the dependencies that changed into account.
Shouldn't all used use flags appear in IUSE?
And why is vfs.cfg copied to bin? This shouldn't be necessary. (And this particular statement is pointless as well, since it copied it as "cfs.cfg"...)
Why is cg-toolkit only used when the nvidia use flag is set? (That Cg only works with NVidia hardware is a common misconception, but it's useful on all hardware. Also, crystalspace works best when cg-toolkit is available.)
Comment 7 loux thefuture 2006-12-04 09:41:43 UTC
Created attachment 103338 [details]
crystalspace-1.1-r26005.ebuild

change vfs.cfg in the pkg_postinst function to remove ${P}
Comment 8 Tristan Heaven (RETIRED) gentoo-dev 2007-01-21 17:35:42 UTC
*** Bug 162917 has been marked as a duplicate of this bug. ***
Comment 9 Frank Richter 2007-01-23 16:58:08 UTC
The ebuild filters out some CFLAGS and LFLAGS emitted by configure; however, configure accepts a number of options that influence the flags. For example,
--enable-cpu-specific-optimizations=no prevents the emission of -march flags. It's probably a good idea to use these facilities instead of forcibly removing all flags.
Comment 10 loux thefuture 2007-01-23 20:05:29 UTC
Created attachment 107933 [details]
crystalspace-1.1-r26005.ebuild

add --enable-cpu-specific-optimizations=no
like res@crystalspace3d.org advice me
see you
loux
Comment 11 Frank Richter 2007-01-23 21:24:24 UTC
What other CFLAGS and LFLAGS would be "unwanted", anyway?
Comment 12 loux thefuture 2007-01-24 17:30:41 UTC
Hello,
we have a big discussion with Frank Richter about FLAGS (C/D),
his position is to let crystalspace handle them,
and mine is to trust user /etc/make.conf flags and not developpers of crystalspace,
so what is wrong or right i don't know this is my first ebuilds,
does malverian@gentoo.org has a point of view ?
thanks
loux
Comment 13 Josef Reidinger 2007-01-25 19:37:59 UTC
I try your ebuild, It's quite good (except downloading from private address). But when I try simple application it write me this:
SCF_ERROR: metadata retrieval error for /usr/lib64/libz.so: Error parsing metada
ta in /usr/lib64/libz.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libss.so: Error parsing metad
ata in /usr/lib64/libss.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libc.so: Error parsing metada
ta in /usr/lib64/libc.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libpam.so: Error parsing meta
data in /usr/lib64/libpam.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libncursesw.so: Error parsing
 metadata in /usr/lib64/libncursesw.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libpwdb.so: Error parsing met
adata in /usr/lib64/libpwdb.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libreadline.so: Error parsing
 metadata in /usr/lib64/libreadline.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libcurses.so: Error parsing m
etadata in /usr/lib64/libcurses.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libncurses.so: Error parsing 
metadata in /usr/lib64/libncurses.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libhistory.so: Error parsing 
metadata in /usr/lib64/libhistory.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libe2p.so: Error parsing meta
data in /usr/lib64/libe2p.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libwrap.so: Error parsing met
adata in /usr/lib64/libwrap.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libuuid.so: Error parsing met
adata in /usr/lib64/libuuid.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libcom_err.so: Error parsing 
metadata in /usr/lib64/libcom_err.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libpamc.so: Error parsing met
adata in /usr/lib64/libpamc.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libext2fs.so: Error parsing m
etadata in /usr/lib64/libext2fs.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libcrack.so: Error parsing me
tadata in /usr/lib64/libcrack.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libpthread.so: Error parsing 
metadata in /usr/lib64/libpthread.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libcursesw.so: Error parsing 
metadata in /usr/lib64/libcursesw.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libblkid.so: Error parsing me
tadata in /usr/lib64/libblkid.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libgpm.so: Error parsing meta
data in /usr/lib64/libgpm.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libbz2.so: Error parsing meta
data in /usr/lib64/libbz2.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libpam_misc.so: Error parsing
 metadata in /usr/lib64/libpam_misc.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libvolume_id.so: Error parsin
g metadata in /usr/lib64/libvolume_id.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libdevmapper.so: Error parsin
g metadata in /usr/lib64/libdevmapper.csplugin: Not an ELF file
SCF_ERROR: metadata retrieval error for /usr/lib64/libcap.so: Error parsing meta
data in /usr/lib64/libcap.csplugin: Not an ELF file

I hope I have good var:
user@localhost /zdrojaky/hyperion-test $ echo $CRYSTAL_PLUGIN
/usr/lib/crystalspace
user@localhost /zdrojaky/hyperion-test $ echo $CRYSTAL_CONFIG
/etc/crystalspace
user@localhost /zdrojaky/hyperion-test $ echo $CRYSTAL       
/usr
Comment 14 Frank Richter 2007-01-25 19:55:22 UTC
Josef: please file a bug upstream.
Comment 15 Tristan Heaven (RETIRED) gentoo-dev 2007-01-27 12:53:18 UTC
Needs USE flags that work. Just adding a dependency isn't enough.

http://www.gentoo.org/proj/en/qa/automagic.xml
Comment 16 Tupone Alfredo gentoo-dev 2007-01-31 08:51:52 UTC
Version 1.0 is now in portage. Please test and report failure.
Comment 17 Frank Richter 2007-01-31 14:59:11 UTC
CS itself does not depend on lcms. It only checks for it since it's needed on some platorms to get libmng to work. (See note in configure.ac.)

Comment 18 Frank Richter 2007-02-01 05:20:45 UTC
- "--disable-separate-debug-info" should be passed to configure. Otherwise, when building CS the binaries' debug info will be stripped into separate files - which gives funny results when combined with gentoo's own debug info stripping. (Note that that option also implies --disable-optimize-mode-debug-info.)
- Some dependencies configure tests for, but which you didn't disable: js, caca, bullet, openal, jackasyn.

- Configure tests for mikmod, however this lib is currently not used. Can be disabled.

- Configure tests for cppunit, however this is only needed for tests. Can be disabled.

- CS has a mandatory dependency on zlib. (Usually probably pulled in by one of the other deps, but maybe some has all USE flags disabled or so...)

- Building is done with jam; if you'd also install with that, you could shave a few seconds off configuring by passing --disable-make-emulation.

- The lighting cache files aren't generated: the 'cslight' command isn't found.
One way to address that is to invoke '${D}/usr/bin/cslight' instead of plain 'cslight'. 

- The docs take up 65M, maybe add a 'doc' use flag or so that toggles installing the docs? (There are targets for a more fine-grained installation: install_bin install_plugin install_lib install_include install_data install_config install_doc. Default is all of them. To exclude docs, you'd explicitly jam all of these except install_doc.)