Greg Ercolano wrote:
> Dmitry wrote:
>>> Why? This is not a fltk problem, it's a problem with the MS tools.=20
>>>
>> I'm use wxWidgets + MSVC 2008 Express Edition and not have problem )))
>
> I don't know why it should be different, unless they've got
> some kind of packaging manager to handle the SxS stuff.
Apparently wxwidgets includes .rc (resource) files which handle
various theming of the interface, and certain settings in these
rc files can control the manifest stuff, eg:
http://www.wxwidgets.org/docs/faqmsw.htm#winxp
http://codeandcoffee.de/index.php?/archives/1-wxWidgets-Visual-Studio-.net-2003-porting-to-VS-2005.html
.rc files get attached to your executable during linking,
basically the same technique we use to assign icons to .exe's.
But everyone runs into this stuff eventually, even folks running
wxWidgets. Note these guys referring to this manifest/sxs stuff
as "madness" as well, as do us all:
http://www.nabble.com/Manifest-problems-td6153933.html
http://n2.nabble.com/Tutorial-How-to-install-files-into-WinSxS-td841475.html
I think the problem here is no one has taken the time to make
a FLTK tutorial for how to solve it in language that's easier
than Microsoft's voluminous "spanning tree" docs.
I've had enough of Microsoft for the day, now. ;)
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
