> On 9/19/2011 22:38, Jon wrote: > > I'm working on an app (targeted to run on WinXP_SP2+) having DLLs > > with runtime dependencies on the particular MinGW-w64 > > `libgcc_s_sjlj-1.dll` and `libstdc++-6.dll` artifacts used to build > > the app. As such, these specific artifact versions will need to be > > placed on the end users PATH. > > > > I'm interested in hearing whether others have discovered > > particularly clever examples of automating a build process to > > ensure the build's install/archive step includes the correct > > versions of these MinGW-w64 toolchain artifacts. > > > > Thanks, > > Jon > > > > > > Why not just bundle the DLLs along side the user executable?
See side-by-side assemblies in MSDN if you need to control differing versions of DLL libraries. Earnie P.S.: My mail client (Claws-Mail) refused to quote Jon's mail. I had to forward it to myself and then reply to the mail. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
