To be clear I wasn't really asking for support, I was telling you it broke in the last patch.
Secondly, read that and there is no output_log.txt. I'm asuming that KSP_Win should be my install directory, right?

To be clear I wasn't really asking for support, I was telling you it broke in the last patch.
Secondly, read that and there is no output_log.txt. I'm asuming that KSP_Win should be my install directory, right?

and I'm saying that it's working, which is why I asked for the log file.

Share this post

Link to post

Share on other sites

Also, it looks like a lot of the build depends on specific paths in your system. The AssemblyInfo templates can use the relative path of the .version file, but the post-build is another matter. Would it be reasonable to replace the hard-coded KSP path with a symbolic link from that KSP install to the output directory? (i.e. mklink /D R:\KSP_1.4.1_dev\GameData\KSP-AVC D:\Users\jbb\github\KSPAddonVersionChecker\Output\KSP-AVC). I've used this approach extensively myself and I've found it to work well.

Also, it looks like a lot of the build depends﻿ on specific paths in your system. The AssemblyInfo templates can use the relative path of the .version file, but the post-build is another matter. Would it be reasonable to replace the hard-coded KSP path with a symbolic link from that KSP install to the output directory? (i.e. mklink /D R:\KSP_1.4.1_dev\GameData\KSP-AVC D:\Users\jbb\github\KSPAddonVersionChecker\Output\KSP-AVC). I've used this approach extensively myself and ﻿I've found it to work well.

Not really, I'm not sure how git would deal with that. Keep in mind that this is a set up I evolved while maintaining and adopting over 130 mods. It may not be best, but it works, and is consistent across all my mods

I'd suggest that you try the changes on your system, but don't commit them.

4 hours ago, blowfish said:

Also, what's the﻿ purpose of all the test case .version files﻿?﻿

Test cases, I assume Seriously, I recently adopted this mod and am still trying to get a handle on it

And glad to hear the symbolic link stuff worked finally. I don't recall having issues like the ones you're describing but maybe I've been creating symbolic links for so long that I just forgot.

Just guessing, but I suspect the "gibberish chars" may have been a Unicode BOM, which some editors insert into text files. (It's not needed for UTF-8 so it's often omitted, but still allowed. I think some editors insert it just to explicitly indicate that the file is UTF-8.)

Just guessing, but I suspect the "gibberish chars" may have been a Unicode BOM, which some editors insert into text files. (It's not needed for UTF-8 so it's often omitted, but still allowed. I think some editors insert it just to explicitly indicate that the file is UTF-8.)

The only time I have a problem like that is with batch files being called by Visual Studio. Calling them by hand works, but from inside VS, its wierd, so I just leave the first line of my batch files blank