And what's wrong with just adding it to our headers?
On 2016-10-30 15:14, hbelusca(a)svn.reactos.org wrote:
Author: hbelusca
Date: Sun Oct 30 14:14:27 2016
New Revision: 73078
URL:
http://svn.reactos.org/svn/reactos?rev=73078&view=rev
Log:
[BTRFS]: Fix compilation with MSVC too, as we don't have the
'FileFsSectorSizeInformation' FS information class in our headers (this is some
Win8+ stuff).
CORE-12223 #comment MSVC compilation fixed in r73078
('FileFsSectorSizeInformation' absent in our headers).
Modified:
trunk/reactos/drivers/filesystems/btrfs/btrfs.c
Modified: trunk/reactos/drivers/filesystems/btrfs/btrfs.c
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/filesystems/btrfs/…
==============================================================================
--- trunk/reactos/drivers/filesystems/btrfs/btrfs.c [iso-8859-1] (original)
+++ trunk/reactos/drivers/filesystems/btrfs/btrfs.c [iso-8859-1] Sun Oct 30 14:14:27
2016
@@ -716,7 +716,8 @@
Status = overflow ? STATUS_BUFFER_OVERFLOW : STATUS_SUCCESS;
break;
}
-
+
+#ifndef __REACTOS__
#ifdef _MSC_VER // not in mingw yet
case FileFsSectorSizeInformation:
{
@@ -739,6 +740,7 @@
break;
}
#endif
+#endif /* __REACTOS__ */
default:
Status = STATUS_INVALID_PARAMETER;