Hi Mike, Bill, Nothing has changed in the hamlib3 build script for the Tool-Chain. The only thing that has changes is the SRC and Build location, which is now in: /c/JTSDK/src/hamlib3 as opposed to /c/JTSDK/msys/%USERNAME%/.. .. .. This was to eliminate issues surrounding compound user names ( those with spaces etc)
If your building Hamlib3 manually, you'll still need to use JTSDK-MSYS env ( for autotools ) and you need to export the paths to the QT5 MinGW toolchain. This is done for you when using the build script. Unless of course, you have your own MSYS setup that includes Autotools, if so, you need to ensure the MSYS profile uses the QT5 winpthread Toolchain, and *not* the MSYS mingw pthread tool chain. 73's Greg, KI7MT On 07/01/2015 11:40 AM, Bill Somerville wrote: > On 01/07/2015 18:02, Michael Black wrote: > > Hi Mike, >> >> Apparently all the paths are fixed in build-hamlib3 – that's what I've >> been doing here the last few days. >> >> Been a while since I had to compile hamlib and it appears something >> got changed in JTSDK-MSYS as I was used to playing with a g4wjs-hamlib >> in my home directory that used to work just fine but it also suffered >> the ar path problem which is fixed by adding this path in. >> > I'm confused, the compiler and binutils tools (ar, ld, ...) are all in > the same directory in the Qt bundled MinGW tools so I don't see how ar > could become missing. >> >> 73 >> >> Mike W9MDB >> > 73 > Bill > G4WJS. >> >> *From:*Bill Somerville [mailto:[email protected]] >> *Sent:* Wednesday, July 01, 2015 11:55 AM >> *To:* [email protected] >> *Subject:* Re: [wsjt-devel] building hamblib >> >> On 01/07/2015 17:45, Michael Black wrote: >> >> Hi Mike, >> >> That works too adding /C/JTSDK/mingw32/bin to the PATH. >> >> Agreed, but it begs the question "How did you (or configure) select >> the compiler & linker before?" >> >> 73 >> >> Mike W9MDB >> >> 73 >> Bill >> G4WJS. >> >> *From:*Bill Somerville [mailto:[email protected]] >> *Sent:* Wednesday, July 01, 2015 11:36 AM >> *To:* [email protected] >> <mailto:[email protected]> >> *Subject:* Re: [wsjt-devel] building hamblib >> >> On 01/07/2015 17:32, Michael Black wrote: >> >> Hi Mike, >> >> Works fine for "build hamlib3". But that takes way too long. >> >> But trying to build hamlib from with a make in hamlib3/build and >> ar is not in the path. >> >> CC newcat.lo >> >> CCLD libhamlib-yaesu.la >> >> ../libtool: line 1115: ar: command not found >> >> Makefile:382: recipe for target `libhamlib-yaesu.la' failed >> >> make: *** [libhamlib-yaesu.la] Error 127 >> >> Obvious ways around it but thought perhaps might want to fix this >> permanently. >> >> I added /c/Cygwin/bin to the path >> >> If you are building Hamlib for use with WSJT-X then the tools you use >> must be the same ones that were used to build Qt and the rest of >> WSJT-X otherwise you are going to create problems. That tool set is >> the one that comes bundled with Qt i.e.MinGW. >> >> >> 73 >> >> Mike W9MDB >> >> 73 >> Bill >> G4WJS. >> > > > > > ------------------------------------------------------------------------------ > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > > > > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
