On Tue, Nov 13, 2012 at 8:05 AM, Kai Tietz wrote: > As I said before ... "you need to add the target-lib/ folder to you path". >
That is unfriendly to the end-user. Note the discussion deals with more than just GCC it is a deployment of the client code using GCC that is in discussion. Businesses will not like your product very well if you have to go configure the client PC using it. > For the host-binaries in /bin it might be good to have "host" DLLs > used by it in the same directory. But this is just true for "host" == > "target" and if you have just one "target". Again the segregation is needed for the executable if you supply both a 32bit and a 64bit version in the same deployment. So taking a clue from the Windows/ directory sysnative/ contains the binaries for the 64bit versions and syswow64 contains the 32bit versions that run under the emulator. So MyApp/bin contains the native 64bit version and MyApp/bin32 contains the 32bit versions and MyApp must provide a manifest so Windows OS knows which is which. The associated DLL would go to the same directories for convenience to the user. -- Earnie -- https://sites.google.com/site/earnieboyd ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
