Date: Sun, 09 Sep 2007 23:14:33 -0400 From: Daniel Rucci <dan@rucci.org> To: Mike Bowie <mbowie@buzmo.com> Cc: freebsd-eclipse@freebsd.org Subject: Re: eclipse 3.3.0 Message-ID: <46E4B699.8020505@rucci.org> In-Reply-To: <46E308C1.8040501@buzmo.com> References: <20070907204747.GA48113@misty.eyesbeyond.com> <46E1BBFA.5000501@buzmo.com> <20070908.111953.41626495.ken@tydfam.jp> <20070908.132508.71086449.ken@tydfam.jp> <46E239AF.7000702@buzmo.com> <46E308C1.8040501@buzmo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Bowie wrote: > Mike Bowie wrote: >> Ken Yamada wrote: >>> Sorry one more... >>> >>> The instruction says; >>> : : : >>> # In the build.xml >>> >>> * update the compilelibs property in the init target to reflect >>> the new architecture >>> * update the compilelibs target to reflect the new architecture >>> >>> # Run the build using "build -compilelibs" to force the recompilation >>> of the native libaries >>> : : >>> >>> However, I cannot find any <property name="compilelibs" ...> in >>> original build.xml in the top directory. >>> >>> What should I do for this? >>> >>> >> Evening all, >> >> My (rather rushed) attempt at building under diablo-jdk1.5 was not >> successful... I didn't really look into it though, as my fresh jdk1.6 >> build finished about the same time; which was of significantly greater >> interest. >> >> I managed to build the port at it stands on a machine at the office >> and here at home, (6.2R and 6.1-RC1 respectively) both to the point of >> displaying the loader error Ken reported earlier. A quick google >> found me a few similar problems and copying the loader library from >> the build to the install seemed to progress things a little. I was >> about to post my findings when I received Ken's musings, which made >> mine rather insignificant! ;-) >> >> Responding to your last point Ken, so far I'd have to agree... I can't >> find more than two instances of compilelibs in build.xml; one defining >> the target, the other referencing it as a dependency of the "run" >> target. It doesn't seem to make much sense. >> >> I'll keep poking around with it over the weekend if I find some time. >> >> Cheers, >> >> Mike. > Ken, > > I've been using the build from last night actively for about six hours > now with the PHPeclipse plugin and it's been working very well; nothing > unusual to report at all. > > Perhaps someone with a bit more Java knowledge can comment on the > warnings generated and someone closer to the Eclipse release team might > be able to resolve the confusion with build.xml. (Although I'm still > asking around and digging.) It may just be that the file wasn't updated > to reflect changes for the 3.3 release... the verbiage between the 3.2 > and 3.3 versions is almost identical, except version numbering. Which warnings are you curious about? I've spoken with a friend at ibm (not release team, but builds eclipse daily) and 100,000s of warnings is the norm. > > All in all, I'd have to say congratulations to Ken and Dan for a > successful port! I'll be running it on both my work machines and will > report in if anything comes up... and will keep an eye on the list. > > Nice work chaps! > > Cheers, > > Mike.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46E4B699.8020505>