From: Nicolas V. <nve...@cl...> - 2005-09-27 17:39:15
|
Hi Ren=E9 Ren=E9 Kanters wrote: > Hi, > > the peculiar thing is that I happened to have gettext and all that =20 > already installed in /sw/bin, which is in my path (version 0.10.40 =20 > [found using the option -V] through Fink commander) but the check =20 > executables in the build answers that they are not available... I =20 > installed the 0.13 version myself and the install puts them in /usr/=20 > local/bin, where they aren't found either. > > So it seems like the ant1.6.5 (which seems to be the one that Eclipse =20 > has built-in) does not look at my path.... > When I add a shortcut (ln -s) to the executables in the basedir (.) =20 > directory of Jmol, and add the resolveexecutable=3D"true" attribute to = =20 > the 'apply' and 'exec' elements the build works for me. Since that is =20 > not the best solution for everyone, I don't think I should commit =20 > this... That's really ennoying. Do you see the same behaviour running Ant outside Eclipse ? (You may=20 need to install Ant itself) We should try to find a solution working for eveyone. A few things you can try with the <exec> task in <check-executables> : - add the attribute searchpath=3D"true" - add the attribute vmlauncher=3D"false" - replace executable=3D"xgettext" by executable=3D"/usr/local/bin/xgettex= t" I think the last one should work (I don't see why it shouldn't). If so, a simple fix would be to : - add a property "gettext_path" at the beginning of build-i18n.xml, set=20 to an empty string. - use "${gettext_path}xgettext" instead of xgettext everywhere. The above modifications could be committed under CVS. Then since you are using Eclipse : - right click on build-i18n.xml - select Run As / Ant Build ... - select the Main tab - in the Arguments field, add -Dgettext_path=3D/usr/bin/local/ You may have to do this also for build.xml > > On a possibly related note: > I noticed that in the build-doc-i18n.xml the <exec os=3D"" > setup is =20 > used to execute the xml2po.sh and things like that depending on the =20 > OS. This one did not work for me because I do not have Linux nor =20 > Windows XP. So I added a copy of the Linux one and tested for Mac OS =20 > X. That seems to want to run the xmol2po.sh, but I get an executable =20 > error. I had to change the execute flag on the .sh file to get that =20 > to run (can that be update in the repository so that it comes over =20 > with the executable bit set?) but the import libxml2 is failing for =20 > me there... So it seems that the Jmol project is starting to rely =20 > more and more on external things, possibly their versions, and as a =20 > result the require a more complex environment for the people that =20 > (try to) contribute to maintain (can anybody say 'dependencies' :-). =20 > I am not complaining, just observing here.... I agree that the needed environment should be kept as simple as possible. As I said in an other post, gettext tools are not required unless you=20 want to make a distribution with the translations. It adds some dependencies to do a full build, but the translation=20 mechanism is much easier. If you don't need a full distributions with translations, the build will=20 work even without gettext tools. For the document part (build-doc-i18n.xml, xml2po.sh, ...), I don't know. I haven't looked at it. I think it's not finished. > > I did find some libxml2 information for Mac users (not just =20 > Windows...) at http://jamesclarke.info/notes/InstallLibxml2 but do =20 > not have the time right now to go through all that. > > At least my regular build works (for now)...=20 If I find enough time, I will try to look at this part to see what can=20 be done. Nicolas |