On 11/5/07, Andreas Schöneck <firstname.lastname@example.org> wrote:
> D.J. Heap wrote:
> > On 11/5/07, Andreas Schöneck <email@example.com> wrote:
> >> Hello!
> >> Has anyone compiled a full set of x64 binaries? I recently tried to
> >> compile but I failed (some strange errors while compiling openssl). I
> >> don't even know whether i get 32-Bit or 64-Bit executables when using
> >> the automated build scripts, though the SDK's command promts tells me
> >> that target is Vista Debug x64.
> >> The problem is that I need x64 binaries to get the JavaHL interface of
> >> Subclipse to work because I use an x64 Version of Eclipse.
> >> It seems that nobody is interested in supporting 64-Bit, nevertheless
> >> there are 64-Bit OSes as well as even a 64-Bit Eclipse!
> >> What I did was to use some binaries from an OpenSLL x64 installer as
> >> well as the files that ship with TortoiseSVN. But the error message in
> >> Eclipse remains the same, regardless of what files are placed inside
> >> Eclipse base directory.
> >> Since I read some posts regarding x64 compiling I think some people
> >> compiled binaries successfully.
> >> So I would need either all the required binaries for Windows (I use an
> >> Intel CPU) or perhaps VS2005 solution/project files (or even better: a
> >> complete archive/project which I can unpack and start compiling in VS) -
> >> I mean, if anyone has done this before and wants to share his/her
> >> project/artifacts.
> > Trunk has some support for x64 when using VS2005. I can't remember
> > for sure if I tried building JavaHL, but I don't know why it wouldn't
> > work.
> > Note that you have to using the -t vcproj and --vsnet-version=2005
> > arguments to gen-make.py to get the VS2005 solution and projects
> > files. Then make sure you choose the x64 platform targets. You'll
> > also have to make sure to build the dependencies for x64 as well,
> > which is trickier, as I recall -- I had to google around a bit to get
> > the info to do that for each of them.
> > DJ
> Thanks DJ!
> After spending the whole afternoon from 4pm to now (8pm) I gave up
> trying. Though OpenSSL compiles now (I had to use VS command prompt not
> WinSDK command promt) with warnings (removed /WX switch from makefile) I
> cannot compile libjavahl or the svn client. Some of the libraries built,
> some not, other after modifying their makefiles. A major problem was
> that CL could not find sqlite3.h so I had to correct the path in the
> file (nothing else worked), then the Linker did not find sqlite3.lib so
> I built one from the def-file (but the dll is not x64). And so on.
> I was to add many lib files into the linker options for libjavahl,
> finally there were errors about imports starting with __impl.
> Since I don't know whether this leads to anything I hope that there will
> be x64 binaries available from the official site shortly.
Why don't you just run Eclipse 32-bit? The 64-bit JVM is generally
much slower and I cannot imagine why you would need a 4GB Heap size
when running Eclipse. You get no benefits from running it 64-bit.
That is one of the reasons Eclipse itself has been slow to add an
official 64-bit version. The need is just fairly minimal.
TortoiseSVN has to be 64-bit because on a Windows 64-bit installation
the Explorer shell is 64-bit.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Nov 5 20:42:10 2007