Hi Dan, You should be able to install Msys, with autotools, to the default C:\MinGW or whatever it is these days. After which you'd need to copy a couple of files from the original /msys/etc folder (for mount points and such) and edit one file to update a path for the new installation of MSYS. Its not difficult. If you want to attempt this email me offline and I'll give you the step by step instructions.
73's Greg, KI7MT On 3/6/2017 8:57 AM, Dan Malcolm wrote: > Bill, > I actually do understand, and thank God for the Bill's and Greg's of this > world. My development efforts these days revolves around PHP and the PhpED > editor. A much more dragon free environment. Of course it is programming > and as such will never be completely dragon free. Remember the old joke > about devil and 10 lines of perfect code? > > Can we do this? You tell me what JTSDK architecture you think I need, and > given what I have in place, I will try to manipulate files/directories to > match that. The first problem to solve is getting the needed tools in > place. Perhaps then the procedures you provided will work. That should > relieve some of my demands on your time, as long as I can still ask the odd > question. At least now I have a sense of what needs to happen. If it all > fails, I can just use the release version of WSJTX. > > Thanks Bill, and thanks to you to Greg. > > _____________________________ > Dan Malcolm CFI/II > K4SHQ > > > -----Original Message----- > From: Bill Somerville [mailto:g4...@classdesign.com] > Sent: Monday, March 06, 2017 9:29 AM > To: wsjt-devel@lists.sourceforge.net > Subject: Re: [wsjt-devel] Hamlib3 compile error > > On 06/03/2017 14:51, Dan Malcolm wrote: >> What to do? Since I have the MinGW Installation Manager I guess I >> could install everything it offers, but it may be installed in the >> wrong place to do any good. Thinking of our email exchanges it seems >> you expect a lot of utilities to be available and available in a >> particular place. Is it possible that something went missing during my > initial package installation? > > Hi Dan, > > I need to clarify a few things. > > Firstly MinGW is Windows port of the GNU compilers. These are essential as > we use them to build WSJT-X. You get a version of them as part of the Qt > install and they match the compilers used to make the Qt libraries and > tools. This in turn is essential so that projects like WSJT-X can use them > and be compatible with the Qt libraries. > > We also use the Hamlib project for rig control. Unlike Qt which just needs > MinGW compilers, Hamlib uses the fairly standard autotools as well that > thousands of Open Source projects use. For autotools to work a Unix like > shell environment is required and there is one available that goes with > MinGW, it is called msys. Msys provides a command shell and many utilities > that would be found on a Unix like system. > > The problem with DLL load addresses is a Microsoft issue in that they use a > binary format that is not position independent. I have no idea why DLLs > suddenly stop working with fork() emulations, it just happens sometimes. The > cure is to rebase the relevant DLLs, rebasing in this context is looking at > the size of each DLL and allocating a unique load address hint to each one > so that none ever need to be loaded at a different address due to > overlapping, at least until whatever causes this happens again. It is this > loading into a process virtual address space at a different address that > causes the fork() emulations to fail. > > It appears that the JTSDK does not provide enough of the msys environment to > run this rarely required utility, that I tried to help you with but I am > largely working blind as I do not use the JTSDK and do not wish to install > it due constraints of other projects. Believe me that rebaseall is what you > need, it is designed to resolve exactly this issue with one simple command > invocation. > > It is quite possible to install each of the required tools and libraries > that are needed to build WSJT-X individually. Greg has taken the time to > build a relatively simple to use package that obviates the user from > understanding and doing all this work. He provides the minimum needed to do > the most basic build tasks which works well for almost everyone. In your > case you have hit an issue that needs a deeper understanding and more > components to resolve. I am afraid that using standard tools for software > development is complex and usually messy, you are living in a charmed world > where someone like Greg has smoothed down all the sharp edges for you but > nearby there be dragons and one of them has walked out of the forest in your > direction. > > 73 > Bill > G4WJS. > > > ---------------------------------------------------------------------------- > -- > Check out the vibrant tech community on one of the world's most engaging > tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ------------------------------------------------------------------------------ Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
