firebreath-1.4a1-0-g1af4e14 FBTestPlugin compile errors in VS 2010

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Compile firebreath-1.4a1-0-g1af4e14 FBTestPlugin in VS 2010
2.
3.

What is the expected output? What do you see instead?
Expect Successful build, instead there are compile errors and 2 failed builds.

What version of FireBreath are you using? On what operating system and
browsers?
firebreath-1.4a1-0-g1af4e14
Windows 7
Chrome

Please provide any additional information below.
firebreath-firebreath-1af4e14\src\pluginauto\win\pluginwindowwin.h(73): error 
C2146: syntax error : missing ';' before identifier 'HandleEvent'

firebreath-firebreath-1af4e14\src\pluginauto\win\pluginwindowwin.h(73): error 
C4430: missing type specifier - int assumed. Note: C++ does not support 
default-int

etc...

Original issue reported on code.google.com by rjani...@gmail.com on 31 Dec 2010 at 5:08

[GoogleCodeExporter]

LOL.  you gotta be kidding me... trying it.  Note that there are a couple of 
breaking changes (really minor ones) that I should have mentioned, but it 
doesn't sound like you're hitting those. 

Original comment by richarda...@gmail.com on 31 Dec 2010 at 5:44

[GoogleCodeExporter]

I can't reproduce this, but looking at where the file is it looks like it could 
be a weird issue that I've seen in other files with using types like int16_t; 
I've changed it the same way I did last time I saw a similar issue.  Could you 
try it and let me know if that fixes your issue?

It's just the latest in the master branch or the firebreath-1.4 branch.

Original comment by richarda...@gmail.com on 31 Dec 2010 at 6:06

• Changed state: Accepted

[GoogleCodeExporter]

Thank you. That fixed the compile errors.
I found the cause of the problem. It is because I am using boost 1.43. I went 
back and tested the original 1.4a1-0-g1af4e14 version and it compiled without 
errors using the built in boost.

Original comment by rjani...@gmail.com on 31 Dec 2010 at 7:34

[GoogleCodeExporter]

huh.  That's weird; I would not have expected that the built-in boost was what 
provided the int16_t type.  I will try to just use the explicit boost::int16_t, 
etc types in the future.

Thank you for clearing that up for me; as I said, we've had this issue before 
and it baffled me =]

Original comment by richarda...@gmail.com on 31 Dec 2010 at 2:55

[GoogleCodeExporter]

Original comment by rich...@firebreath.org on 31 Dec 2010 at 8:21

• Changed state: Fixed