Hi Bill and Greg. Your answers have also made it clear my doubts about some merge between branches
73's Sandro IW3RAB Il 03/04/2015 01:48, Bill Somerville ha scritto: > On 02/04/2015 23:38, Alessandro Gorobey wrote: >> Hi All, > Hi Sandro, >> I would like an explanation on some files in jtsdk. > I will try ;) >> Referring to svn log, Bill write: >> ------------------------------------------------------------------------ >> r5139 | bsomervi | 2015-04-02 01:04:09 +0200 (gio, 02 apr 2015) | 5 lines >> Changed paths: >> M /branches/wsjtx/CMakeLists.txt >> M /branches/wsjtx/Configuration.cpp >> D /branches/wsjtx/kvasd.dat >> >> Do not package kvasd.dat >> >> This file is created at run time and is not needed in the deployment >> package. Also removed from source control to avoid further >> misunderstandings. >> ------------------------------------------------------------------------ >> >> I found the follow in sdk directory (dir kvasd.dat /s/b) : >> >> C:\JTSDK\src\trunk\kvasd.dat > The file above may not be necessary. I do not know exactly how WSJT is > packaged, it may also be erroneously including kvasd.dat. I did not > remove that one as I do not normally check out the trunk. >> C:\JTSDK\src\wsjtx-1.4\kvasd.dat > The file above could be removed if the change r5139 were to be merged > into ^/branches/wsjtx-1.4 but this branch is frozen to enhancements and > this change is of low importance since it has no bearing on WSJT-X > installation or running. >> C:\JTSDK\src\wsjtx_exp\kvasd.dat > The file above is in a feature branch and when that gets merged into > ^/branches/wsjtx the branch will become redundant. >> C:\JTSDK\wsjt\install\kvasd.dat (generated by wsjt running) > The file above is correct AFAIK. >> plus some in tags > Tags are not changed retrospectively as they represent milestones in > development. >> "This file is created at run time" is referred to >> %temp%\WSJTX-X[command line option]\kvasd.dat ??? > Correct. >> >> The file C:\JTSDK\src\wsjtx-1.4\issue-log.txt >> seems to be at Dec 2014. >> After a lot of work to hamlibs, wsjtx 1.4 and 1.5 I think that most of >> problems reported is solved. > The issue log was important when WSJT-W v1.4.0-rc2 was first released as > there were a lot of rig control issues to track. As the number of issues > reduced it became less important. There are some outstanding issues in > there such as requirements for support of new rig models in Hamlib that > will be addressed once the WSJT-X v1.4 GA release is complete. >> Thanks for the work >> >> 73's >> Sandro >> IW3RAB > 73 > Bill > G4WJS. > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
