Multiple DLLs from a single project

[Steve_Block]

I'm curious about wheher CVI is capable of generating multiple DLLs from a single project. I'm using CVi with TestStand and would like to have my functions spread over several DLLs instead of just one, but would like to be able to manage everything from a single project. Is there a way of doing this.

[dummy_decoy]

i don't think you can generate multiple binaries from the same project (i don't see how it would fit into the target settings dialog...). however, you can create multiple projects (1 per DLL) and regroup them into a single workspace.

[Steve_Block]

That's what I'm hoping I don't have to do. If I do end up having to do that, is there a way to run them all simultaneously through the debugger.

[menchar]

Yes you can do more than a single dll in a workspace, but not in a single project.

And a CVI dist kit will not  check dll versions prior to overwrite - yuo have to create a merge module to get file version based behavior.

menchar

[dummy_decoy]

you may open as many CVI instances as you have DLL to debug: open each project in its instance of CVI, and press the debug button for all of them.

this may not be the most efficient way of debugging multiple dlls; can't you ensure that each dll is behaving correctly through its interface (the set of functions or variables it exports),  then debug them separately ?

[SLocke]

If you have a single EXE that is using all the DLLs, you could also add all the DLL projects to your main EXE project workspace, create post-build actions to copy the DLLs (and debug databases if in debug mode) to the EXE's directory, and debug/run the EXE.  CVI will let you step into/through any of the DLLs compiled in debug mode, and will let you set breakpoints in those DLLs as well.

[Guillaume Dargaud]

> That's what I'm hoping I don't have to do. If I do end up having to do
> that,
> is there a way to run them all simultaneously through the debugger.

Through the debugger, I don't know, but if you want to compile them all in
one go, you could write a simple scrip calling compile.exe on every .prj
file. It's found in the same directory as cvi.exe
--
Guillaume Dargaud
http://www.gdargaud.net/

[ebalci]

Hi,

Even if you do not have an EXE already, I think you need to write one to be able to debug your DLLs.

DLLs can be debugged when called from an "external process" and you need to specify it (must be an executable file) through Run > Specify External Process... menu.

You can make your program (the EXE) to call a function from the DLL so it gets loaded. Then you'll be able to step into your DLL code if you put breakpoints where necessary.

Hope this helps,