I mentioned in a recent post that gcc is a long time item on our wish list
{ dgk gsf jkf } simply haven't had the time to dedicate to thatso at the moment if you want to build you must first download and install the latest "free to download but not opensource" msvc c++ compiler using ms instructions (all but one c++ file in uwin is c) if you have a windows machine you have already signed on to proprietary software mcvs will just be one more thing on the heap once you do that and get a complete build you should be in shape to play with mingw-cc or maybe clang the issue will mainly be getting open-source headers and compile time .lib files for the corresponding ms .dll files and possibly tweaking them with 64 vs 32 bit ifdefs if anyone does try this, start with a simple hello world before attempting posix.dll (posix.dll being the uwin posix<=>win32 layer) also, even on 64 bit the windows api is called win32, so don't lose your mind trying to make sense of that -- see the "32 and 64" link under the "uwin" nav on the download page On Sat, 1 Jun 2013 10:44:05 +0200 Simon Toedt wrote: > On Sat, Jun 1, 2013 at 6:22 AM, Glenn Fowler <[email protected]> wrote: > > > > I don't recall specific problems reported on building uwin > We only started trying last week. We didn't report anything yet > because we thought we might miss a simple detail. > > > > also, I don't know what "the easy way" means > Compile within UWIN itself via ssh only using the gcc compiler would > be a good start. We like to do it fully scripted without involving > hitting buttons on a GUI. > > the posted instructions are the way we do it > Which appears to rely on a specific Windows compiler version or > whatever is the damn reason it doesn't work. We try again when the > next UWIN alpha is out. > Glenn, please understand we like to join development and help you out. > Right now we can't do that. > Simon _______________________________________________ uwin-users mailing list [email protected] http://lists.research.att.com/mailman/listinfo/uwin-users
