Hi sdcc users and developers,

if you carefully looked to the SDCC Snapshot Build web page, you might noticed two new items: "Windows 64bit (experimental) (x86_64-w64-mingw32)" and "Windows 64bit package with installer (experimental) (x86_64-w64-mingw32-setup)".

Both contains the native 64 bit Windows compiled sdcc suite. The builds are done on Erik's cf-x86 amd64 Fedora 12 Linux machine, cross-compiled in mingw_w64 environment (libraries, header files, ...) with x86_64-w64-mingw32-gcc (GCC) 4.5.4 (prerelease). Regression test are ran on the same machine with wine64 and they all pass.

The zip packages sdcc-snapshot-x86_64-w64-mingw32-yyyymmdd-bbbb.zip are quite complete. The only remaining TODO is compilation of 64 bit readline5.dll and it's inclusion.

The setup package still needs some work:

   * I just noticed that it has to be renamed since the name is same as
     for 32 bit packages. The new name will probably be
     sdcc-yyyymmdd-bbbb-w64-setup.exe
   * Detection when trying yo install 64 bit package on 32 bit Windows
   * Proper installation in 64 bit registry and in 64 bit "Program
     Files". Currently it is incorrectly installed as 32 bit
     application in "Program Files (x86)" directory.
   * Already mentioned inclusion of 64 bit readline5.dll

Any reports of successful or unsuccessful installation & execution are welcome!

Thanks to Erik Petrich to upgrade cf-x86 to Fedora 12 (glibc 2.11 is required by brebuild mingw_w64) and to gcc, mingw_w64 and wine teams to make this possible.

Borut
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user

Reply via email to