On 8 April 2015 at 22:16, Matthieu Vachon <[email protected]> wrote: >> 1. Are the --login -i flags essential to correct working? Would I be >> able, for example, to simply run msys64\usr\bin\sh.exe -c "configure; >> make"? > > Why running `sh` to invoke commands, why not invoking your python script > directly from terminal? Maybe I don't correctly understand what you are > trying to achieve.. > > If I want to building multiple packages, I would have a single Python script > I would open my terminal (with the correct env for the toolchain I want to > use) and would simply launch my Python script from the terminal.
Well, that's certainly possible. I've written build scripts using the msys shell in the past, and they work fine. But I spend so much of my time in a powershell environment, that switching to bash, losing the context of the directory I'm in and having to cd back to it (translating Windows <-> Unix filename conventions) is a real stumbling block. And I don't store my development work in the msys home directory - I use a directory that suits my Windows build processes, and having msys-based builds stored somewhere else would be a problem. Essentially, I want msys/mingw to fit into my existing powershell-based development processes, rather than having to adapt my powershell processes to msys. And there's the other side of things - my console environment is 100% ConEmu, as it provides a much better console experience. The minitty.exe shell msys2 uses isn't remotely as productive for me. I'll probably just work through the various bat files and profile scripts and work out what I need to set manually. Then I'll just replace the supplied profile with something that works the way I want. Looks like the cd into $HOME is done by /etc/post-install/05-home-dir.post. Seriously, what's a profile doing changing directory? And for that matter, why does *every* login shell rerun the postinstall scripts? My only concern is that, if I hack around with /etc/profile and the scripts it calls, how much will I cause problems further down the line with maintaining msys2? I feel that as I'm in effect the sysadmin of the environment, I should be able to customise it as I wish, but what's going on in there seems like it might be pretty fundamental to the system. It's pretty frustrating - it feels like I have to do things the way msys2 wants me to, or I'll hit issues. > I hope I did not confuse you more about this. Don't hesitate to read the > MSYS2 wiki for more information. Not at all, it's been very helpful - many thanks. 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
