denormgen is a tool for generating normal/height maps from high resolution meshes for use in games or 3d applications. is based on FOX toolkit and provides a python export script for Blender3D. allows previewing and merging of normal maps. some user suggested that i might create an ebuild for this tool so here it is. i hope this is all done correctly this way as it is my first ebuild suggestion.
Created attachment 87592 [details] ebuild for 1.4 release build should be stable as i tested it on 2 different pcs with different setup. but i marked it ~x86 as i don't know how stableness is handled around here.
well, new ebuilds should be marked unstable, however actually gcc-4.1 is marked unstable too and this mean fox must be version 1.6.x to emerge (older ones doesn't compile with gcc-4.1). Then, fox-wrapper actually doesn't support WANTS_FOX="1.6" (need just to add this to the fox-wrapper script)....
(In reply to comment #2) > well, new ebuilds should be marked unstable, however actually gcc-4.1 is marked > unstable too and this mean fox must be version 1.6.x to emerge (older ones > doesn't compile with gcc-4.1). no problem. the configure should be 1.6 aware using fox-config ( unless this changed, what i do not assume ). > Then, fox-wrapper actually doesn't support WANTS_FOX="1.6" > (need just to add this to the fox-wrapper script).... what's fox-wrapper?
fox-wrapper is the gentoo script that care about symlinking /usr/bin/fox-config with /usr/bin/fox-config-1.4 , 1.5 ,1.6 .....
forgot to mention. i placed it under 'media-gfx/denormgen'. sounds to me to be a logical place for that tool. though first about placing it under he game-utils, but it's for more than only games in the end. so is the dependency on FOX now a problem or not?
noticed that assigned to is set to "Default Assignee for New Packages <maintainer-wanted@gentoo.org>" ... does this mean you simply wait for somebody taking over maintaiance of the package? as if this is the only thing missing for it getting included i can put my hands on this one.
This means some waiting is needed. There are a couple of causes: 1) fox is actually not in portage for unstable branch systems (>=fox-1.6 is needed to emerge it with gcc-4.x, but is not in portage) 2) the script installation directory is an issue, cause still there isn't a fixed directory for blender scripts (2.42 installs them in /usr/lib/blender/scripts/ , but with 2.42a you will find them in /usr/share/blender/scripts/ .....) so some kind of "mechanism" to retrieve where the script should be installed is needed. (actually I know just 2 ways: a- "equery f blender | grep 3ds_export.py" that would depend on gentoolkit, b- "locate 3ds_export.py" that's depending on locate implementation.... if anyone has ideas on how to get the script directory with no dependancies or system-implicit dependancies, please tell.... )
Created attachment 93020 [details] ebuild not installing into blender concerning the problem with the blender script directory i only have an idea how to solve it if the ebuild system allows for probing existance of directories/files. i expect though this not to be the case. i made now a modified version of the ebuild installing the script into /usr/share/denormgen-1.4/scripts . this way the script can later on be linked to the blender script directory once we have a working detection schema or the user can link it anywhere he wants by himself.
Created attachment 93033 [details] sunrise fixes some fixes for sunrise
It seems that this package is no longer in Sunrise.
