summaryrefslogtreecommitdiff
path: root/RepositoryFixes.mk
diff options
context:
space:
mode:
authorTor Lillqvist <tlillqvist@novell.com>2011-07-25 18:19:36 +0300
committerTor Lillqvist <tlillqvist@novell.com>2011-07-26 08:50:56 +0300
commit1a316d26d6f0d6049cc99ff6788478680bf31367 (patch)
tree5ca66f320a4143513918da15ecc17b981ddc70df /RepositoryFixes.mk
parent09fb06102812269cb911dc11c9d772331cf48a05 (diff)
Remove superfluous empty line
The comment for gb_Library_ILIBFILENAMES in the WNTGCC case doesn't make much sense for us, though, as I think we want to support WNTGCC only for cross-compilation, and thus we don't have access to the PSDK ("Platform" SDK, with which they mean the Windows SDK). I don't see any point in using MinGW natively on Windows to build LibreOffice. If you build locally, use MSVC.
Diffstat (limited to 'RepositoryFixes.mk')
-rw-r--r--RepositoryFixes.mk7
1 files changed, 3 insertions, 4 deletions
diff --git a/RepositoryFixes.mk b/RepositoryFixes.mk
index b6c710800f1c..d822ae6965b5 100644
--- a/RepositoryFixes.mk
+++ b/RepositoryFixes.mk
@@ -81,10 +81,9 @@ gb_Library_SDKLIBFILENAMES:=\
# some Windows platform libraries are missing in mingw library set
# we have to use them from the PSDK by linking against their ilibs
gb_Library_ILIBFILENAMES:=\
-
- unicows \
- uuid \
- winmm \
+ unicows \
+ uuid \
+ winmm \
gb_Library_DLLFILENAMES := $(filter-out $(foreach lib,$(gb_Library_SDKLIBFILENAMES),$(lib):%),$(gb_Library_DLLFILENAMES))
gb_Library_DLLFILENAMES += $(foreach lib,$(gb_Library_SDKLIBFILENAMES),$(lib):$(WINDOWS_SDK_HOME)/lib/$(lib).lib)