![]() ![]() Assemblers aren't complex at all and the entire idea is that they're one of the lowest programs you can write so you aren't punching in machine code. ![]() I know that XP works fine, but to completely cut out a lineage of pre-XP NT OSes was just bad manners on GNU's part. I thought I must've missed something when I looked over the news article, guess it was the BinUtils. This ide only supports above WinXP as far as I know. I would suggest "Auld Lang Syne" as the music to accompany your windows 2000. So I don't know how windows 2000 will fare. My old windows 98 failed with freebasic, I tested a couple of years ago. (This has nothing to do with freebasic at this stage)īut my old Win XP has no problems, my old XP (32 bits) does fine with freebasic 32 bits. If you set the bin folder on your system path you will have working gcc, g++, fortran and all the other utilities on a command window to use straight away. ![]() If you expand either the 32 bit one or the 64 bit one you will get about 500 MB of files which are in effect a working MinGW distro. The MinGW-w64 toolchains used for the main win32/win64 builds can be found here: You can get these binutils from the news thread of the forum. If %errorlevel% NEQ 0 (type Err.%2.log) else (type Norm.%2.log) Set direct=C:\DOCUME~1\ADMINI~1\Desktop\DEVELO~1\FREEBA~1\Projects\%project%Įcho Compiling %1\%folder% with %name%.Įcho Debug compilation for console application(T%3).Įcho %fb% -x "%direct%\built\%name%.exe" -i \shared\ -map "%direct%\built\%folder%.txt" -v -export -s console -O 0 "%direct%\%folder%\build.bas" 1>Norm.%2.log Set fb="C:\Documents and Settings\Administrator\Desktop\Development\FreeBasic\FBC\fbc.exe" REM OLD set fb="C:\Documents and Settings\Administrator\Desktop\Development\FreeBasic\FreeBASIC-1.09.0-winlibs-gcc-9.3.0\fbc32.exe" Code: Select all title Batch Compiler(Type %3) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |