| [proaudio] Freqtweak needs to be changed to use sigc++-2.0 |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: [proaudio] Freqtweak needs to be changed to use sigc++-2.0
- From: Reuben Martin <reuben.m@xxxxxxxxx>
- Date: Sat, 8 Oct 2011 20:47:11 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=MQ/Eg7ATL4W8mMvB4RQIP2uYSqxecwcD/KhFNickOFk=; b=hE6iBNHLYMtELseMIGEpVgXwESaf7EOd/5rWBh/FLwvx4s5l0/wzJI+Ja3uX1dBGE6 1UK7QR6KEdK22fKVnt3o+9CDs9MV4VRO6pU7KSw7Qmpa6DAYJWK8o5lRfRGkKu96exLV 7wqgM0MTORAm/qDCu93qZah/IBQO0nWymVz6w=
For some reason Freqtweak no longer will build again sigc++-1.2. I'm
not really sure why, all the includes are set correctly. For some
reason though the namespace used when compiling has switched back to
the depreciated "SigC" type. (Examin the output generated by the
compiler with the -E option set) Me thinks this may have something to
do with supporting old cruft in portage propper that require mucking
around with the namespace used.
I haven't taken the time to see if that's what's going on because it
really doesn't matter. Freqtweak will build with sigc++-2.0 anyway if
you go in and manually change all the includes and linking to use the
2.0 version. Just built it now and it seems to be working just fine.
I'm sure there is probably a quick and dirty way to swap out the
sigc++ versions being set by autotools.
-Reuben