From version 3.3.0 Ice is not distributed in files divided by languages. I think that it is the right step, because for example Java part of the Ice contains Ice Grid Admin GUI, which is usefull even if you are using only the cpp binding, the cpp part of Ice includes translation of slice language to other languages (so it is not only cpp binding), etc. So,i think it is better to have only one ebuild with use flags for language bindings instead of Ice,IceRuby,IcePy,... I am a developer of Ferda application (http://ferda.sourceforge.net/). It is an application which use the .NET and Java Ice bindings. I would like to create an ebuild for Ferda, but I am missing IceCS and IceJava bindings in the Portage. So if you do not agree that it is better to create only one ebuild, can you create ebuilds for IceCS and IceJava? At least I need from IceCS the iceboxnet application and the Ice Grid Admin GUI application form IceJava is very usefull for debuging. Thanks Reproducible: Always Steps to Reproduce:
Caleb, It looks like you have been doing all of the work for this package, so I'm forwarding this on to you to look at.
Hi Michal, Certainly, we can revise the ebuild to build/include bindings for each language based on use flags; it's just not something I've had the time to sit down and try to do. In addition, since I don't use anything but the CPP and Ruby bindings myself, I don't have a good way to test and verify that the ebuild is building/installing correctly. Alternatively, we could create IceCS/IceJava ebuilds as well. I'm not stuck on one way or another. If you want to take stab at making some of these changes, I'm happy to put it into portage.
Ok, I've rewritten the Ice ebuild and pushed it in my overlay here: http://git.overlays.gentoo.org/gitweb/?p=dev/dev-zero.git;a=tree;f=dev-libs/Ice;hb=HEAD It currently supports mono and python bindings. Java, ruby and php are going to follow in the next week. @caleb: It's more or less a complete rewrite and doesn't need patches anymore. It should therefore be more robust on version bumps. Furthermore some stuff gets installed to other dirs as recommended by upstream. It also features doc and example USE flags.
it looks ok to me, feel free to commit at will.
And what about bindings for Java? I'm not good in writing ebuilds so could you update it as you have done for c# and python? I also think Ice is in the wrong category, it's multilanguage stuff so maybe it should go to dev-libs or sth else...
I maintain the IceE ebuild and am really liking this clean-up for Ice, when will this be pushed?
Finally done. Except for the java and php bindings...
Any updates on this? PHP support would be nice. I can build it myself outside of portage, but my new ebuild isn't cooperating with me.
Created attachment 258579 [details] ebuild with php support Added PHP support. Builds for me with USE="ncurses php php_targets_php5-3 python".
No update on this in a long time. The ebuild I attached has been working for me. Update to 3.4.2 (released 2011/06/16) seems okay with just a ebuild file name change.
I can also verify that the ebuild provided by Mr. Pettey works properly. Both as provided, and if updated for version 3.4.2. It should be noted that there appears to be a typo on line 110: "use debug && OPTIONS"${MAKE_RULES}"..." should read "use debug && OPTIONS="${MAKE_RULES}... I'll attach my ebuild with the typo corrected.
Created attachment 291195 [details] Ice-3.4.1 ebuild with php support. (minor typo corrected)
Created attachment 295145 [details] Updated ebuild for nocxx/cxx USE change
Comment on attachment 295145 [details] Updated ebuild for nocxx/cxx USE change oops, uploaded the wrong file
Created attachment 295147 [details] Update to Ice-3.4.2, nocxx/cxx USE change, db-use eclass
Created attachment 295149 [details] fix debug typo
Created attachment 295161 [details] 3.4.2, debug typo and wrong variable name fixed, db-use eclass, nocxx>cxx USE change
Just wanted to say thanks for maintaining this ebuild :) I was in need of the IcePHP module, and it seems to have compiled, installed, and loaded (by apache/php) correctly on an otherwise stable amd64 machine.
Can we put the ebuld with php in portage? IcePHP is needed by many mumble web UIs because murmur (the mumble server) uses ice for configuration.
Created attachment 309643 [details] Ice-3.4.2 with EPREFIX Added EPREFIX as in bug 385567
(In reply to comment #20) > Created attachment 309643 [details] > Ice-3.4.2 with EPREFIX > > Added EPREFIX as in bug 385567 I've tried mucking about with this ebuild yesterday evening because I need the php bindings for a project i've been working on related to mumble admin plugin that has a dependency on IcePHP. I'm almost certain there's a sed error in src_configure() I tried emerging this ebuild in a local overlay but it errors out with sandbox violations and the ruby module will not build. I wound up building Ice with USE="-ruby" just to see if i could get this to build with php bindings however the sandbox violations still persisted.
Created attachment 319906 [details] Ice-3.4.2 build https://236264.bugs.gentoo.org/attachment.cgi?id=309643
While trying to see if I could get this to build the ruby module I figured why not "test" if RUBY_TARGETS="ruby19" would build so I edited the ebuild in my local overlay since ruby18 wouldn't compile the python module with USE="ruby". If your reading the build log i attached to this bug that's why rubt19 is in ruby targets. While I don't require the ruby components for my needs I'm sure this also qualfies as a bug for the attached ebuild. make[1]: Leaving directory `/var/tmp/portage/dev-libs/Ice-3.4.2/work/Ice-3.4.2/py/python' make: Leaving directory `/var/tmp/portage/dev-libs/Ice-3.4.2/work/Ice-3.4.2/py' make -j2 -C rb prefix="/usr" install_docdir="/usr/share/doc/Ice-3.4.2" install_configdir="/usr/share/Ice-3.4.2/config" embedded_runpath_prefix="/usr" LP64=yes OPTIMIZE=yes DB_FLAGS=-I/usr/include/db4.8 install_rubydir="/" install_libdir="/" ruby18: no such file to load -- auto_gem (LoadError) ruby18: no such file to load -- auto_gem (LoadError) ruby18: no such file to load -- auto_gem (LoadError) make: Entering directory `/var/tmp/portage/dev-libs/Ice-3.4.2/work/Ice-3.4.2/rb' making all in src ruby18: no such file to load -- auto_gem (LoadError) ruby18: no such file to load -- auto_gem (LoadError) ruby18: no such file to load -- auto_gem (LoadError) make[1]: Entering directory `/var/tmp/portage/dev-libs/Ice-3.4.2/work/Ice-3.4.2/rb/src' making all in IceRuby ruby18: no such file to load -- auto_gem (LoadError) ruby18: no such file to load -- auto_gem (LoadError) ruby18: no such file to load -- auto_gem (LoadError) ruby18: no such file to load -- auto_gem (LoadError) ruby18: no such file to load -- auto_gem (LoadError) ruby18: no such file to load -- auto_gem (LoadError) ruby18: no such file to load -- auto_gem (LoadError) make[2]: Entering directory `/var/tmp/portage/dev-libs/Ice-3.4.2/work/Ice-3.4.2/rb/src/IceRuby' x86_64-pc-linux-gnu-g++ -c -I. -I.. -I../../../cpp/include -I -I -march=core2 -mtune=core2 -O2 -mfpmath=sse -fomit-frame-pointer -mssse3 -msse4.1 -pipe -m64 -Wall -D_REENTRANT -fPIC -DNDEBUG Connection.cpp x86_64-pc-linux-gnu-g++ -c -I. -I.. -I../../../cpp/include -I -I -march=core2 -mtune=core2 -O2 -mfpmath=sse -fomit-frame-pointer -mssse3 -msse4.1 -pipe -m64 -Wall -D_REENTRANT -fPIC -DNDEBUG Communicator.cpp In file included from ./Connection.h:13:0, from Connection.cpp:10: ./Config.h:29:18: fatal error: ruby.h: No such file or directoryIn file included from ./Communicator.h:13:0, from Communicator.cpp:10: ./Config.h:29:18: fatal error: ruby.h: No such file or directory compilation terminated. compilation terminated.
After some further research it appears that IceRuby built with USE="ruby" depends on rubygems built with RUBY_TARGETS="ruby18" which may explain my build error. I previously "upgraded" my server to ruby19 excluding ruby18 more or less for the sole purpose of future proofing against the depreciation of ruby18. Noted this situation has me curious of Ice supports ruby19
(In reply to comment #24) > After some further research it appears that IceRuby built with USE="ruby" > depends on rubygems built with RUBY_TARGETS="ruby18" which may explain my > build error. > > I previously "upgraded" my server to ruby19 excluding ruby18 more or less > for the sole purpose of future proofing against the depreciation of ruby18. > Noted this situation has me curious of Ice supports ruby19 Here's a (somewhat old) thread possibly related: http://www.zeroc.com/forums/bug-reports/4776-3-4b-ruby-bindings-fail-build.html
Hi guys I have a problem with PHP_TARGET, the ebuild want version 5.3 but i have 5.4 and want to keep it. Here is a topic I have made on gentoo forums. http://forums.gentoo.org/viewtopic-t-948024.html
Created attachment 359976 [details] Ice-3.4.2.ebuild (EAPI=5 and builds with PHP 5.3, 5.4 and 5.5)
Created attachment 359978 [details, diff] Ice-3.4.2-php54.patch
Created attachment 359980 [details] Ice-3.5.0-r1.ebuild (EAPI=5 and builds with PHP 5.4 and 5.5)
Did a lot of work the get the PHP bindings running. It would be great if this could be added to the official portage tree. Every webinterface for a Mumble-server needs this bindings.
(In reply to Thomas Oettli from comment #29) > Created attachment 359980 [details] > Ice-3.5.0-r1.ebuild (EAPI=5 and builds with PHP 5.4 and 5.5) died while building with the python useflag: * python2_7: running building make -j2 -C py-python2_7 prefix="/var/tmp/portage/dev-libs/Ice-3.5.0-r1/image//usr" install_docdir="/var/tmp/portage/dev-libs/Ice-3.5.0-r1/image//usr/share/doc/Ice-3.5.0-r1" install_configdir="/var/tmp/portage/dev-libs/Ice-3.5.0-r1/image//usr/share/Ice-3.5.0/config" embedded_runpath_prefix="/usr" LP64=yes OPTIMIZE=yes DB_FLAGS=-I/usr/include/db4.8 make: *** py-python2_7: No such file or directory. Stop.
(In reply to kisak42 from comment #31) > (In reply to Thomas Oettli from comment #29) > > Created attachment 359980 [details] > > Ice-3.5.0-r1.ebuild (EAPI=5 and builds with PHP 5.4 and 5.5) > > died while building with the python useflag: > > * python2_7: running building > make -j2 -C py-python2_7 > prefix="/var/tmp/portage/dev-libs/Ice-3.5.0-r1/image//usr" > install_docdir="/var/tmp/portage/dev-libs/Ice-3.5.0-r1/image//usr/share/doc/ > Ice-3.5.0-r1" > install_configdir="/var/tmp/portage/dev-libs/Ice-3.5.0-r1/image//usr/share/ > Ice-3.5.0/config" embedded_runpath_prefix="/usr" LP64=yes OPTIMIZE=yes > DB_FLAGS=-I/usr/include/db4.8 > make: *** py-python2_7: No such file or directory. Stop. Could you post some more information about that? Just merged Ice-3.5.0-r1 with the following USE flags: USE="ncurses python -debug -doc -examples -mono -php -php_namespaces -ruby {-test}" PHP_TARGETS="-php5-4 -php5-5" PYTHON_TARGETS="python2_7 (-pypy2_0) -python2_6" RUBY_TARGETS="ruby18" On my system, it worked perfectly.
Created attachment 360010 [details] Ice-3.4.2.ebuild (EAPI=5 and builds with PHP 5.3, 5.4 and 5.5) PHP_TARGETS is not mandatory anymore
Created attachment 360012 [details] Ice-3.5.0-r1.ebuild (EAPI=5 and builds with PHP 5.4 and 5.5) PHP_TARGETS is not mandatory anymore
Friendly reminder: Any news on this after one year?
Created attachment 420890 [details, diff] Ice-3.5.1.ebuild (EAPI=5 and builds with PHP 5.4, 5.5 and 5.6)
I have ported the patch to the version 3.5.1
Comment on attachment 309643 [details] Ice-3.4.2 with EPREFIX obsoleting old ebuild
Pull request on GitHub: https://github.com/gentoo/gentoo/pull/1332
php has been in since a few years so i changed the summary. the java component is gradle based so im not sure how to proceed here. the only package i know of that uses gradle is dev-java/openjfx. and im not really sure if implementing it like that is the right call.
