Crypto++ not compiling with VS 2009 Professional

[kt-8]

Downloaded the most recent version, neither the .sln nor the .proj
files will compile - complaining about undefined BOOL - seems to be
missing some windows headers or libraries.  Using VS 2009 Prof.

thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe@....
More information about Crypto++ and this group is available at http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---

[Dillon Beresford]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

kt wrote:
> Downloaded the most recent version, neither the .sln nor the .proj
> files will compile - complaining about undefined BOOL - seems to be
> missing some windows headers or libraries.  Using VS 2009 Prof.
>
> thanks.
> >
>
Hi kt,

Welcome to the group. Try changing BOOL to bool for giggles and see
what happens. In addition, the .sln should migrate right over without
issues. The headers and library needs to be linked accordingly.

If you need further help please respond and include debug output. Jeff
Walton can probably explain this better than me.

- ---- snip

Example: MSDN
[SerializableAttribute]
[ComVisibleAttribute(true)]
public value class Boolean : IComparable,
    IConvertible, IComparable<bool>, IEquatable<bool>

- ---- snip

The only possible values for a 'bool' are 'true' and 'false', whereas
for 'BOOL' you can use any 'int' value, though 'TRUE' and 'FALSE'
macros are defined in 'windef.h' header.

typedef int                 BOOL;

#ifndef FALSE
#define FALSE               0
#endif

#ifndef TRUE
#define TRUE                1
#endif

Best,

Dillon


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEUEARECAAYFAkqUOfIACgkQRnxC5lZRuuHIfwCgiDo6eO+5PY6NGSIg3dTfn2to
EVUAmNIUf921eCLbMkmJp57wqbcPn/s=
=aOq5
-----END PGP SIGNATURE-----


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe@....
More information about Crypto++ and this group is available at http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---

[Robert Roessler]

kt wrote:
> Downloaded the most recent version, neither the .sln nor the .proj
> files will compile - complaining about undefined BOOL - seems to be
> missing some windows headers or libraries.  Using VS 2009 Prof.

You must have a special version of VS - most of us have to make do with
2008 or possibly 2010 beta releases. ;)

On my VS 2008 SP1, all of the projects EXCEPT "dlltest" build without
error - once I have allowed VS to do its automatic upgrade from the VS
2005 project files.

For the "dlltest" project, there is a fairly well-known build issue that
can be easily fixed by adding in the lines

--------
#define _DO_NOT_DECLARE_INTERLOCKED_INTRINSICS_IN_MEMORY

#include <intrin.h>
--------

in dlltest.cpp, just before the first #include.  You might want to do a
Web search on _DO_NOT_DECLARE_INTERLOCKED_INTRINSICS_IN_MEMORY.

BTW, I don't guarantee the above fix... it definitely allows me to
complete building the solution, and I *think* the proper semantics are
preserved. ;)

Robert Roessler

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe@....
More information about Crypto++ and this group is available at http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---

[kt-8]

thanks for your ideas.  I think there is a windows preprocessor flag
missing, I tried adding _WIN32 and _WINDOWS to all the projects, I
also tried putting in #include <windows.h> in the crypto++ source
files that were causing the errors, neither seemed to help.

The errors I am getting are:

1>Compiling...
1>iterhash.cpp
1>dll.cpp
1>C:\Program Files\Microsoft Visual Studio 9.0\VC\include\list(143) :
error C2061: syntax error : identifier 'BOOL'
1>        C:\Program Files\Microsoft Visual Studio 9.0\VC\include\list
(1274) : see reference to class template instantiation
'std::list<_Ty,_Ax>' being compiled
1>C:\Program Files\Microsoft Visual Studio 9.0\VC\include\list(143) :
error C2992: 'std::list<_Ty,_Ax>::_Const_iterator' : invalid or
missing template parameter list


What I'm really after is a 32-bit sse implementation of aes-gcm.  I
don't really need these projects to build, but felt more comfortamble
pulling in the aes and gcm source in crytpo++ if I could get a running
example.

thanks



On Aug 25, 12:38 pm, Robert Roessler <roess...@...> wrote:

