Compiling program VC++ (and ComponentWork++) in release's mode with static library ...

[mfischer]

When i try to compil the program, there are conflicts between "nafxcw.lib" and an other library. The conflicts doesn't exist when i compil the program with shared library. Can you help me ?

my OS is Windows NT 4.0

thanks

[Jason F.]

Which "other library" does nafxcw.lib conflict with? Nafxcw.lib is an mfc library and is not distributed with Componentworks++.

When you say the conflict does not exist when you use the shared library, are you talking about the selection in the Measurement Studio App Wizard where it asks how you want to access the mfc library? What exactly is the conflict that you get?

In general I would always select to use the mfc library as a shared dll, because it is a known issue to statically link the library into any arbitrary project, not just a Componentworks++ project.

Jason Foster
Application Engineer
National Instruments
www.ni.com/ask

[Chris_W1]

Tools for Visual C++ (ComponentWorks++) currently does not allow the option of statically linking MFC; you must dynamically link the MFC libraries (as a shared DLL) to use ComponentWorks++.

This decision was made both because the vast majority of MFC programmers already choose to use the MFC DLLs, and because allowing other ways to use the MFC library would require National Instruments to distribute many different versions of the ComponentWorks++ modules.

Chris Wood
Applications Engineer
National Instruments

[xufei_sjtu]

then, how can I make sure that my application can run correctly on my custom's computer?
If my custom's computer has no measurement studio, or even has no mfc dll, what will happen?
I am facing the problem and wondering if I should choose measurement studio.
Thanks.
xufei_sjtu@yahoo.ca