mirrors/fltk
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add "Known Problems" section for MinGW builds to README.MSWindows.txt (STR #2971).

Browse Source 
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@10322 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
This commit is contained in:
Albrecht Schlosser 2014-09-19 12:19:50 +00:00
parent 527190420c
commit d98853628b
1 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.MSWindows.txt
View File

@ -240,6 +240,22 @@ linking:
./configure <config flags> LDFLAGS=-Wl,--enable-auto-import
:END_ADVANCED
Known Problems:
There is a known incompatibility with some Windows subversion tools that
may not set the correct line endings for autoconf. If you get strange
error messages when running ./configure or make, you may need to convert
configh.in to "Unix line endings" (LF-only). These error messages are
unspecific, e.g. compilation errors like:
error: 'U32' does not name a type
error: 'bmibuffer' was not declared in this scope
You can fix the line endings with the MinGW/msys tool 'unix2dos' (u2d)
or with your favorite editor, if it allows to change the line endings,
then run autoconf and ./configure again.
For further information see this bug report:
http://www.fltk.org/newsgroups.php?gfltk.bugs+v:10197
Building FLTK
---------------
@ -537,7 +553,7 @@ is changed, the corresponding .cxx file will be recompiled.
Windows has a flag that determines whether an application
runs in the foreground with a console or in the background
without a console.
without a console.
If you're using gcc (i.e. MinGW or Cygwin), then use the
linker option "-mwindows" to make your application run in