So Eclipse. [Moved, Because apparently I'm doing it wrong(tm)]
-
It's now 2014, and you have a general file system importer. Cool.
Now, CAN YOU PLEASE FUCKING LET ME CREATE A NEW PROJECT AT THE TIME OF IMPORT INSTEAD OF LETTING ME NAVIGATE TO MY FILES THEN TELLING ME TO FUCK OFF?
-
CLOSED WONTFIX YOU'RE DOING IT WRONG™.
-
Of note
This project was also exported originally using eclipse export project to file system.
-
Such a bad software design that I see so often. We'll let you dig your hole, and not tell you to put down the shovel.
-
You're Doing It Wrong™
You should've done Import > Existing Projects Into Workspace
-
That worked better.
Now for your next trick, getting a 32 bit app running on a 64 bit java installation / 64 bit machine! <I've actually got this piece under control, thanks though.>
-
... isn't Java run through a VM? Why the fuck would bit-ness matter?
-
Native DLLs?
-
It's actually the 32 bit JDBC driver to connect to MSSQL. The application itself is fine otherwise.
-
Ok that makes some sense, since it's undoubtedly running native code.
-
So you get the 64-bit driver? That seems...easy to solve.
-
As @boomzilla said: 64-bit driver (or changing to the 32 bit jvm)
-
Changing to 32 bit jvm for eclipse just means downloading the x86 version, right? (I've opened this project exactly one time in the last two years, and my normal environment is .net)
-
Of note
I generally expect various WTFery from Eclipse anyway, so this would probably just be below my enragement threshold.
-
Changing to 32 bit jvm for eclipse just means downloading the x86 version, right? (I've opened this project exactly one time in the last two years, and my normal environment is .net)
Probably. In my limited experience Java apps don't seem to care the bitness of the JVM. Minecraft certainly doesn't. But I'll add my voices to the people who suggest a 64-bit driver first, modulo obvious disqualifiers like "it's a buggy beta".
-
But I'll add my voices to the people who suggest a 64-bit driver first, modulo obvious disqualifiers like "it's a buggy beta".
The question is whether the program is meant to continue to be just a 32-bit app or if it needs to support 64-bit.
You'll want both the JRE and the JDK, of course, for development.
-
Using Eclipse was your first mistake.
-
App has to be a 32 bit app since it will be used on 32 bit citrix environment, JRE - JDK - got it. Off I go.
-
Yeah, this app was created during extreme business politics, and java apps were the only things that could be created that didn't need to be installed through the process. (No install required at all)
-
Solved: Just needed to do this for the jdbc auth dll file
-
Minecraft certainly doesn't.
No, but if you want mumble to put an overlay on your Minecraft while mining with friends, you have to use the 32-bit JVM. So annoying.
-
I know you're not talking about regular mods because that's not true for them. What's an overlay in this context?
-
mining with friends
Also, I wish you hadn't used those three words, because you probably just gave Zynga an idea.
-
I presume it's a Steam-like overlay.
Or if you've never used Steam, maybe you know Raptr? Or if you've never used that, *shudder* Games for Windows Live runs one.
-
You know what Mumble is, yes? It can put an overlay on other programs, which is useful when gaming. Like so:
http://i.imgur.com/OV9SFOk.png
This is at runtime, without modding the game.
I presume it's a Steam-like overlay.
Or basically what he said.
-
I might have heard of Mumble. The fact that you mentioned it's external to Minecraft explains why it has to be 32-bit just fine.