Copy .ini, .dat, and /saves/ref to bin (OutDir) about zelda3 HOT 11 CLOSED

I can't have the saves in the build folder, because when I switch between Release and Debug mode i wouldn't be able to load my other saves.

from zelda3.

Why <LinkIncremental>false</LinkIncremental>

from zelda3.

How about a package.py script that zips all the files you need into a zip-file?

from zelda3.

Re: saves in the build folder, CopyToOutputDirectory moves them to wherever OutDir is. If you don't like having an extra copy in both Debug and Release, I suppose you could do as you suggested in #74 and use a consistent OutDir but with differing names for the .exe files.

Re: LinkIncremental, I set it off for release (but not debug) because unlike the .pdb which I moved to the IntDir build directory, there's no way to change the location of the .ilk file from OutDir. Perhaps another solution would be better (e.g., a post-build step; and of course you could use that instead of CopyToOutputDirectory).

Re: a python solution, I suppose it sort of meets my suggestion in a cross-platform way, though I obviously prefer having a clean bin directory with which I can do whatever I want (e.g., a simple copy to another install location), and I personally prefer using a makefile with install/package macros for non-VS builds.

from zelda3.

The makefile could invoke the python script to install things

from zelda3.

I don't know how to move forward with this.

from zelda3.

I don't know how to move forward with this.

Well, if you're OK with not using a common python script, I've got an updated MSVS version in a branch in my fork: https://github.com/Nutzzz/zelda3/tree/output_folder

This follows your suggestion to have just one /bin OutDir with differing OutputFile names (e.g., zelda3-x86-debug.exe) so your /saves persist in a single location.

from zelda3.

I don't really like this.... Perhaps we could add a third build option called BundleRelease or something that does this?
Or some other way to have a shortcut in msvs that does it?

The python script could also invoke the extract_resources.py and invoke msbuild to build, and copy files...

from zelda3.

I remain slightly confused about what you like and don't like about this idea (beyond the couple of things that have already been implemented, thanks), but I went back to separate OutDirs and added a ReleaseDeploy configuration in my fork.

Note that Build won't replace an existing .ini but Rebuild does.

from zelda3.

...and now it looks like the .dat needs to be copied as well.
EDIT: Updated (fix for #122 ).

from zelda3.

Fixed in 8ee08ac

from zelda3.