On 9/09/2015 13:26, Edward Diener wrote:
On 9/8/2015 7:56 PM, Gavin Lambert wrote:
On 9/09/2015 05:38, Edward Diener wrote:
I already had a long, frustrating discussion with the mingw-64 developers about this and they are just adamant about the necessity that any given implementation's 'bin' directory must be in the PATH to just compile and/or link.
IIRC, their argument was that since the bin directory must be in the PATH to run the application (which is wrong, and bad practice for non-console apps at least) then they require it to be present when compiling so that running the app after compiling "just works".
'Compile/link' and 'run' are two separate steps. Doing the first does not always mean doing the second. A number of Boost tests are just compiles. An end-user should be allowed to configure a 'run' as he desires. Creating pre-conceived assumptions about how software should be used which limit the freedom and flexibility of programming is almost always a sign of bad programming design.
I completely agree. I was just filling in some context.