On 8 April 2015 at 20:03, Alexey Pavlov <[email protected]> wrote: >> build process for everything… >> > Sorry but we prefer shared linking. We build most packages with > «—enable-shared —enable-static» to have both shared/static linking but We > will not build with «—disable-shared —enable-static». You can do it yourself > if you need.
Thanks for the information - I understand what you're saying, I certainly wouldn't expect standard builds to be statically linked, I appreciate that my needs are very unusual. A further question, though, if I may - when you say "you can do it yourself if you need", the only way I know to build statically linked executables is to build the full toolchain, including all dependent libraries, with --enable-static --disable-shared. As you can imagine, that's a pretty painful exercise :-( Is it possible to use the mingw64 standard builds (which provide both static and shared forms) to build a statically linked executable? I've never managed to find any information on how to do this on the web - the autoconf documentation isn't very helpful on the matter. In particular, it would be fantastic if there were a way to configure a makepkg build to use the static versions of dependent libraries. Sorry if this is a basic question - I don't have any experience with the standard Unix build tools, all my experience is with Windows, so I don't really know how to properly do anything beyond the basics... Thanks for any help, Paul ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
