Jump to content

  • Log In with Google      Sign In   
  • Create Account

Interested in a FREE copy of HTML5 game maker Construct 2?

We'll be giving away three Personal Edition licences in next Tuesday's GDNet Direct email newsletter!

Sign up from the right-hand sidebar on our homepage and read Tuesday's newsletter for details!


We're also offering banner ads on our site from just $5! 1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


No DLL local copy


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
3 replies to this topic

#1 Draycos   Members   -  Reputation: 108

Like
0Likes
Like

Posted 25 March 2013 - 11:10 AM

I have created solution using Visual Studio C++ 2010 Express which has two EXE projects and a DLL project - a game, game editor and the shared code.  Since having switched to a more 'industry standard' directory structure I've been getting a "program can't start because xxx.dll is missing" error.  I've added all the dependancies and references, made sure 'Copy Local' is set to true, etc (the 'Reference Properties' even shows the correct full path of the dll), but there isn't a local copy of the dll in the project output directory when I compile the solution.  I can get around the error by manually copying the dll, but it would seem that Visual Studio should be doing this for me.  Can you suggest why Visual Studio might not be doing this, have I missed a setting somewhere?



Sponsor:

#2 Paradigm Shifter   Crossbones+   -  Reputation: 5408

Like
0Likes
Like

Posted 25 March 2013 - 11:14 AM

You can set the output path in the linker output options panel for the dll project.


"Most people think, great God will come from the sky, take away everything, and make everybody feel high" - Bob Marley

#3 Serapth   Crossbones+   -  Reputation: 5582

Like
1Likes
Like

Posted 25 March 2013 - 11:29 AM

This post explains one way to do it.

 

How you set it up really depends on you.  I generally create a shared folder ( projectroot/dlls ) for example that all generated and 3rd party dlls are put in.  In this case, I simply invoke a copy command as a post build command in my dll projects.   Then in your other projects, you add this folder path as a dependency.  However, this requires you to update dependencies manually ( if your DLLs change, this dependency isn't known across the various projects ).



#4 Draycos   Members   -  Reputation: 108

Like
0Likes
Like

Posted 28 March 2013 - 12:22 PM

This post explains one way to do it.



Cool, thanks for the info.  I think I just need to concrete my project directory layout, as nicely illustrated in your link.




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS