| | <<<Back 1 day (to 2019/10/22) | Fwd 1 day (to 2019/10/24) >>> | 20191023 |
| kens | Marco you might be better to put your questions in the #mupdf channel. Some of the MuPDF developers are here, some of the time, but you'll probably get a swifter response in the dedicated channel. | 07:29.17 |
| Marco | kens thanks, I will try | 12:49.50 |
| kens | Let me know if you have a problem, I can shout at the righ tpeople to come and chat here | 12:50.33 |
| Marco | thank you very much! | 12:53.02 |
| emendelson | A question about 9.50 and VS2017: I dual-boot between 32-bit and 64-bit Windows 10, with Visual Studio installed and updated on both systems. I imported the 9.50 code into VS2017 on both systems, made no change in the code at all, but changed the configuration to build all the components. This worked perfectly in 32-bit Windows 10, but under 64-bit | 17:09.40 |
| | Windows 10, everything failed except for Ghostscript itself. The fatal error messages looked this: | 17:09.41 |
| | 2>NMAKE : fatal error U1073: don't know how to make 'pclromfs1.obj'2>Stop.2>NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\HostX86\x86\nmake.EXE"' : return code '0x2' | 17:10.09 |
| | This happened with the default Win32 setting. - It finally occurred to me that maybe I should build for x64, but this failed too with different fatal-error messages. This happened on two different 64-bit Windows 10 systems both running VS2017. Am I missing something obvious? This isn't urgent, because I can build under 32-bit Windows 10, but I | 17:13.07 |
| | wonder if I'm the only person seeing this. | 17:13.07 |
| chrisl | emendelson: I can only say I worked when I built on VS2005. I'm not a regular Windows users, so I only tend to test and build for the release binaries | 17:19.17 |
| | emendelson: You say Ghostscript failed, but the error message says "pclromfs1.obj'" - that's not part of Ghostscript | 17:24.46 |
| emendelson | Sorry - I was trying to build GhostPCL, and should have clarified. | 17:25.12 |
| | As it turns out, I had a copy of VS2015 installed on one of these systems, and I was able to build gpcl6win32.exe with no trouble under VS2015. | 17:26.25 |
| chrisl | We do occasionally have issues with different VS versions, but that's not the kind of problem I expect | 17:27.08 |
| emendelson | OK, don't take my reports too seriously, because I'm a complete beginner at these things (even after ten years of building GhostPDL versions). | 17:27.53 |
| chrisl | Okay. Question, did you select a "Release/x64" build in the gui? | 17:28.51 |
| emendelson | Yes, I tried both Release/Win32 and Release/x64. - While I'm here, I found in VS2015 that I could build gpcl6win32.exe by building only that, but if I tried to build GhostPCL and GhostScript in the same build operation (by selecting both in the Config Manager), only GhostPCL would build correctly. | 17:31.30 |
| chrisl | I think you have to either build each product individually, or use the All target in the solution to build everything. | 17:32.40 |
| emendelson | Building individually does seem to work. Building the All target only produces a working Ghostscript; the others fail. | 17:34.26 |
| | Clarification: "Building the All target produces only a working Ghostscript..." | 17:35.09 |
| chrisl | Hmm, I'll check that, but it will have to be tomorrow | 17:35.51 |
| emendelson | No urgency about this - and of course I could be entirely wrong; that's happened before. - And, to confirm, I was able to build GhostPCL under VS2017 when I built only GhostPCL. So this isn't a fatal problem, just something that users might want to know about. | 17:37.12 |
| chrisl | emendelson: It's a known limitation, which is why we have the "All" project in the solution. For me, building All worked in VS2017 | 17:40.07 |
| | emendelson: I have to finish for the day. I'll experiment a bit more tomorrow, and double check what we say in the docs about it. You can leave other comments, and I'll read them in the morning (UK time). | 17:47.28 |
| emendelson | Well, basically ignore everything I said, and I apologize for wasting time. I took a fresh copy of the code, and chose the "All" project and everything worked correctly. Obviously, I messed up by choosing the wrong set of options in the configuration manager. Again, apologies for time-wasting, and I'll know better in the future.... | 18:48.53 |
| | <<<Back 1 day (to 2019/10/22) | Forward 1 day (to 2019/10/24)>>> | |
Log of #ghostscript at irc.freenode.net.