![]() ![]() I have only used the SumatraPDF project, for building a single stand-alone exe, and have not tested the build of the DLL not yet fully set up to use github for distribution of binaries, so I have made a set of builds and put the results on my DropBox. I have not yet had any problems with this procedure I then run a few tests and if's they are OK i switch to the Release configuration and rebuild the SumatraPDF project and then do the tests again. I then usually build by opening the solution in VS2019, select the Debug configuration, and then build the SumatraPDF project in the solution. I have used this solution with a number of different printer drivers and paper formats and fork should compile directly, I try to keep up with the upstream SumatraPDF, and whenever I update I just do a fetch all and then rebase my changes on the upstream code. I have added a function that directly uses a PAPERKIND specification on the command line and I have made an extension to the original code for PAPERSIZE to handle custom sizes and to use PAPERKIND as a numeric alternative.īoth of these are used as ways to be able to control the correct paper size when printing a PDF using a SumatraPDF command line. ![]() Have made a fork to experiment with a couple of ways to use paper size specification from the command line. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |