Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
yangql
googletest
Commits
44a8cf19
Commit
44a8cf19
authored
Dec 22, 2008
by
shiqian
Browse files
Fixes Windows build instructions in README.
parent
9dd55ad3
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
19 additions
and
14 deletions
+19
-14
README
README
+19
-14
No files found.
README
View file @
44a8cf19
...
@@ -228,27 +228,32 @@ against Google Test as well. There is no need to configure Google Test
...
@@ -228,27 +228,32 @@ against Google Test as well. There is no need to configure Google Test
separately
.
separately
.
###
Windows
###
###
Windows
###
The
msvc
/
directory
contains
VC
++
2005
projects
for
building
Google
Mock
and
The
msvc
/
directory
contains
VC
++
2005
projects
for
building
Google
selected
tests
.
In
order
to
build
Google
Mock
you
must
have
an
implementation
Mock
and
selected
tests
.
In
order
to
build
Google
Mock
you
must
have
of
TR1
tuple
.
One
library
that
provides
such
implementation
is
Boost
.
If
you
an
implementation
of
TR1
tuple
.
One
library
that
provides
such
choose
to
use
Boost
,
download
it
from
www
.
boost
.
org
and
install
it
on
your
implementation
is
Boost
.
If
you
choose
to
use
Boost
,
download
it
from
system
.
After
that
you
have
two
options
:
either
configure
Boost
as
a
system
www
.
boost
.
org
and
install
it
on
your
system
.
Note
that
Boost
TR1
tuple
library
or
modify
the
Google
Mock
project
to
point
to
your
copy
of
Boost
.
The
is
a
header
-
only
library
,
so
the
installation
only
involves
unpacking
former
solution
will
let
all
your
tests
use
the
same
copy
of
Boost
while
the
it
to
a
suitable
location
-
you
don
't need to compile it or download a
latter
one
will
let
each
of
your
projects
use
its
own
copy
of
Boost
.
You
can
pre-compiled Boost binary.
also
use
a
hybrid
solution
:
your
project
settings
will
override
the
system
-
wide
one
.
After that you have two options: either set up Boost globally or
modify the Google Mock project to point to your copy of Boost. The
former will let all your tests use the same Boost library while the
latter will allow each of your projects use its own copy. You can also
use a hybrid solution: your project settings will override the
system-wide one.
For example, if you unpacked boost v1.36.0 into C:\boost:
For example, if you unpacked boost v1.36.0 into C:\boost:
To
configure
Boost
as
a
system
library
.
To
set up Boost such that all projects can use it:
* Assuming you are using the Visual Studio 2005 IDE, select Tools |
* Assuming you are using the Visual Studio 2005 IDE, select Tools |
Options | Projects And Solutions | VC++ Directories.
Options | Projects And Solutions | VC++ Directories.
* In the "Show directories for" drop-down select Include Files. Add
* In the "Show directories for" drop-down select Include Files. Add
C
:\
boost
\
v
_1_36_0
\
boost
\
tr1
\
tr1
and
C
:\
boost
\
v
_1_36_0
to
the
list
of
C:\boost\
boost
_1_36_0\boost\tr1\tr1 and C:\boost\
boost
_1_36_0 to the
directories
.
list of
directories.
To configure your project to point to that version of Boost, replace
To configure your project to point to that version of Boost, replace
the
value
of
the
BoostDir
user
macro
with
C
:\
boost
\
v
_1_36_0
in
the
the value of the BoostDir user macro with C:\boost\
boost
_1_36_0 in the
msvc/gmock_config.vsprops file. You can use any text editor to edit
msvc/gmock_config.vsprops file. You can use any text editor to edit
that file.
that file.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment