![]() ![]() Let's say there's old PDP-11 software that used to run in a control room on a Boomer. Minor point for discussion: Keeping up with software versions. It looks like that's only the SDK, which doesn't look like it needs to be built from source.įrom what I can see, it looks like the only change I'd have to make to the sim-master side is pointing the WinXX-specific include and library variables to a different directory, maybe copy DLLs over to the BIN directory. The interesting challenge will be winpcap, which is obsolete. There exists a pthreads42-cmake, which is pthreads4w with a CMakeLists.txt build prototype. If you look in some of the source directories, you'll find CMakeLists.txt files, which are CMake build prototypes, so using CMake isn't much of a stretch. It'll give you some control over where libraries, DLLs and headers are installed, so that you won't have that ugly lib\Release hack and copy files. For example, it'll generate solutions for VS2015, VS2017 and VS2019, 圆4 and x86, as well as for MingGW mingw32-make. This strategy was implemented as a consequence of early days experiences, where we had significant problems chasing down problems due to user built packages that weren't otherwise known to work.ĬMake is a meta-build system, very cross platform and multi-compiler. The careful build of this stuff aligns with the strategy that on non windows platforms, we explicitly do not support user built dependent libraries, but only count on OS supplied (or standard package distribution facilities) which presumes that those who put together the OS supplied packages have tested them and they work solidly on the particular host platform. From my point of view I think you are looking at a significant hill to climb with little potential gain. No problem asking questions along the way. If you want to design a different build paradigm for simh (including potentially a different paradigm for dependencies), feel free to do that and come back with something that works for all versions of visual studio, MinGW and the other supported host OS platforms and we'll check it out when you're ready. There is currently only one use of libpng (the SCREENSHOT command for simulators that have graphics devices). I looked at updating the libpng version, but it was much more trouble than it was worth. I'll be adding that explicit detail to the README.md Changes to this repo are few and far between (once or twice a year or when a new version of Visual Studio is released - I'm working on VS2019 which will be added soon). It is a static collection of things which have been carefully built to work and are customized to the various versions of Visual Studio that are supported. User rebuild of this stuff is absolutely not the intention.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |