Re: [PATCH 2/3] msvcp90/tests: Added allocator<char> tests
Piotr Caban <piotr(a)codeweavers.com> writes:
diff --git a/dlls/msvcp90/tests/Makefile.in b/dlls/msvcp90/tests/Makefile.in index b7fb8e5..9ac5ef5 100644 --- a/dlls/msvcp90/tests/Makefile.in +++ b/dlls/msvcp90/tests/Makefile.in @@ -5,7 +5,7 @@ VPATH = @srcdir@ TESTDLL = msvcp90.dll APPMODE = -mno-cygwin MODCFLAGS = @BUILTINFLAG@ -EXTRAINCL = -I$(TOPSRCDIR)/include/msvcrt +EXTRAINCL = -I$(TOPSRCDIR)/include/msvcrt -I$(SRCDIR)/..
Don't do that. Define the macros you need directly in the test file. -- Alexandre Julliard julliard(a)winehq.org
On 07/22/10 17:04, Alexandre Julliard wrote:
Piotr Caban<piotr(a)codeweavers.com> writes:
diff --git a/dlls/msvcp90/tests/Makefile.in b/dlls/msvcp90/tests/Makefile.in index b7fb8e5..9ac5ef5 100644 --- a/dlls/msvcp90/tests/Makefile.in +++ b/dlls/msvcp90/tests/Makefile.in @@ -5,7 +5,7 @@ VPATH = @srcdir@ TESTDLL = msvcp90.dll APPMODE = -mno-cygwin MODCFLAGS = @BUILTINFLAG@ -EXTRAINCL = -I$(TOPSRCDIR)/include/msvcrt +EXTRAINCL = -I$(TOPSRCDIR)/include/msvcrt -I$(SRCDIR)/..
Don't do that. Define the macros you need directly in the test file.
Almost all tests will need macros for calling functions. Should I define them in every test file?
Piotr Caban <piotr(a)codeweavers.com> writes:
Almost all tests will need macros for calling functions. Should I define them in every test file?
You can have a header in the tests if absolutely necessary. -- Alexandre Julliard julliard(a)winehq.org
participants (2)
-
Alexandre Julliard -
Piotr Caban