FB/Win32/MSYS compilation docs fixed

jonathanbrickman0000 · Posted: Apr 09, 2006 0:50 Post subject: FB/Win32/MSYS compilation docs fixed

They appear to be fixed. If anyone finds a problem, please post it here. Also, if anyone knows how to add /mingw/lib to the standard linker path, or could add it to the standard CVS, that would be very helpful!

Sisophon2001 · Master

jonathanbrickman0000 · Posted: Apr 09, 2006 4:04 Post subject:

Actually, /lib/mingw will be /lib/mingw on any working MSYS installation; gcc/MSYS requires it, and MSYS sets up its own virtual paths (forward slashes only) in addition to Windows-standard. Ditto Cygwin, to an extent differently (no Windows-standard, somewhat different tree, but /lib and /lib/mingw are still there).

fbc is using its own supplied ld, which does not know about the standard MSYS or Cygwin paths.

I found the .x file you pointed out; I think that is the way. It is a standard ld linker script, and so I might be able to add a line to its end to add /lib/mingw (no drive letter, forward-slashes) to the standard Win32 FB ld search path. But I would appreciate it if someone experienced in FB ld scripts would do it and put it in CVS; I studied that script file, and it's a language all its own.

Sisophon2001 · Master

Did you look at the paths ld searches using ld --verbose?

This is the default search path of the linker that comes with FreeBASIC.

SEARCH_DIR("/mingw/mingw32/lib"); SEARCH_DIR("/mingw/lib"); SEARCH_DIR("/usr/local/lib"); SEARCH_DIR("/lib"); SEARCH_DIR("/usr/lib");

The Script file adds one additional search path.

SEARCH_DIR("lib");

I don’t have any problem building the compiler with MSYS, so what problem are you seeing?

Did you copy libmingwex.a into your FB lib directory?

Garvan

jonathanbrickman0000 · Posted: Apr 09, 2006 19:58 Post subject:

Garvan, that's it. Easy as pie, works great. I should have thought of that, simply because FBC comes with its own ld.exe. MSYS procedure adjusted; Cygwin shortly.

DrV · Site Admin

I just read the procedures now, and it appears that you are building the compiler before rtlib, which means that the new fbc will still be linked with the old rtlib. If you want to have the latest fbc linked with the latest rtlib, you should build the rtlib first, then the compiler. To be extra safe (in case some part of the rtlib <-> compiler interface changes drastically), you could rebuild the compiler first as is done now, then again after building the new rtlib.

jonathanbrickman0000 · Posted: May 02, 2006 10:57 Post subject:

So should it be something like:

Build rtlib, copy to ~FB/lib
Build rtlibx, copy to ~FB/lib
Build compiler, copy to ~FB/lib

Or should it be...

Build rtlib
Build rtlibx
Build compiler
Copy all three to ~FB/lib

Or some other permutation?

Sisophon2001 · Master

Always follow the first option, but be careful to have backups of the libraries. The old fbc may be incompatible with the new runtime library or it can fail to compile the new fbc, but this will not happen often.

If you follow the second option, the new compiler gets linked to the old library and you have a hybrid version that may be buggy.

The correct answer may depend on the modifications made since the last compiler update.

Several times I needed to modify the source code downloaded from SF so that I could build an intermediate version that I in then used to compile CVS version.

This game of following the latest build is not always a straight forward one, and it is often not worth the effort, unless you are interested in learning.

For general advice, it is sometimes recommended to build a self compiling compiler three times before use. This process should work out any obvious cyclic bugs, which appear in every second version of a compile.

Garvan

EDIT 2006-05-03:
Re-read my post, and decided it did not say exactly as I intended, so I updated it.

jonathanbrickman0000 · Posted: May 10, 2006 14:33 Post subject:

Thanks, Siso. I referenced your post immediately above in a note at the end of each doc. I'll do better as soon as I am given time.

ici · Posted: Oct 11, 2006 17:05 Post subject:

Hi all, and especially DrV :)

Please change in CVS Tree, src/rtlib/win32/fb_win32.h, line 80:

DrV · Site Admin

Thanks, updated in CVS.

1000101 · Hero

In the section titled "Updating the FreeBASIC software installed in MSYS" there is an error. The current line regarding the first of the copies of the newly compiled compiler reads as follows:

ici · Posted: Oct 26, 2006 15:29 Post subject:

Linux build, required one step more for me on Suse 10.1, after first cvs update
Make rtlib above make install

wolfman775 · Posted: May 17, 2009 9:24 Post subject:

I got to make rtlib and just copied and pasted the commands and when it got to autoreconf I got this error:

counting_pine · Site Admin

If you're trying the MinGW build, then maybe having cygwin tools in your path is causing problems.

Also: if your instructions mention CVS, they're very out of date. FB has been using SVN for a while. Try the wiki:
http://www.freebasic.net/wiki/wikka.php?wakka=SVNCompile