Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hello Jerzy, Tuesday, June 15, 2004, 10:27:24 PM, you wrote: JK> Tony, >> You end up with a huge executable file, so it doesn't help - the more >> files that use MFC the more the overhead gets.. it doesn't take many >> before it's not worth it. JK> Since CVSNT is not MFC-intensive and it probably won't be the linker will JK> trim the size quite a lot. JK> There are two projects that use MFC. I made a quick check and the math is JK> currently as follows: JK> 1. cvsagent - 40960B - statically linked: 172032B. Difference: 131072B JK> 2. cvsntcpl - 61952B - statically linked: 222720B. Difference: 160768B JK> Two differences together: 291840B JK> Now, two MFC dlls: 1047552B + 1060864B = 2108416B JK> So, between dynamic and static linking we have 1816576B difference. JK> That is nearly 1.8MB more and it would make CVSNT installer half the JK> current size (and very suitable to include within WinCvs installer, JK> naturally ;) But cvsnt is using VS.NET i.e. MFC 7.1 and WinCvs is still MFC 6.0, isn't it? -- Best regards, Richard mailto:r.wirth at wirthware.de