> kt wrote:
> > Downloaded the most recent version, neither the .sln nor the .proj
> > files will compile - complaining about undefined BOOL - seems to be
> > missing some windows headers or libraries.  Using VS 2009 Prof.
>
> You must have a special version of VS - most of us have to make do with
> 2008 or possibly 2010 beta releases. ;)
>
> On my VS 2008 SP1, all of the projects EXCEPT "dlltest" build without
> error - once I have allowed VS to do its automatic upgrade from the VS
> 2005 project files.
>
> For the "dlltest" project, there is a fairly well-known build issue that
> can be easily fixed by adding in the lines
>
> --------
> #define _DO_NOT_DECLARE_INTERLOCKED_INTRINSICS_IN_MEMORY
>
> #include <intrin.h>
> --------
>
> in dlltest.cpp, just before the first #include.  You might want to do a
> Web search on _DO_NOT_DECLARE_INTERLOCKED_INTRINSICS_IN_MEMORY.
>
> BTW, I don't guarantee the above fix... it definitely allows me to
> complete building the solution, and I *think* the proper semantics are
> preserved. ;)
>
> Robert Roessler

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe@....
More information about Crypto++ and this group is available at http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---

[Dillon Beresford]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

kt wrote:

> thanks for your ideas.  I think there is a windows preprocessor flag
> missing, I tried adding _WIN32 and _WINDOWS to all the projects, I
> also tried putting in #include <windows.h> in the crypto++ source
> files that were causing the errors, neither seemed to help.
>
> The errors I am getting are:
>
> 1>Compiling...
> 1>iterhash.cpp
> 1>dll.cpp
> 1>C:\Program Files\Microsoft Visual Studio 9.0\VC\include\list(143) :
> error C2061: syntax error : identifier 'BOOL'
> 1>        C:\Program Files\Microsoft Visual Studio 9.0\VC\include\list
> (1274) : see reference to class template instantiation
> 'std::list<_Ty,_Ax>' being compiled
> 1>C:\Program Files\Microsoft Visual Studio 9.0\VC\include\list(143) :
> error C2992: 'std::list<_Ty,_Ax>::_Const_iterator' : invalid or
> missing template parameter list
>
>
> What I'm really after is a 32-bit sse implementation of aes-gcm.  I
> don't really need these projects to build, but felt more comfortamble
> pulling in the aes and gcm source in crytpo++ if I could get a running
> example.
>
> thanks
>
>
>
> On Aug 25, 12:38 pm, Robert Roessler <roess...@...> wrote:
>> kt wrote:
>>> Downloaded the most recent version, neither the .sln nor the .proj
>>> files will compile - complaining about undefined BOOL - seems to be
>>> missing some windows headers or libraries.  Using VS 2009 Prof.
>> You must have a special version of VS - most of us have to make do with
>> 2008 or possibly 2010 beta releases. ;)
>>
>> On my VS 2008 SP1, all of the projects EXCEPT "dlltest" build without
>> error - once I have allowed VS to do its automatic upgrade from the VS
>> 2005 project files.
>>
>> For the "dlltest" project, there is a fairly well-known build issue that
>> can be easily fixed by adding in the lines
>>
>> --------
>> #define _DO_NOT_DECLARE_INTERLOCKED_INTRINSICS_IN_MEMORY
>>
>> #include <intrin.h>
>> --------
>>
>> in dlltest.cpp, just before the first #include.  You might want to do a
>> Web search on _DO_NOT_DECLARE_INTERLOCKED_INTRINSICS_IN_MEMORY.
>>
>> BTW, I don't guarantee the above fix... it definitely allows me to
>> complete building the solution, and I *think* the proper semantics are
>> preserved. ;)
>>
>> Robert Roessler
> >
>

kt,

I'm a little perplexed as to why you would include the <windows.h>
header file inside the Crypto++ source files?  You don't need to do
this . Have you upgraded the SP1 for Visual Studio 2008? Or is this a
fresh install of VS 2008 sp0? The error that Robert Roessler mentioned
is very common and I think we have all had to deal with that issue at
one time or another. Is this the latest version of Crypto++ 5.6? Can
you verify the version I can assure you I have never had a proble with
any windows preprocessor flags when compiling Crypto++ from source on
Windows.

Before you worry about compiling the aes-gcm you need to make sure you
can compile the test and the working debug and release libraries if
you plan on developing anything...

