On Mon, Apr 13, 2015 at 3:59 PM, Paul Moore <[email protected]> wrote:
> On 10 April 2015 at 08:35, Ray Donnelly <[email protected]> wrote:
>> I had a go at this last night, and here's what I came up with (fingers
>> crossed
>> the email doesn't get too mangled ..):
>
> A simpler approach (if you don't mind having a whole other copy of
> msys2) is to just install a new copy of msys2 from the base archive,
> do the initial update as usual, and install all of the dependencies
> you might need to build the packages you want. Then just do
>
This may be simpler initially, but probably once people get into the
swing of MSYS2 and Pacman mine is simple enough; it's certainly faster
and requires less space, or maybe I just like using the bash command
line a lot.
> find /mingw64/lib -name "*.dll.a" -exec rm {} \;
>
> to make your mingw64 build tree purely static. (This obviously means
> you shouldn't use this tree for anything other than making static
> builds - but that's why you need a separate installation for this
> method).
>
> Now just get the build directory you want from
> https://github.com/Alexpux/MINGW-packages, and run
>
> MINGW_INSTALLS=mingw64 makepkg-mingw
>
> (I guess you can build for 32-bit as well if you want, if you strip
> the .dll.a files from /mingw32, but I haven't tried this).
>
> Don't add -s to the makepkg-mingw command, as that'll download dynamic
> link libraries. Instead, if you did miss a dependency, stop and
> install it manually and then strip any new .dll.a files before
> rerunning makepkg-mingw.
>
> I've only tried this on libarchive so far, and it seems to work as
> expected. One odd thing is that it doesn't build or install the
> internationalised messages. I don't know if that's something odd with
> libintl, but in actual fact for my needs, omitting the message files
> is a bonus rather than a problem (I only want English messages, and
> fewer files to deploy fits my needs in this case). So although I'll
> probably dig around to see if I can work out why this happens, it's
> not a high priority for me.
>
> Anyway, I hope this is of some use to people, even if just as an
> alternative to the approach Ray described.
Coincidentally, someone asked how to handle static and shared
libraries on the CMake mailing list today, as I suspected, it doesn't
have a good story here either:
https://www.mail-archive.com/[email protected]/msg51678.html
>
> Thanks again for all the help.
No problem at all.
>
> 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
