[hpsdr] VS2015 build questions & help request

[Neal Campbell]

You do know you can use VS2015 while compiling with an older SDK (say
vs2010..)? Thats what I do for DXBase.

73

Christmas Sale in Progress!

Neal Campbell
Abroham Neal LLC



On Thu, Dec 24, 2015 at 3:04 PM, Rick Royston <rick.kf4zz at yahoo.com> wrote:

> ***** High Performance Software Defined Radio Discussion List *****
>
> Group,
>         I appreciate the info.  I may look at simple changes to support VS
> 2015, but if I ever reach the point that I have a useful module I will
> build in the common environment of the day.  That will make life simpler
> for those doing the heavy lifting.  The area I am investigating is pretty
> tightly compartmentalized as it has even beed suggested as connected only
> by a virtual ports.
>
> In the short term I want to get some internal visibility into the USB
> detection of the enumerated devices so the build will be kept local.
>
> Rick-KF4ZZ
>
> Merry Christmas All!
>
>
> > On Dec 24, 2015, at 12:23 PM, George Byrkit <ghbyrkit at chartermi.net>
> wrote:
> >
> > Joe,
> > Thank you for your reply!  I was only informing Rick why he was having
> an issue with
> > VS2015, and informing you and Doug what the apparent compatibility
> issues with VS2015
> > were.  I'm still using VS2013 for KISS Konsole maintenance.
> >
> > Beyond the issue that I identified, I'm not sure that you would find any
> other issues in
> > VS2015, since the code involved is C code and not C++ code.  If you have
> identified any
> > other issues, I would appreciate hearing about them!
> >
> > Of course you need to become aware of the issues such as the one that
> Rick raised.
> > Otherwise we become stuck too far in the past.  I was part of the group
> that proposed that
> > VS2013 (community edition, with the MFC MBCS supplement) was
> acceptable.  I agree that
> > you, Doug, Phil and Warren need to work on a common platform.  Yet,
> making a somewhat
> > simple change to allow others the possibility of exploring a newer
> version of Visual
> > Studio doesn't seem like it should be a significant inconvenience to you
> all.  If I'm
> > wrong in that supposition, I'd like to understand why.
> >
> > I am not, after all, proposing that you move to VS2015 Community Edition
> as your
> > development environment.  Only that you do some relatively minor things
> to not preclude
> > others from using VS2015 Community Editon.
> >
> > 73,
> > George K9TRV
> >
> > -----Original Message-----
> > From: Joe Martin [mailto:k5so at k5so.com]
> > Sent: Thursday, December 24, 2015 1:04 PM
> > To: George Byrkit
> > Cc: 'Rick Royston'; hpsdr at lists.openhpsdr.org; Doug W5WC
> > Subject: Re: [hpsdr] VS2015 build questions & help request
> >
> > Rick, George,
> >
> > Doug, Warren, Phil, and I use VS2013 Community in our current
> development activities, by
> > mutual agreement to avoid problems with different development tool
> version
> > compatibilities, such as you are experiencing with using VS2015.  Some
> day we may wish to
> > move to VS2015 Community but that is not today.  There are simply too
> many changes
> > presently in flux with software/firmware/protocol issues to
> unnecessarily complicate
> > things further by switching development tools midstream during this
> large development
> > effort.
> >
> > My recommendation to you is to use VS2013 Community if you wish to be
> compatible with our
> > current work without issues.  Of course, if you don't mind working
> through compatibility
> > issues then by all means use whatever version of tools you wish.  Just
> thought I'd let you
> > know what we're presently using.
> >
> > 73, Joe K5SO=
> >
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help:
> http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20151224/ff217913/attachment.htm>