1. Update Visual Studio to SP1 if you haven't already, install reboot.
2. Download the latest build of crypto++ unzip and upgrade the solution.
3. Compile the libs and test.
4. Run the benchmark.

- ---- snip

I've stripped down my version of crypto++ but that's just due to my
own needs for my project. However, from what you're saying here you
shouldn't need to edit anything in the source. Just compile and viola!
I've used the library on Windows and Linux inside various compilers
g++, NetBeans, Qt Creator, Visual Studio and I've never had to once
edit any of Wei's source files other than the #define statement Robert
mentioned... I think your source is a little screwed up. :)

Best,

Dillon



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqURFEACgkQRnxC5lZRuuEguACgktFMtAL9UvfY92Cp1rmc1pBM
e80AoOAJOylKc77ZnymHJ/lcK2m1eYfR
=6Iyw
-----END PGP SIGNATURE-----


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe@....
More information about Crypto++ and this group is available at http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---

[kt-8]

Indeed, I do have SP1.  And indeed the title of this post was
inaccurate, I am using VS 9.0 (which is 2008 not 2009).  That's great
to know you haven't had problems, there must be something special
about my install or environment.


On Aug 25, 1:06 pm, Dillon Beresford <dillon.beresf...@...>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
>
>
> kt wrote:
> > thanks for your ideas.  I think there is a windows preprocessor flag
> > missing, I tried adding _WIN32 and _WINDOWS to all the projects, I
> > also tried putting in #include <windows.h> in the crypto++ source
> > files that were causing the errors, neither seemed to help.
>
> > The errors I am getting are:
>
> > 1>Compiling...
> > 1>iterhash.cpp
> > 1>dll.cpp
> > 1>C:\Program Files\Microsoft Visual Studio 9.0\VC\include\list(143) :
> > error C2061: syntax error : identifier 'BOOL'
> > 1>        C:\Program Files\Microsoft Visual Studio 9.0\VC\include\list
> > (1274) : see reference to class template instantiation
> > 'std::list<_Ty,_Ax>' being compiled
> > 1>C:\Program Files\Microsoft Visual Studio 9.0\VC\include\list(143) :
> > error C2992: 'std::list<_Ty,_Ax>::_Const_iterator' : invalid or
> > missing template parameter list
>
> > What I'm really after is a 32-bit sse implementation of aes-gcm.  I
> > don't really need these projects to build, but felt more comfortamble
> > pulling in the aes and gcm source in crytpo++ if I could get a running
> > example.
>
> > thanks
>
> > On Aug 25, 12:38 pm, Robert Roessler <roess...@...> wrote:
> >> kt wrote:
> >>> Downloaded the most recent version, neither the .sln nor the .proj
> >>> files will compile - complaining about undefined BOOL - seems to be
> >>> missing some windows headers or libraries.  Using VS 2009 Prof.
> >> You must have a special version of VS - most of us have to make do with
> >> 2008 or possibly 2010 beta releases. ;)
>
> >> On my VS 2008 SP1, all of the projects EXCEPT "dlltest" build without
> >> error - once I have allowed VS to do its automatic upgrade from the VS
> >> 2005 project files.
>
> >> For the "dlltest" project, there is a fairly well-known build issue that
> >> can be easily fixed by adding in the lines
>
> >> --------
> >> #define _DO_NOT_DECLARE_INTERLOCKED_INTRINSICS_IN_MEMORY
>
> >> #include <intrin.h>
> >> --------
>
> >> in dlltest.cpp, just before the first #include.  You might want to do a
> >> Web search on _DO_NOT_DECLARE_INTERLOCKED_INTRINSICS_IN_MEMORY.
>
> >> BTW, I don't guarantee the above fix... it definitely allows me to
> >> complete building the solution, and I *think* the proper semantics are
> >> preserved. ;)
>
> >> Robert Roessler
>
> kt,
>
> I'm a little perplexed as to why you would include the <windows.h>
> header file inside the Crypto++ source files?  You don't need to do
> this . Have you upgraded the SP1 for Visual Studio 2008? Or is this a
> fresh install of VS 2008 sp0? The error that Robert Roessler mentioned
> is very common and I think we have all had to deal with that issue at
> one time or another. Is this the latest version of Crypto++ 5.6? Can
> you verify the version I can assure you I have never had a proble with
> any windows preprocessor flags when compiling Crypto++ from source on
> Windows.
>
> Before you worry about compiling the aes-gcm you need to make sure you
> can compile the test and the working debug and release libraries if
> you plan on developing anything...
>
> 1. Update Visual Studio to SP1 if you haven't already, install reboot.
> 2. Download the latest build of crypto++ unzip and upgrade the solution.
> 3. Compile the libs and test.
> 4. Run the benchmark.
>
> - ---- snip
>
> I've stripped down my version of crypto++ but that's just due to my
> own needs for my project. However, from what you're saying here you
> shouldn't need to edit anything in the source. Just compile and viola!
> I've used the library on Windows and Linux inside various compilers
> g++, NetBeans, Qt Creator, Visual Studio and I've never had to once
> edit any of Wei's source files other than the #define statement Robert
> mentioned... I think your source is a little screwed up. :)
>
> Best,
>
> Dillon
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkqURFEACgkQRnxC5lZRuuEguACgktFMtAL9UvfY92Cp1rmc1pBM
> e80AoOAJOylKc77ZnymHJ/lcK2m1eYfR
> =6Iyw
> -----END PGP SIGNATURE------ Hide quoted text -
>
> - Show quoted text -

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe@....
More information about Crypto++ and this group is available at http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---

