Dlls is very great!

dsantos-2 · ‎Feb 10, 2009

Hello!

I am compiling my Toolkit Wildfire 4.0project in Visual Studio 2005.

But the builded dlls is very great.It's haves 13.860 Kbytes.

Thanks, Diogo.

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

pwilliams-3 · ‎Feb 10, 2009

dsantos-2 · ‎Feb 10, 2009

Patrick!

I saw the examples of the Protoolkit (pt_examples.dll)and the dll is very great.

You could tell me which dlls in Visual Studio 2005 is required to distribute my application?

Thanks.

pwilliams-3 · ‎Feb 10, 2009

Just the dll that you compile should be distributed to your users.
Nothing else from Visual Studio is required.

Patrick Williams | Sr. Application Engineer | Engineering Systems |
Steelcase Inc. | 616.698.4078 | My Site
<">http://my.steelcase.com/Person.aspx?accountname=NA\PWILLIA3>

bbailey · ‎Feb 10, 2009

Hi Pat,

In case you've used any MFC stuff, you need to be sure that you've built
your DLL in Release mode. The app complains that it wants the debug DLLs.
Found that out the hard way!

Release mode also gives smaller compiled DLLs as well.

Ben

pwilliams-3 · ‎Feb 10, 2009

Ben,

You are correct but the difference in size between Release and Debug is
not due to the Pro/TOOLKIT libraries. PTC does not distribute a debug
version of their libraries. Therefore the difference in DLL size is due
to the Microsoft C/C++ runtime libraries. They do distribute debug and
release versions of their libraries. I always recommend distributing a
DLL compiled for the Release configuration.

Patrick Williams | Sr. Application Engineer | Engineering Systems |
Steelcase Inc. | 616.698.4078 | My Site
<">http://my.steelcase.com/Person.aspx?accountname=NA\PWILLIA3>

FV · ‎Feb 11, 2009

Hi all,

Interesting discussion.

Here is what I got from PTC support some time back:

=============================================================================

You opened 6829265 with PTC Technical Support on 12-Jan-2009, with the following description:

"Debug information is included in protk_dll.lib file. This cause VS2005 debugger to look for the original source files."

After further investigation, I found that SPR 1462374 was filed to reports the issue "While using ‘protk_dll.lib’ of Wildfire 4.0 release, the Size of TOOLKIT DLL increases by a factor of 9 to 10".

From this SPR, I understood that the debug information was provided intentionally with Pro/Toolkit library files to benefit the customers.

Based on the past feed back from Tech support (customer reported issues), this debug information was added to Pro/Toolkit libraries to generate better crash dump information if a crash occurred in a Pro/Toolkit app at customer’s end.

However, the SPR did not mention about VS2005 looking for source files while debugging Pro/TOOLKIT applications. I requested PTC development to check this issue and confirm. I’ll update you as soon as I hear from them.

Sincerely,

Seshu Kumar

Technical Support Engineer, Senior

============================================================================

It looks like quite a number of factors had influenced dll file size increase.

FV.

pwilliams-3 · ‎Feb 11, 2009

Thanks for the update Feliks. In my opinion they should distribute two
versions of their libraries then. A debug and release version. As far
as needing source files when stepping through, I think this can be
avoided by not stepping into any Pro/TOOLKIT functions. Am I wrong?

Patrick Williams | Sr. Application Engineer | Engineering Systems |
Steelcase Inc. | 616.698.4078 | My Site
<">http://my.steelcase.com/Person.aspx?accountname=NA\PWILLIA3>

seckart · ‎Nov 01, 2011

FYI - I opened a similar call complaining about large DLL's and the refrenced the closed SPR you found 1462374

I did some more looking and found another Open SPR - Severity High - 1985138 - that makes more sense and shows there is something that PTC can do to correct this issue. See PTC SPR Description below:

"

DomenicLaritz · ‎Feb 10, 2012

Hi together,

are there any news regarding the big Pro/TOOLKIT DLLs?
Has anybody a solution how to decrease the filesize?

Best regards, Domenic

DomenicLaritz · ‎Feb 10, 2012

Hi together,

are there any news regarding the big Pro/TOOLKIT DLLs?
Has anybody a solution how to decrease the filesize?

Best regards, Domenic

Eike_Hauptmann · ‎Feb 14, 2012

I don't know anything about the big toolkit dlls, but I know that OTK Dlls are bigger. Smallest OTK Example I build is 28 MB. So I think the size doesn't matter for PTC. But don't know.

Best regards,

Eike