<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16464"><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
SPAN.EmailStyle17 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: personal-compose
}
SPAN.BalloonTextChar {
FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
.MsoChpDefault {
FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=206312514-11032013><FONT color=#0000ff
size=2 face=Arial>Hi Ross,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=206312514-11032013><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=206312514-11032013><FONT color=#0000ff
size=2 face=Arial>may be the easiest solution for such issue is to wrap all
Live555 functionality in a namespace? And place "using namespace Live555;"
somewhere in it's header. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=206312514-11032013><FONT color=#0000ff
size=2 face=Arial>Then people that uses boost (or any other library that
clashes with your lib by internal names/types) should not have a
problem...</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=206312514-11032013><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=206312514-11032013><FONT color=#0000ff
size=2 face=Arial>Nikolai</FONT></SPAN></DIV><BR>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> live-devel-bounces@ns.live555.com
[mailto:live-devel-bounces@ns.live555.com] <B>On Behalf Of </B>Jeff
Shanab<BR><B>Sent:</B> Monday, March 11, 2013 2:27 PM<BR><B>To:</B>
live-devel@lists.live555.com<BR><B>Subject:</B> [Live-devel] Breaking
change<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>I am updating live555 from 2012.2.29 to 2013.03.07 and found
a change in Boolean.hh that breaks my build. From reading the changelog, I think
this is recent.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>The line <o:p></o:p></P>
<P class=MsoNormal> “ #define Boolean bool
“<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Overwrites a class name in boost (move.cpp) where
there is a class with the name Boolean<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>In the past I have had this collide with libavcodec. So I end
up modifying this file every time I upgrade. <o:p></o:p></P>
<P class=MsoNormal>Is the problem a tough one to fix for live555?
too many years of too many people doing their own thing. (amazing for only
two states how many conflicting definitions there are)<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Is there a long term solution? Take it out of preprocessing
with a typedef? Or *<B>cough</B>* rework live555 to have it’s own bool type and
one header to map that to all the platforms?<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>I just remove the second part of the condition so it disables
the first case (lines 20-22), But I have not used Borland for
years.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt"> Jeff
Shanab, Manager-Software Engineering<o:p></o:p></SPAN></B></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt"> D
630.633.4515 | C 630.453.7764 | F 630.633.4815 | <A
href="mailto:jshanab@smartwire.com">jshanab@smartwire.com</A><o:p></o:p></SPAN></P>
<P class=MsoNormal><IMG id=Picture_x0020_1 border=0 alt=MVSSig
src="cid:206312514@11032013-00AD" width=626 height=90><o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<P>This message and any attachments contain confidential and proprietary
information, and may contain privileged information, belonging to one or more
affiliates of Windy City Wire Cable & Technology Products, LLC. No privilege
is waived by this transmission. Unauthorized use, copying or disclosure of such
information is prohibited and may be unlawful. If you receive this message in
error, please delete it from your system, destroy any printouts or copies of it,
and notify the sender immediately by e-mail or phone.</P><BR></BODY></HTML>