[Dillon Beresford]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

kt wrote:

> Indeed, I do have SP1.  And indeed the title of this post was
> inaccurate, I am using VS 9.0 (which is 2008 not 2009).  That's
> great to know you haven't had problems, there must be something
> special about my install or environment.
>
>
> On Aug 25, 1:06 pm, Dillon Beresford <dillon.beresf...@...>
> wrote:
>
>
>
>
> kt wrote:
>>>> thanks for your ideas.  I think there is a windows
>>>> preprocessor flag missing, I tried adding _WIN32 and _WINDOWS
>>>> to all the projects, I also tried putting in #include
>>>> <windows.h> in the crypto++ source files that were causing
>>>> the errors, neither seemed to help. The errors I am getting
>>>> are: 1>Compiling... 1>iterhash.cpp 1>dll.cpp 1>C:\Program
>>>> Files\Microsoft Visual Studio
> 9.0\VC\include\list(143) :
>>>> error C2061: syntax error : identifier 'BOOL' 1>
>>>> C:\Program Files\Microsoft Visual Studio
> 9.0\VC\include\list
>>>> (1274) : see reference to class template instantiation
>>>> 'std::list<_Ty,_Ax>' being compiled 1>C:\Program
>>>> Files\Microsoft Visual Studio
> 9.0\VC\include\list(143) :
>>>> error C2992: 'std::list<_Ty,_Ax>::_Const_iterator' : invalid
>>>> or missing template parameter list What I'm really after is a
>>>> 32-bit sse implementation of aes-gcm.  I don't really need
>>>> these projects to build, but felt more
> comfortamble
>>>> pulling in the aes and gcm source in crytpo++ if I could get
>>>> a
> running
>>>> example. thanks On Aug 25, 12:38 pm, Robert Roessler
>>>> <roess...@...> wrote:
>>>>> kt wrote:
>>>>>> Downloaded the most recent version, neither the .sln nor
>>>>>> the .proj files will compile - complaining about
>>>>>> undefined BOOL - seems
> to be
>>>>>> missing some windows headers or libraries.  Using VS 2009
>>>>>> Prof.
>>>>> You must have a special version of VS - most of us have to
>>>>> make
> do with
>>>>> 2008 or possibly 2010 beta releases. ;) On my VS 2008 SP1,
>>>>> all of the projects EXCEPT "dlltest" build
> without
>>>>> error - once I have allowed VS to do its automatic upgrade
>>>>> from
> the VS
>>>>> 2005 project files. For the "dlltest" project, there is a
>>>>> fairly well-known build
> issue that
>>>>> can be easily fixed by adding in the lines -------- #define
>>>>> _DO_NOT_DECLARE_INTERLOCKED_INTRINSICS_IN_MEMORY #include
>>>>> <intrin.h> -------- in dlltest.cpp, just before the first
>>>>> #include.  You might want
> to do a
>>>>> Web search on
>>>>> _DO_NOT_DECLARE_INTERLOCKED_INTRINSICS_IN_MEMORY. BTW, I
>>>>> don't guarantee the above fix... it definitely allows me to
>>>>>  complete building the solution, and I *think* the proper
> semantics are
>>>>> preserved. ;) Robert Roessler
> kt,
>
> I'm a little perplexed as to why you would include the <windows.h>
> header file inside the Crypto++ source files?  You don't need to do
>  this . Have you upgraded the SP1 for Visual Studio 2008? Or is
> this a fresh install of VS 2008 sp0? The error that Robert Roessler
> mentioned is very common and I think we have all had to deal with
> that issue at one time or another. Is this the latest version of
> Crypto++ 5.6? Can you verify the version I can assure you I have
> never had a proble with any windows preprocessor flags when
> compiling Crypto++ from source on Windows.
>
> Before you worry about compiling the aes-gcm you need to make sure
> you can compile the test and the working debug and release
> libraries if you plan on developing anything...
>
> 1. Update Visual Studio to SP1 if you haven't already, install
> reboot. 2. Download the latest build of crypto++ unzip and upgrade
> the solution. 3. Compile the libs and test. 4. Run the benchmark.
>
> ---- snip
>
> I've stripped down my version of crypto++ but that's just due to my
>  own needs for my project. However, from what you're saying here
> you shouldn't need to edit anything in the source. Just compile and
> viola! I've used the library on Windows and Linux inside various
> compilers g++, NetBeans, Qt Creator, Visual Studio and I've never
> had to once edit any of Wei's source files other than the #define
> statement Robert mentioned... I think your source is a little
> screwed up. :)
>
> Best,
>
> Dillon
>
>>

