Re: [chirp_devel] Fix issue #2029 - Try to make Cygwin not complain about bash env params
On 15-01-11 03:00 PM, chirp_devel-request@intrepid.danplanet.com wrote:
Date: Sat, 10 Jan 2015 15:29:37 -0800 From: Dan Smith dsmith@danplanet.com Subject: Re: [chirp_devel] Fix issue #2029 - Try to make Cygwin not complain about bash env params To: chirp_devel@intrepid.danplanet.com Message-ID: 54B1B5E1.3030902@danplanet.com Content-Type: text/plain; charset="windows-1252"
The original changeset 2289:2f60576c5713 added these lines to most scripts where it was previously missing, however, it would appear that changeset 2295:1d3eb2711f91 was necessary to build on Cygwin/Windows.
However, only make_win32_build.sh was corrected by changeset 2295:1d3eb2711f91 and win32_remote_build.sh was left in a maybe not-working state. This patch should remove any potential remaining problems.
It works, and remote_build isn't actually run on win32 anyway, only the bare win32 one actually runs there.
If it's okay, do you mind if we just leave these two as they are? They really only run on my machine -- I don't even know if they're generic enough to work for other people or not.
--Dan
Absolutely! If you feel that you would like to leave this one out, I'm perfectly fine with that. I don't have access to a Windows machine to perform much in the way of testing there so I'm happy to defer the matter.
(Unless maybe someone already has a *confirmed working* Cygwin build/test environment running under Wine on Ubuntu perhaps.)
That being said, are you already aware of some other things that are likely to work only on your machine? These might be good candidates for me to start thinking about maybe improving/automating.
Tyler VA3DGN
Absolutely! If you feel that you would like to leave this one out, I'm perfectly fine with that. I don't have access to a Windows machine to perform much in the way of testing there so I'm happy to defer the matter.
Cool.
(Unless maybe someone already has a *confirmed working* Cygwin build/test environment running under Wine on Ubuntu perhaps.)
My build environment ssh's to a windows box running cygwin to do the actual builds.
That being said, are you already aware of some other things that are likely to work only on your machine? These might be good candidates for me to start thinking about maybe improving/automating.
That remote script is really the only one that's super hacky I think. It's really not useful unless someone wants to setup remote win32 builds from a linux machine, and even still, it's just one way to do it. I put it in the tree mostly just in case I get hit by a bus and because the builds get generated from the tree mostly without any external help. I don't know of anyone else that runs any of this stuff other than me (not much point) so I don't think it's worth a whole lot of effort, to be honest :)
--Dan
participants (2)
-
Dan Smith -
Tyler Tidman