Ok, thank you. 

We are wanting to package this within the installer for our module and are just trying to make it as small as possible.  If this the best we can do, than that is fine.

Are there any other ways to limit the size of windows installation, perhaps using parameters to the installer or something like that?  Is there a way to exclude libraries that we don't need?

I apologize if this question is redundant based on previous answers. 

Thanks,
Joe

Thanks!  That is exactly what I was after.

Joe

Hi,

I am using omc.exe to run an mos to load mo files and call buildModel and then later running the executable with overrides.  I am hoping to pull out omc.exe and it's minimal dependencies so that I can package them in another module.  I don't need OMPlot, OMEdit, etc.  I would prefer not to build from source if it's unnecessary. 

So the questions:
What are the omc.exe's minimal dependencies?  Is there any documentation about this?  Is there a better way to go about this?

Thanks,
Joe