- - Show quoted text -
>
kt,

Might be the includes path, I would just start from scratch and double
check your environment. It really sounds like the path variable is not
configured properly maybe this happen after you upgraded your
solution. I can tell you it's going to be well worth the time you
invest getting the libraries compiled. For over a year now I have had
so much fun with this library. It's truly awesome. Just hang in there
and give it another shot. Try building from scratch again and let us
know how it works out. We are here to help you.

Best,

Dillon

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqUSTYACgkQRnxC5lZRuuEujQCgqMRk1wadEUcrChUPLlnDnGLt
UeAAoIotePzfosC4d+zouuVPFJSMNKH4
=tNbT
-----END PGP SIGNATURE-----


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe@....
More information about Crypto++ and this group is available at http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---

[kt-8]

I tried to compile the library in a different environment and it
worked.  Looking at the difference between the two environments,
either the 2005 redistributables or the 2008 SDK (1.1)
are the culprit.

kt

On Aug 25, 1:27 pm, Dillon Beresford <dillon.beresf...@...>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
>
>
> kt wrote:
> > Indeed, I do have SP1.  And indeed the title of this post was
> > inaccurate, I am using VS 9.0 (which is 2008 not 2009).  That's
> > great to know you haven't had problems, there must be something
> > special about my install or environment.
>
> > On Aug 25, 1:06 pm, Dillon Beresford <dillon.beresf...@...>
> > wrote:
>
> > kt wrote:
> >>>> thanks for your ideas.  I think there is a windows
> >>>> preprocessor flag missing, I tried adding _WIN32 and _WINDOWS
> >>>> to all the projects, I also tried putting in #include
> >>>> <windows.h> in the crypto++ source files that were causing
> >>>> the errors, neither seemed to help. The errors I am getting
> >>>> are: 1>Compiling... 1>iterhash.cpp 1>dll.cpp 1>C:\Program
> >>>> Files\Microsoft Visual Studio
> > 9.0\VC\include\list(143) :
> >>>> error C2061: syntax error : identifier 'BOOL' 1>
> >>>> C:\Program Files\Microsoft Visual Studio
> > 9.0\VC\include\list
> >>>> (1274) : see reference to class template instantiation
> >>>> 'std::list<_Ty,_Ax>' being compiled 1>C:\Program
> >>>> Files\Microsoft Visual Studio
> > 9.0\VC\include\list(143) :
> >>>> error C2992: 'std::list<_Ty,_Ax>::_Const_iterator' : invalid
> >>>> or missing template parameter list What I'm really after is a
> >>>> 32-bit sse implementation of aes-gcm.  I don't really need
> >>>> these projects to build, but felt more
> > comfortamble
> >>>> pulling in the aes and gcm source in crytpo++ if I could get
> >>>> a
> > running
> >>>> example. thanks On Aug 25, 12:38 pm, Robert Roessler
> >>>> <roess...@...> wrote:
> >>>>> kt wrote:
> >>>>>> Downloaded the most recent version, neither the .sln nor
> >>>>>> the .proj files will compile - complaining about
> >>>>>> undefined BOOL - seems
> > to be
> >>>>>> missing some windows headers or libraries.  Using VS 2009
> >>>>>> Prof.
> >>>>> You must have a special version of VS - most of us have to
> >>>>> make
> > do with
> >>>>> 2008 or possibly 2010 beta releases. ;) On my VS 2008 SP1,
> >>>>> all of the projects EXCEPT "dlltest" build
> > without
> >>>>> error - once I have allowed VS to do its automatic upgrade
> >>>>> from
> > the VS
> >>>>> 2005 project files. For the "dlltest" project, there is a
> >>>>> fairly well-known build
> > issue that
> >>>>> can be easily fixed by adding in the lines -------- #define
> >>>>> _DO_NOT_DECLARE_INTERLOCKED_INTRINSICS_IN_MEMORY #include
> >>>>> <intrin.h> -------- in dlltest.cpp, just before the first
> >>>>> #include.  You might want
> > to do a
> >>>>> Web search on
> >>>>> _DO_NOT_DECLARE_INTERLOCKED_INTRINSICS_IN_MEMORY. BTW, I
> >>>>> don't guarantee the above fix... it definitely allows me to
> >>>>>  complete building the solution, and I *think* the proper
> > semantics are
> >>>>> preserved. ;) Robert Roessler
> > kt,
>
> > I'm a little perplexed as to why you would include the <windows.h>
> > header file inside the Crypto++ source files?  You don't need to do
> >  this . Have you upgraded the SP1 for Visual Studio 2008? Or is
> > this a fresh install of VS 2008 sp0? The error that Robert Roessler
> > mentioned is very common and I think we have all had to deal with
> > that issue at one time or another. Is this the latest version of
> > Crypto++ 5.6? Can you verify the version I can assure you I have
> > never had a proble with any windows preprocessor flags when
> > compiling Crypto++ from source on Windows.
>
> > Before you worry about compiling the aes-gcm you need to make sure
> > you can compile the test and the working debug and release
> > libraries if you plan on developing anything...
>
> > 1. Update Visual Studio to SP1 if you haven't already, install
> > reboot. 2. Download the latest build of crypto++ unzip and upgrade
> > the solution. 3. Compile the libs and test. 4. Run the benchmark.
>
> > ---- snip
>
> > I've stripped down my version of crypto++ but that's just due to my
> >  own needs for my project. However, from what you're saying here
> > you shouldn't need to edit anything in the source. Just compile and
> > viola! I've used the library on Windows and Linux inside various
> > compilers g++, NetBeans, Qt Creator, Visual Studio and I've never
> > had to once edit any of Wei's source files other than the #define
> > statement Robert mentioned... I think your source is a little
> > screwed up. :)
>
> > Best,
>
> > Dillon
>
> - - Show quoted text -
>
> kt,
>
> Might be the includes path, I would just start from scratch and double
> check your environment. It really sounds like the path variable is not
> configured properly maybe this happen after you upgraded your
> solution. I can tell you it's going to be well worth the time you
> invest getting the libraries compiled. For over a year now I have had
> so much fun with this library. It's truly awesome. Just hang in there
> and give it another shot. Try building from scratch again and let us
> know how it works out. We are here to help you.
>
> Best,
>
> Dillon
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkqUSTYACgkQRnxC5lZRuuEujQCgqMRk1wadEUcrChUPLlnDnGLt
> UeAAoIotePzfosC4d+zouuVPFJSMNKH4
> =tNbT
> -----END PGP SIGNATURE------ Hide quoted text -
>
> - Show quoted text -

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe@....
More information about Crypto++ and this group is available at http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---