LNK4075: ignoring '/EDITANDCONTINUE' due to '/SAFESEH' specification is explained here:
https://msdn.microsoft.com/en-us/library/9a89h429.aspx (be sure to change the pulldown near the top that says "Visual Studio 2015" to "Visual Studio 2012").
In other words: check the linker configuration for the project and see if
/SAFESEH is set. If so, you can get rid of the warning doing
/SAFESEH:NO, or (from what I can determine) you have to register a safe exception handler within the code itself using
.safesh or other methodologies. Exception handlers... *sighing, shaking head*
C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead is self-explanatory:
several string-related functions in the CRT are considered deprecated, but cannot be explicitly rejected for backwards-compatibility reasons.
strcpy() in this case doesn't have the capability/ability to check for sufficient space in the destination when copying from the source, i.e. provides a potential buffer overflow vector.
strcpy_s() (
link) rectifies this through use of an argument that specifies the maximum length to copy and does some additional checking of ranges/sizes. The
_s suffix is supposed to indicate "secure".
strncpy() (which is what I'd have used) doesn't alleviate this on Windows either. The solution is to use
strcpy_s() and for the
numberOfElements field, determine what the size should be (through review of the code; they could be hard-coded values, or if for literal string space you might be able to use
sizeof() or
strlen() in some cases).
The reason you might see these while thefox doesn't could be explained in compiler version differences (ex. one of you using a different compiler suite than the other), or possibly some global linker settings (for the former issue) or compiler flags.
I'll just throw in here that concern/care about warnings is *highly* justified. Some of the worst advice I was ever given when I was learning C back in the late 90s was "ah, just ignore them" (warnings) -- and I'm very glad, still to this day, that I ignored that advice. (Please do not let this paragraph become a focal point of the thread.)