Fix VS2005 build environment #36
Comments
|
I just fixed the one issue I was aware of which was that the solution file didn't have some of the paths to projects correct. They should be correct now in GitHub. Other than that...there was a dependency on the DirectX SDK BaseClasses; so those needed to be compiled as well. But beyond that it should all build find in VS2005 (and it all did build for me before it was released). There are currently efforts underway by others on the forums for getting it to build with something much more current than VS2005 and they're making really good progress on it...I know they already have the EXEs built with it. |
|
Although there was some earlier discussion about getting this to work under VS2015, the last I've seen in the Forum was from wnjj on 9/12 who said "that's only part of getting this going. I'm off on something else for now." There was success with building the exe's, but I never saw any success with building the .ax and .dll files. I haven't been able to build them from the repo. Looked for an open Issue where someone else is actively following thru, but didn't spot one. Definitely don't want to duplicate effort. Maybe I missed something. I'm aware that the DirectShow BaseClasses need to be compiled outside the existing Solution, but there still seem to be additional issues. Although the Solution undoubtably was buildable some time ago, the existing VS build env. doesn't completely build with a "standard" clean installation of VS2005, the final DirectX SDK (June 2010) and Platform SDK6.1. In examining the .vcproj files, I see they expected an odd merger of DirectX SDK and Platform SDK files within the same DXSDK_DIR path. Was that normal in some older version of SDKs? Or maybe an indication of a rather "creative" toolset installation some time ago? There were also references to a hard-coded C:\DXSDK path; probably not something MS has done for awhile. Also, MS has omitted a critical file (dxtrans.h) from the final DirectX SDK (June 2010), so that needs to be taken into account. I was also planning to commit the missing hcwIRBlast.lib file. I've written a HOWTO doc for installing and configuring the above toolset and a concise list of the needed environment variables, since the "VS2005 build environment thread" has quite a range of info; some of it conflicting, but nothing all in once place. |
|
Cool, I didn't realize you had been following along on the forums. :) I Looking forward to someone committing the fixes to get this built in a On Mon, Sep 28, 2015 at 4:25 PM, Keith Fischer notifications@github.com
Jeffrey Kardatzke |
|
Yeah, been lurking in the forums (JustFred) ever since my initial Sage6 installation quite a few years ago. Really itching to get to the point where I can fix a bug in the channel-scan stuff (introduced in Sage7) that skips a C-QAM channel that has a mixture of clear and non-clear streams. But gotta get the toolchain working first. |
|
Unfortunately, ae41796 introduced changes that are fundamentally incompatible with VS2005 and it's libraries. That commit breaks the build under the current build environment. Best resolution is to move forward and migrate from VS2005 to VS2015. I'm going to close this issue and open another for updating to VS2015. |
|
Yeah, that doesn't surprise me it broke it...but those were essential On Sun, Oct 11, 2015 at 12:07 PM, Keith Fischer notifications@github.com
Jeffrey Kardatzke |
Ever since the development tree was placed into GitHub, native code (i.e, non-Java) couldn't be built using a "standard" installation of VS2005, DirectX SDK & SDK6.1. Once we're first able to fully build using VS2005, it will be much easier to take the next step of replacing VS2005 with VS2015.
The text was updated successfully, but these errors were encountered: