On April 27, 2003 08:15 pm, Troy Rollo wrote:
The only problem in the head code appears to be in the linker, which it turns out has a problem when it's told there's 3GB of user address space.
This is pretty cool. I've added you to the Fun page: http://63.138.153.104/wine/Wine-Fun.html#source
Few questions: * Do you build on Windows? * Could we run bcc in Wine on Linux to build on Linux using bcc? * How far do you get? Do you actually get an executable? * Does it run? * What are the steps you need to take? A concise list of instructions would be nice :) I can post it on the Fun page, so other can play with it was well.
On Mon, 28 Apr 2003 14:23, Dimitrie O. Paun wrote:
Few questions:
- Do you build on Windows?
Until now, I have developed on Windows, but I will be continuing to target Windows from Linux using Wine to support the build environment, and possibly for testing of the application itself, together with plex86 or Bochs VMs as needed for testing under the target OS.
- Could we run bcc in Wine on Linux to build on Linux using bcc?
Yes, this is what I'm doing.
- How far do you get? Do you actually get an executable?
Yes. It produced (among others) an executable of 9402368 bytes (not including debugging information which is in a separate file) from 948 object files (not including libraries).
- Does it run?
Not only does it run, it appears to work OK in wine.
- What are the steps you need to take? A concise list of instructions would be nice :) I can post it on the Fun page, so other can play with it was well.
The setup of the Borland C compiler was quite straight-forward - I copied it over from an existing Windows installation. This was necessary rather than a full install because we use modified header files, but it appears the installation from the self-extracting executable won't run, so copying over from a copy installed on native Windows is necessary.
Then I put it in the PATH, checked out the code and built using exactly the same procedure I used to use under Windows.
On Tue, 29 Apr 2003, Troy Rollo wrote:
On Mon, 28 Apr 2003 14:23, Dimitrie O. Paun wrote:
Few questions:
- Do you build on Windows?
Until now, I have developed on Windows, but I will be continuing to target Windows from Linux using Wine to support the build environment, and possibly for testing of the application itself, together with plex86 or Bochs VMs as needed for testing under the target OS.
Sorry, I misunderstood you. I thought you were building *Wine* with bcc, and I did not understand how you managed to get a running binary. :)
What version did you specify in ~/.wine/config [windows] version?
win2k
I guess you ran in non NT mode. And I guess your change will do havoc to programs needing NT mode (like Xilix ISE). Probably the limit has to be set in dependance of the version emulated.
The limit doesn't depend on version, at least not in terms of what you probably mean by version. Windows only offers a 3GB user address space on its "higher end" editions, such as Advanced Server. Some applications can't deal with this. Yes, technically this is a bug in the application, but it's a bug that would not be triggered when running on a genuine Microsoft workstation operating system.
And yes, it should be configurable, or perhaps Wine should be capable of detecting which apps can deal with a 3GB user address space (as apparently executables can be marked to declare this), but as long as it's not configurable, and Wine's not capable of detecting this, it seems to me that the 2GB limit applicable to the desktop operating systems is the correct one.
Troy Rollo wrote:
And yes, it should be configurable, or perhaps Wine should be capable of detecting which apps can deal with a 3GB user address space (as apparently executables can be marked to declare this), but as long as it's not configurable, and Wine's not capable of detecting this, it seems to me that the 2GB limit applicable to the desktop operating systems is the correct one.
Well, this depends on what you mean by "desktop operating systems" ;-)
The Win95 based OSes all have a 3GB user space, and in fact *require* it if you want to use native DLLs, because the system DLLs need to be located at > 2GB ...
Bye, Ulrich
-
Dimitrie O. Paun -
Dimitrie O. Paun -
Troy Rollo -
Ulrich Weigand