From: <rka...@ri...> - 2005-09-28 00:26:50
|
Hi Nico, I replied to Daniel's message regarding this a bit earlier. =46rom what =20= he wrote and the test he suggested, it looks like the problem stems =20 from Eclipse. I just retrieve the original build files from CVS, and ant (my =20 version in OS X is 1.6.2) works with the original CVS build-i18n.xml =20 file. It is just Eclipse that doesn't seem to know my path. Since you =20= are the Eclipse guru, maybe you know where I may have a setting wrong =20= there... The -Dgettext_path=3D/usr/local/bin/ method you suggest with the =20 modification in the build-i18n.xml file does indeed work. So I could upload this modification to the xml file, but on the other =20= hand, I feel like Eclipse should be able to do the right thing from =20 the get go (without having to change things that do work for other =20 people). I assume that your install of eclipse id not giving you these =20 problems, so it may be just me... Ren=E9 On Sep 27, 2005, at 1:29 PM, Nicolas Vervelle wrote: > Hi Ren=E9 > > Ren=E9 Kanters wrote: > > >> Hi, >> >> the peculiar thing is that I happened to have gettext and all =20 >> that already installed in /sw/bin, which is in my path (version =20 >> 0.10.40 [found using the option -V] through Fink commander) but =20 >> the check executables in the build answers that they are not =20 >> available... I installed the 0.13 version myself and the install =20 >> puts them in /usr/ local/bin, where they aren't found either. >> >> So it seems like the ant1.6.5 (which seems to be the one that =20 >> Eclipse 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" =20 >> attribute to the 'apply' and 'exec' elements the build works for =20 >> me. Since that is not the best solution for everyone, I don't =20 >> think I should commit this... >> > > That's really ennoying. > Do you see the same behaviour running Ant outside Eclipse ? (You =20 > may 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/=20 > xgettext" > > 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, =20= > set 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 =20= >> is used to execute the xml2po.sh and things like that depending =20 >> on the OS. This one did not work for me because I do not have =20 >> Linux nor Windows XP. So I added a copy of the Linux one and =20 >> tested for Mac OS X. That seems to want to run the xmol2po.sh, =20 >> but I get an executable error. I had to change the execute flag =20 >> on the .sh file to get that to run (can that be update in the =20 >> repository so that it comes over with the executable bit set?) =20 >> but the import libxml2 is failing for me there... So it seems =20 >> that the Jmol project is starting to rely more and more on =20 >> external things, possibly their versions, and as a result the =20 >> require a more complex environment for the people that (try to) =20 >> contribute to maintain (can anybody say 'dependencies' :-). I am =20 >> not complaining, just observing here.... >> > > I agree that the needed environment should be kept as simple as =20 > possible. > > As I said in an other post, gettext tools are not required unless =20 > you 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 =20= > will work even without gettext tools. > > For the document part (build-doc-i18n.xml, xml2po.sh, ...), I don't =20= > 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 =20 >> do not have the time right now to go through all that. >> >> At least my regular build works (for now)... >> > > If I find enough time, I will try to look at this part to see what =20 > can be done. > > Nicolas > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, =20 > discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Jmol-developers mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-developers > |