Dan Kegel [EMAIL PROTECTED] writes:
You could provide a dummy implementation of __bb_init_func
in the preloader, but that's uglier IMHO than just not
passing those options when compiling the preloader.
Sure, but you have to do that in a way that doesn't depend on
configure, and doesn't
By the way, I talked to Alexandre about the GCOV stuff, basically he wants
us to find out why arc profiling borks the preloader. Then the idea is it
can be enabled just using CFLAGS.
Until that happens though are you generating lcov output anywhere?
Mike Hearn wrote:
By the way, I talked to Alexandre about the GCOV stuff, basically he wants
us to find out why arc profiling borks the preloader. Then the idea is it
can be enabled just using CFLAGS.
(You're confusing the UCLA guys with the Harvey Mudd guys, Mike!)
Here's what [EMAIL PROTECTED]
Hi,
On Sun, Feb 27, 2005 at 10:21:15PM -0800, Rizwan Kassim wrote:
Folks,
Aleksandr Liber and I have put together a set of tests for
cabinet.dll. Before we submit them to wine-patches, can anyone offer
any critiques/input? We plan to submit in a day or two.
Cool stuff!
It's wonderful
Andreas wrote:
It's an unspoken rule that preprocessor directives (#ifdef, ...)
always start at the very beginning of a line to make sure one recognizes
immediately which parts of the code are being processed and which ones aren't.
Good point. I should have caught that style violation
when I
