[EMAIL PROTECTED] schrieb:
> along those lines, has anyone been successful at running the Keil
> compiler .exe pieces under Wine? i did the experiment at one point,
> and got the compiler to run, but since i hadn't configured a license
> key (i didn't want to disturb my existing license, and i only had one,
> of course) the compiler wouldn't create object files. i'm curious as
> to whether anyone else has run it this way and gotten a working executable.
Hi,
I have to prepend that the information I'm giving here is
sketchy and in parts almost certain to be either misleading
or plain wrong. Sorry for that.
If you read on, expect nothing.
There are at least three scenarios of wine usage:
a) using wine (in the sense of wine only)
b) using wine making use of DLLs of an existing windows
installation
c) using wine making use of DLLs of an existing windows
installation and having rw access to files/directories
or the root filesystem of an existing windows installation.
(please excuse if my wording does not match a windows
mindset)
If you fear disturbing an existing Keil license you're probably
using c). Which might be dangerous (no intention to spread FUD).
While using a) is in my view preferred you could safely use b)
if you mount the windows installation read-only.
I cannot comment on b) or c) because I do not have installed
a reasonably recent Windows installation at home (ie. no Vista,
no XP, no Win2k).
I had some success using scenario a) with an ancient evaluation
version (7.01 ek51v701.exe) of Keil downloaded here:
ftp://ftp.phytec.de/pub/product/Keil_IDE/C51/
What did I do?
I renamed my .wine folder
I ran winecfg clicking through all its defaults
I ran wine ek51v701.exe
there was a complaint there.
I ran cp ek51v701.exe .wine/drive_c/windows/system32/
(knowing that this is not what I'd really want to do)
I ran wine ek51v701.exe again and the installation completed
I then ran wine .wine/drive_c/Keil/C51/BIN/c51.exe c/main.c
and arrived at:
---8<------
C51 COMPILER V7.01 - SN: Eval Version
COPYRIGHT KEIL ELEKTRONIK GmbH 1987 - 2002
C51 COMPILATION COMPLETE. 0 WARNING(S), 0 ERROR(S)
--->8------
with a main.OBJ and main.LST file being generated.
I did not check either the linker lx51.exe
or object to hex converter oh51.exe (which both might
just work fine within the given scenario)
But why should I (or anyone) give support for a competing
compiler that
1) runs on a host platform I do not like (Windows)
and which does not provide the functionality I'm
accustomed to.
2) runs on a host platform which I (at home) do not use.
While having been forced to pay for Windows licenses I did
not use (or even intend to use) them. The money feels like
stolen.
3) does not run on my host system which the competing
compiler vendor does not support?
As "there should be no tool chain lock-in anywhere" I think
giving some loose ends might not hurt, but I would not like
to post follow ups. (If someone feels safe about the above
stuff, and thinks it matters there is a wiki)
Greetings,
Frieder
PS: Host was openSUSE 11.0 if that matters (it should not)
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
