search

divyang4481 / bizhawk

Automatically exported from code.google.com/p/bizhawk
0 stars 0 forks source link

DLLs Compiling into the Output folder not Output\DLL folder #230

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Get latest SVN
2. Build the Solution (release mode)
3. The Compiled DLL files are in the Output folder.

My "issue" is:
Do all DLL files belong in the folder "DLL" and not in the same folder as 
EmuHawk.exe?  If so, can the DLL Projects inside the solution be changed so 
their output is set to Output\dll instead of Output?  And can all DLLs that are 
not compiled by the user that are in the trunk, be moved to Output\DLL so that 
all DLLs are in one place?

What version of the product are you using? On what operating system?
I am using SVN r7387.  Though older versions should also be doing this.

Please provide any additional information below.
This only effects those that use the Developer Builds and only if the users 
compile BizHawk them themselves.

This is technically not a bug per say.  More of a question and a request (if it 
applies).

Original issue reported on code.google.com by hegyak on 26 Jul 2014 at 4:03

GoogleCodeExporter commented 9 years ago 
They compile to the output folder, it is just something developers have to deal 
with (there's no trivial workaround for this).  When making release builds, 
they are packaged into the /dll folder and EmuHawk will properly find them 
there.

Original comment by adeli...@tasvideos.org on 27 Jul 2014 at 2:41